Skip to content
Ember

01 / Pricing

No rate card yet. That is deliberate.

Ember is early. We are working directly with teams who want to shape it, so pricing stays a conversation about scope rather than a grid you pick a row from.
If you need a number for a budget line, ask us and we will give you one.

02 / Stance

Publishing tiers before the product has settled would be a guess dressed up as a policy.

What happens instead

We talk with engineering leaders and early users about scope, integrations and what good would actually look like for their team.

What the number depends on

Team size, how you roll out, and how much support you want from us while we are both still learning what Ember is good at.

When that changes

Clearer packaging will reflect what we have shipped with real teams. Until then, a conversation is more honest than a table.

Ember is in private development.

scopeintegrationsrollout

03 / What we optimise for

Beyond the number itself.

Four things we care about in an early agreement.

  • 01

    Straight terms

    Simple early engagements with room to adjust as both sides learn what works. Nothing that takes a quarter to unpick later.
    fewer moving parts
  • 02

    Priced against how you operate

    Scope tied to the activity you actually connect and the teams that actually use it, rather than a generic per-head number on a spreadsheet.
    not seat count
  • 03

    Rollouts people use

    We would rather run a narrow pilot that gets used than a broad one that gets forgotten. Working out which is which is most of the conversation.
    not shelfware
  • 04

    Early partners steer the roadmap

    Teams in early access shape what gets built next. That loop matters more to us right now than the size of the agreement.
    feedback over contract

04 / Who this is for

Early access suits some teams more than others.

If none of these describe you yet, that is useful for us to know too. The writing is a better starting point than a sales call, and it will tell you whether the way we think about cause matches the way you do.

No hard qualification. Just an honest fit check.

  • Engineering leaders who want fewer surprises out of production and chat

    You currently find out from a customer, a channel, or a dashboard you happened to be looking at.

  • Teams ready to run a focused pilot rather than a procurement cycle

    One service, one team, a few weeks. Not a company-wide rollout with a steering group.

  • Groups who care about being able to inspect what a tool concluded, and why

    If it cannot show the evidence underneath a conclusion, your team is not going to act on it.

05 / Thinking

The cost of the problem, written down.

All writing

06 / Talk to us

Tell us about your team, your timeline and what you need to see.

Join the waitlist, or open the contact page and start with the requirements. Either reaches the same people.
Join the waitlistTalk to us
We will tell you what is true today and what is queued, without overselling either.