Pricing
Priced per person on call, not per alert.
A noisy week shouldn't cost you more. Start free and move up when Nocturne has earned it.
Prices in US dollars, excluding VAT and sales tax.
Free
$0
Free for as long as you like
One team trying it out on a few services.
Start free- 3 services
- 1 on-call rota
- 50 investigations a month
- Diagnosis and a suggested fix for every alert
- Shadow mode
- Slack and email notifications
- 7 days of incident history
Team
Recommended$49
per on-call engineer a month ($39 billed yearly)
Teams ready to let it act, with a person approving.
Start freeYour first 14 days include Team.
- Everything in Free
- Unlimited services and rotas
- Unlimited investigations
- Rollbacks, flag changes and scaling, with approval
- Fix pull requests on GitHub or GitLab
- Approval rules per service and environment
- Runbook import
- Hand-off to PagerDuty or Opsgenie
- 1 year of incident history
- Email support, answered within one working day
Enterprise
From$1,500
a month, billed yearly
Organisations with a security review to pass.
Start freeOr email enterprise@nocturne.example
- Everything in Team
- Single sign-on (SAML) and SCIM user provisioning
- Runner inside your own cloud account
- EU or US data residency
- Your own list of actions Nocturne may never take
- Audit log export to your SIEM
- 99.9% uptime commitment in your contract
- A named support engineer and a shared Slack channel
- Invoices in US dollars, pounds or euros
Every plan, side by side.
| Free | Team | Enterprise | |
|---|---|---|---|
| Watching | |||
| Services | 3 | Unlimited | Unlimited |
| On-call rotas | 1 | Unlimited | Unlimited |
| Investigations a month | 50 | Unlimited | Unlimited |
| Monitoring integrations (Datadog, Grafana, Prometheus, Sentry) | Yes | Yes | Yes |
| Runbook import | No | Yes | Yes |
| Fixing | |||
| Diagnosis with every step shown | Yes | Yes | Yes |
| Suggested fixes | Yes | Yes | Yes |
| Shadow mode | Yes | Yes | Yes |
| Rollbacks, flag changes and scaling | No | With approval | With approval |
| Fix pull requests | No | Yes | Yes |
| Approval rules per service | No | Yes | Yes |
| Low-risk actions without approval | No | Yes, ones you name | Yes, ones you name |
| Custom list of forbidden actions | No | No | Yes |
| People | |||
| Slack and email notifications | Yes | Yes | Yes |
| PagerDuty and Opsgenie hand-off | No | Yes | Yes |
| Incident notes posted to Slack | Yes | Yes | Yes |
| Security and data | |||
| Incident history | 7 days | 1 year | Your choice |
| Audit log export | No | CSV | CSV and SIEM |
| Single sign-on (SAML) | No | No | Yes |
| SCIM user provisioning | No | No | Yes |
| Hosting | EU or US | EU or US | EU, US or your own cloud |
| Support | |||
| Support | Docs and community | Email, one working day | Named engineer and shared Slack channel |
| Uptime commitment | None | None | 99.9% in contract |
Questions engineers ask us.
Will Nocturne change production without asking?
Not unless you tell it to. Out of the box, every production action needs a person to approve it. You can let it go ahead alone on specific low-risk actions, one service at a time, and you can take that back whenever you like.
What if it gets the diagnosis wrong?
It shows every query and log line behind its answer, along with how confident it is, so a wrong answer is easy to spot. The actions it can take are all reversible, and when its confidence is low it pages a person instead of guessing.
What access does it need?
To start, read-only API keys for your monitoring tools and your code host. Taking action needs a separate credential with a narrow scope, which you create and can revoke. On Enterprise the runner sits in your own cloud account, and only incident summaries leave it.
Do you train AI models on our data?
No. Your logs and code are used to work your incidents and for nothing else. Incident history is kept for as long as your plan says, then deleted.
Who counts as an on-call engineer?
Anyone on a rota that Nocturne covers, counted once however many rotas they're on. People who only approve or read incidents are free.
Why are prices in dollars?
We sell to teams in a lot of countries, so we price in the currency most developer tools use. Enterprise customers can be invoiced in pounds or euros.
Start with three services and a week of shadow mode.
No card needed. If Nocturne's suggestions are no good, you've lost nothing but a few API keys, and you can revoke those.