Reach us without making an account
One person reads these. No form routing, no qualification, and no sales team to be passed to.
Where this actually goes
Into a table in our own database, which is the only channel we can prove arrives. There is no address on this domain to write to: it has no mail routing, so anything we printed here would bounce at the sending server and you would never know.
The row is written first, and then it is forwarded: the full text goes by email to the person who answers these, and the subject line alone is posted to our own alerting channel. Both are listed on the Trust Center. Please do not paste API keys or passwords into it.
There is no response-time commitment behind any of it, for the same reason there is no uptime SLA: there is no rota to honour one.
Reporting a vulnerability
Please use this form: quietly, and before disclosing it anywhere else. There is no bug bounty and no PGP key. Good-faith research that stops at the first sign of another customer’s data is welcome, and a report will be read and answered.
What we do and do not have in place is written out on the Trust Center, including the certifications we do not hold.
Four lines that make the first reply useful
- Roughly what you spend on models a month, and with whom.
- The shape of the traffic: chat, batch, agents, embeddings.
- Any constraint that is non-negotiable: residency, an audit report, SSO. Lead with it. It may end the conversation early, which is better for both of us.
- Whether you hold provider contracts you would rather keep using.
Already have an account?
Use Support inside the dashboard instead. It files the message against your account, so we can see the request you are asking about without you having to describe it.