Pricing
Three plans. Priced per node.
Start with monitoring and alerting, take the full operational platform, or add the intelligence layer on top. Every plan is licensed per database instance, and the rate steps down as the fleet grows.
Plans
What each plan does
Basic
Monitoring, alerting and incidents
from$15/node/mo
Monitoring, alerting, incidents. Database and host metrics across every supported engine, dashboards and health visibility, alert rules with severity, state and history, and incident management with email notification.
Request Basic pricingOperations
The full platform, without the AI layer
from$35/node/mo
The full operational platform without the AI layer. Everything in Basic, plus fleet and topology, query analytics, backup with point-in-time recovery, the Deployment Manager, provisioning, drift detection, advanced incident correlation, maintenance workflows and every integration — PagerDuty, Jira, Slack, Teams and webhooks.
Request Operations pricingRecommended
Intelligence
The full platform, plus the intelligence layer
from$49/node/mo
Everything in Operations, and the part that does the reading for you: the AI Database Assistant, the Recommendation Engine, performance insights and AI-assisted root-cause investigation — each answer carrying the evidence it came from.
Request Intelligence pricing
Estimate
What it would cost for your fleet
| Nodes | Basic | Operations | Intelligence |
|---|---|---|---|
| 1 – 10 nodes | $15/node/mo | $35/node/mo | $49/node/mo |
| 11 – 25 nodes | $14/node/mo | $33/node/mo | $46/node/mo |
| 26 – 50 nodes | $13/node/mo | $31/node/mo | $43/node/mo |
| 51 – 100 nodes | $12/node/mo | $28/node/mo | $39/node/mo |
| 101 – 250 nodes | $10/node/mo | $25/node/mo | $35/node/mo |
| 251+ nodes | $9/node/mo | $22/node/mo | $31/node/mo |
Compare
What is in each plan
| Capability | Basic | Operations | IntelligenceRecommended |
|---|---|---|---|
| Monitoring & alerting | |||
| Database monitoring and metrics | Yes | Yes | Yes |
| Host monitoring, host metrics and host configuration | Yes | Yes | Yes |
| Dashboards and health visibility | Yes | Yes | Yes |
| Alert rules, severity and state | Yes | Yes | Yes |
| Alert historyEvery firing, mute and acknowledgement retained, so a recurring problem is visible as a pattern. | Yes | Yes | Yes |
| Incident management | Yes | Yes | Yes |
| Advanced incident correlationRelated signals absorbed into one incident carrying the event sequence, rather than a wall of separate alerts. | No | Yes | Yes |
| Maintenance windows and maintenance workflows | No | Yes | Yes |
| Operational platform | |||
| Fleet and topology | No | Yes | Yes |
| Query Analytics | No | Yes | Yes |
| Backup and recovery | No | Yes | Yes |
| Point-in-time recovery | No | Yes | Yes |
| Deployment Manager | No | Yes | Yes |
| Provisioning and automation | No | Yes | Yes |
| Inventory and drift detection | No | Yes | Yes |
| Notifications & integrations | |||
| Email notificationsAn alerting product needs a channel, so email is in every plan. | Yes | Yes | Yes |
| PagerDuty | No | Yes | Yes |
| Jira — two-way incident linkStatus, assignee and comments read back from Jira; comments and status pushed the other way, attributed. | No | Yes | Yes |
| Slack and Microsoft Teams | No | Yes | Yes |
| Webhooks | No | Yes | Yes |
| Intelligence | |||
| AI Database AssistantAsk the estate a question in plain language. | No | No | Yes |
| Recommendation EngineFinding, evidence, impact, suggested action, confidence and why now. | No | No | Yes |
| AI analytics and Performance Insights | No | No | Yes |
| AI-assisted root-cause investigation | No | No | Yes |
| Evidence-backed analysisEvery answer cites the metric, query, event or run it drew on, so it can be checked rather than trusted. | No | No | Yes |
| Contextual analysis across metrics, queries, topology, incidents, backup and inventory | No | No | Yes |
| History | |||
| Full-resolution metrics and time-seriesEvery sample as collected — the detail an investigation into one specific minute needs. | 2 weeks | 2 months | 2 months |
| Aggregated metrics and analyticsThe rolled-up series behind trends, baselines and recommendations. | — | — | 6 months |
Full-resolution history is every sample as the agent collected it — the detail an investigation into one specific minute needs. Aggregated analytics is the rolled-up series behind trends, baselines and recommendations, which is why Intelligence keeps it for six months: a recommendation about a capacity trend needs months of shape, not months of raw samples.
The model
How licensing works
- Licensed per node
- You pay for the database instances SchemaPulse manages, not for seats, queries or data volume. Adding an engineer to the console costs nothing.
- Volume banded
- The per-node rate steps down as the fleet grows, so consolidating your estate onto one platform gets cheaper per instance rather than more expensive.
- Node-locked keys
- Licences activate against specific hosts, with rebind and release built in — replacing hardware does not mean buying a licence again.
- Self-hosted
- One licence covers the platform running in your own infrastructure. There is no per-environment surcharge for staging or DR.
What you can buy
Four things, priced differently
SchemaPulse platform
The licence for the platform, running in your infrastructure and operated by your team.
Priced per node with volume bands, on one of the three plans above. The plan sets what the platform does; the band sets what it costs.
Request pricingSupport
Response times, channels and coverage hours, matched to how critical the estate is.
Tiered alongside the platform licence. We will recommend a tier based on your topology and recovery objectives rather than selling you the largest one.
Compare tiersDBChefs professional services
Database engineering engagements — migrations, performance work, architecture, HA/DR.
Scoped per engagement, because they genuinely vary. An assessment comes back with what we would actually do and what it would take.
Request an assessmentSchemaPulse + DBChefs
The platform operated with expert support.
Built per environment rather than sold as a fixed tier. Implementation, ongoing operations, optimisation and recovery assurance on top of the licence.
Build a planCommon questions
Before you ask us
- What counts as a node?
- A database instance SchemaPulse manages. A three-member replica set is three nodes; a router or mongos fronting them is not counted separately.
- Can I mix plans across one estate?
- Yes. Production on Intelligence and non-production on Basic is a common shape, and the volume band is calculated across the whole fleet rather than per plan.
- Can I move up a plan later?
- Yes, at any point in the term. Moving up is a licence change, not a redeployment — the platform and the agents are the same on all three plans.
- Why does Intelligence keep analytics longer?
- Because recommendations and baselines are built from months of aggregated shape. Full-resolution history is two months on both Operations and Intelligence — the extra six months is the rolled-up series, not raw samples.
- Do non-production environments count?
- Staging and DR instances are nodes, but they are exactly where volume banding helps — talk to us about how your estate is shaped before assuming.
- What happens if I replace a host?
- Licences are node-locked but releasable. Rebind the key to the new host — you are not buying a licence again.
- Can I buy services without the platform?
- Yes. DBChefs engagements stand on their own, with or without SchemaPulse.
Tell us what you run
Send us your fleet size and the engines you run, and we will come back with a price and the plan we would actually recommend.