Help from the people who build Octri
Every message to support is read by the engineers who write the code you are asking about. Tell us what broke and what you expected, and we will aim to make the first reply the fix.
Production problems go first, on every plan.
Hi. What went wrong?
Pick one and Octri will point you at the fix, or at the right inbox.
- Product
- support@octri.dev
- Billing
- sales@octri.dev
- Security
- founders@octri.dev
Ways to reach us
Pick the inbox that matches the problem and it reaches the person who can fix it.
What your plan includes
Every plan gets help. Higher plans get it sooner and in more ways. Compare plans
Free
Docs and GitHub
Every guide, plus GitHub for generated SDKs. Hit something that looks like a bug? Email us anyway.
Starter
Email support for the product, your account and your billing.
Growth
Priority email
Your messages go to the front of the queue, and we get on a call when that is faster.
Business
Priority email
The same front-of-queue email as Growth, with a call whenever that is faster than writing back and forth.
Enterprise
Dedicated
A named contact, a shared channel if you want one, and response targets written into your order form.
Outside an Enterprise agreement we do not publish response times. A number on a marketing page is worth little the day it slips, so we tell you where your message stands instead.
What we promise you
Whichever inbox you write to and whichever plan you are on.
Production comes first
A broken live docs site or a failing production SDK goes ahead of everything else in the queue, whatever plan you are on.
You hear about outages from us
If docs sites, the dashboard or the API are down for more than a moment, account owners get an email with what we know and what we are doing.
Staff access is on the record
Anything Octri staff do in your organisation is written to your audit log under their own email address, next to your team’s actions.
We never ask for your password
No one at Octri will ask for a password, a two-factor code or a live API key. A message that does is not from us.
What we generate is yours
SDKs, MCP servers, code samples and docs output belong to you, with no royalty. Publishing runs under your own registry accounts.
Leave whenever you like
Cancel from the billing portal at any time. Your plan runs to the end of the period you paid for, then moves to Free.
Write once, get the fix
The more of this your first message has, the more likely the first reply is the fix.
- Your organisation name and the project involved.
- What you expected, what happened instead, and the steps to reproduce it.
- When it happened, with a timezone. A five-minute window is usually enough to find the request.
- The request id or the full error message, if the dashboard or the API gave you one.
- For SDKs: the language, the version and the build log. For docs: the URL.
- Never live API keys, passwords or customer data. Strip credentials from a spec before you send it.
To support@octri.dev
Subject SDK build problem
- Organisation
- Acme
- Project
- Acme API
- Expected
- The Python SDK to build after we added POST /invoices
- Instead
- The build failed at the type check
- When
- 24 Oct, 14:05 CET
- Error
- req_7f3k2q · "InvoiceCreate has no schema"
build-log-python-2.3.0.txt
Before you write in
Use the password reset link on the sign-in page. If you lost your authenticator, use one of the recovery codes you saved when you turned two-factor on. If you have neither, an owner or admin in your organisation can reset two-factor for you. If you are the only owner, write to support@octri.dev from the account’s email address.
More on limits and credits in the Fair Use Policy, and on cancelling in the Terms.
Still stuck? Write to us.
A person reads every message. Send the details and we will take it from there.