Company
Contact OpsAI
Reach sales, enterprise, security, developer support, or general enquiries. Tell us which and we will route it to the right people.
No form
This site is statically exported, so a form would have nowhere to post to. One that appeared to submit while going nowhere would be worse than none — you would believe you had made contact.
Routes
4
Forms that go nowhere
0
Four addresses
Pick the one that matches, and include the two or three facts that let somebody answer.
Most enquiries to a product like this arrive missing exactly the information needed to reply usefully, which turns one exchange into three. What to include is listed under each address — it costs nothing to have been told and it saves a fortnight.
Sales and evaluation
hello@opsai.devYou are working out whether this fits, or you want a number.
What to include
- Roughly how many AI systems you would bring under governance.
- Which systems of record they reach, or would need to.
- Whether you have a deployment constraint — managed, your own cloud account, or air-gapped.
Security review
security@opsai.devYou are assessing the architecture, or you have found a vulnerability.
What to include
- For a review: which questionnaire or framework you are working from, so the answer maps to it.
- For a vulnerability: what you did, what happened, and what you expected.
- Please do not test against another organization’s tenant, and do not scan production.
Developer support
developers@opsai.devSomething in the API or an SDK is not behaving as documented.
What to include
- The action id, if there is one. It resolves the whole trace and usually the question with it.
- The request and the response, including the error code rather than only the status.
- Which SDK and version, or whether you are calling the API directly.
Enterprise and procurement
enterprise@opsai.devYou need contractual, compliance or deployment answers in writing.
What to include
- The control obligations you are assessed against, so the mapping can be checked against yours.
- Whether a current third-party audit report is a hard requirement — OpsAI holds none today.
- Your data residency and retention requirements.
What happens next
A reply from a person, and no date attached to anything we have not committed to.
The same discipline as the rest of this site. If the answer to your question is that OpsAI cannot do the thing yet, that is the answer you will get rather than a timeline.
- A straight answer about gaps
- If a connector you need is not built, or a certification you require is not held, you will be told that plainly. The certification position is already published for exactly this reason.
- No date we have not committed to
- Including for an audit, a connector or a feature. The roadmap carries no dates, and neither will a reply.
- Your estate stays yours
- Nothing you describe becomes a case study or a reference without a written agreement. There are no customer names anywhere on this site, and that is not an accident.
- If it is urgent and operational
- Say so in the subject line. The status page cannot tell you whether something is up, because it is statically exported — so reporting it is genuinely faster than checking.
Reporting a vulnerability
Send it to security@opsai.dev and we will tell you what we intend to do.
Acknowledged on receipt, with a real answer about whether it is being fixed rather than an automated reply. A sandbox tenant is available for security testing on request.
Include what you did, what happened, and what you expected. If you found a way to reach a system of record without passing the boundary, that is the most valuable report you could send — the four routes we know about are published, and a fifth would matter a great deal.
Please do not test against another organization’s tenant, and please do not run automated scanning against production.
Addresses
- Sales and evaluationhello@opsai.dev
- Security reviewsecurity@opsai.dev
- Developer supportdevelopers@opsai.dev
- Enterprise and procuremententerprise@opsai.dev
Where to start
Count your AI systems before the first conversation.
It is the input to every other question — pricing, deployment, which controls matter first — and most estates find the number is larger than anybody expected. Discovery reads systems you already run to find it.