Skip to content
Ember

01 / Contact

Talk to the people building it.

There is no sales queue. Messages reach the team directly, and you get a reply from a person who works on the product.
If we are not the right fit yet, we will say so plainly rather than keep you warm.

02 / What to write about

All of them reach the same inbox.

Four things this page is good for.

  • 01

    Early access or a pilot

    Tell us the service you would point Ember at, the team that would use it, and roughly when. That is enough for us to say whether the timing works.
    waitlist
  • 02

    Security, diligence or procurement

    Questionnaires, integration scope, or anything from a risk review. We answer at the level of directness the security page sets, including where the answer is 'not yet'.
    security
  • 03

    A product question

    Including the sceptical ones. If you want to know how Ember decides something is evidence rather than noise, ask that.
    product
  • 04

    Something else entirely

    Partnerships, press, or a note telling us we have got something wrong. Short messages are welcome.
    open

03 / Send a message

Two fields. That is the whole form.

We read every message ourselves, reply from a real address, and keep the response practical and short. No drip sequence, no qualification call before a human answers.

Usually within two working days.

Short notes are fine. Longer context helps too.

Direct addresses

Vulnerability reports can also follow security.txt.

Ember is in private development. Onboarding runs in waves rather than on demand.

Not ready for a conversation? The writing explains how we think about cause and evidence. Come back when it makes sense.