Simple pricing. Serious tooling.
Per-database for Starter and Team. Fleet-wide coverage at enterprise scale. All read replicas included, regardless of how many are running.
- →Autonomous monitoring and investigation. Root cause analysis delivered to your team.
- →Observability ingest. Datadog, CloudWatch, Performance Insights, Prometheus.
- →Slack and Teams. Findings posted where your engineers already work.
- →Execution with approval. SIXTA proposes, you approve, SIXTA executes.
- →Automated runbooks. Proactive remediation across the fleet.
- →Incident workflow. PagerDuty, Jira, OpsGenie.
- →ServiceNow, native. Incidents, problems, changes, and bi-directional CMDB sync.
- →Segregation of duties. Fine-grained access controls for regulated environments.
- →Named reliability partner. A dedicated DBRE, with SLA.
| Starter | Team | Enterprise | |
|---|---|---|---|
| Autonomy | Observe and recommend | Act with approval | Policy-driven automation |
| Integrations | Slack, Teams, Datadog, CloudWatch, Prometheus | + PagerDuty, Jira, OpsGenie | + ServiceNow, CMDB |
| Governance | Admin and member roles | Role-based, per environment | Segregation of duties, SSO/SAML/SCIM |
What a Team deployment actually costs.
A mid-sized deployment running 80 production writers across MySQL and PostgreSQL, each with around 4 read replicas on average.
Fleet-wide coverage, priced to your operations.
When your estate reaches hundreds of databases, per-database pricing stops making sense. Most of your fleet is automated. Your DBA team is small relative to the estate they cover. Your budget is measured in headcount, not database count.
We price SIXTA to the operational reality of your team, not the number of databases in your inventory. One agreement covers your entire fleet.
Your Enterprise agreement is scoped to your environment and requirements.
- →Full fleet coverage regardless of database count
- →Production and non-production included
- →ServiceNow, native for incidents, problems, and change records
- →Audit-ready history of changes, risk assessments, and remediation
- →SLA with guaranteed response times and named reliability partner
What database operations costs today.
The status quo is expensive. SIXTA reduces the manual investigation work that consumes your DBA's time, makes your monitoring more useful, and shortens the incidents your tools alert you to.
Build SIXTA around your environment.
The three tiers above are the commercial path. Design partnership is something different: a co-development relationship where you get a senior DBRE built around your specific problems, and we get the deep operational learning that makes the product better for everyone.
Spots open quarterly. We onboard a small number of partners at a time so each one gets the founding team's full attention.
- →Full platform access. Root cause analysis, proactive detection, and the trust progression in production.
- →Direct line to engineering. Weekly syncs with the team building the product. Your incidents become our roadmap.
- →Deploys inside your infrastructure. Your data never leaves your network. Read-only database access by default.
- →Partnership pricing. Locked in for the duration of the partnership. We'll share specifics on a call.
“SIXTA helped me to spot a vacuum to prevent wraparound before static alerts. What can I say besides it works when I need and hides when I focused on other tasks.”
Database Reliability Architect, AB InBev
Common questions.
How is pricing calculated?
Starter and Team are priced per primary database per month, for fleets up to 500 primary databases. Above 500, Enterprise fleet pricing covers your entire estate. Predictable, per-database pricing.
What counts as a database?
Each primary (writer) instance counts as one database. All associated read replicas are included regardless of how many are running, including auto-scaled replicas. Sharded keyspaces count as one database. For large sharded estates, Enterprise fleet pricing applies. You pay for the workload, not the infrastructure that serves it.
Do non-production databases cost the same?
No. Per-database plans offer staging, development, and test databases at significantly reduced rates. Fleet-wide enterprise agreements include all environments.
Can I start with a pilot?
Yes. We offer 60 to 90 day paid pilots on a limited set of production databases. Pilot fees are credited 100% against your first annual contract.
Are you still taking design partners?
Yes, selectively. Spots open quarterly and we onboard a small number of partners at a time. Partners get direct access to the founding team, weekly syncs, partnership pricing locked for the duration, and meaningful influence over the roadmap. If you're running PostgreSQL or MySQL at scale and have a specific problem you'd like SIXTA built around, talk to us.
How does pricing work for large fleets?
Up to 500 primary databases, per-writer pricing with volume discounts. Above 500, fleet-wide coverage priced to your operational needs rather than database count. Talk to us and we will find the right fit.
Is there a free tier?
No — Starter has a monthly entry point at $40/database. Self-serve Starter is in early access with design partners; join the beta to get notified.
What databases do you support?
MySQL and PostgreSQL today, including managed services like RDS, Aurora, Cloud SQL, and AlloyDB. Additional engines are on the roadmap.
How long does setup take?
Initial connection and baseline monitoring can be running within days. SIXTA's understanding of your environment deepens over the first few weeks as it learns your topology and patterns.
See SIXTA in your environment.
We'll onboard SIXTA into your Slack or Teams, connect it to your databases, and show you what autonomous database reliability looks like in practice.