Early access
Design partners, not a waitlist
We take on a small number of Postgres fleets at a time and work with each one directly. This page says exactly what that involves, on both sides, before you fill anything in.
What a pilot includes
A pilot is the whole product against your real fleet, not a sandbox with sample data. It runs for ninety days, and it ends with a written read-out of what we found, whether or not you carry on.
Discovery before monitoring
We point the agent at your fleet and it works out what each cluster actually is: engine and version, high-availability manager, pooler, backup tool, replication shape, extensions, and whatever monitoring you already run. Nobody fills in a form.
Detection tuned to your engines
Hundreds of rules, applied per engine rather than as one generic ruleset, because a managed service and a self-hosted cluster fail in different ways and expose different internals.
An advisor that shows its evidence
Index, query and schema advice arrives with the observation behind it and the expected effect, so your DBA can argue with it rather than guess at it.
Remediation at the rung you choose
Every pilot starts at observe. You move a class of action up the ladder when you have watched it be right often enough, and the policy gate refuses anything outside what you wrote down.
The detail behind each of those lives on the platform tour, and the shapes we discover are listed under topologies. One of those pilot weeks usually starts with indexing, which has a page of its own. Week one is mostly working out what you actually run, and teams who want their own assistant reading the result should start with what the gate lets one do. If your security team wants to read first, send them security and trust: connection model, what leaves the database, the signed ledger, and SOC 2-aligned controls with an audit underway.
What we ask from you
Design partner is a two-way word. We are asking for a path into production and for your time, and it is fair to say up front what that costs you.
- 01
A read-only role and a short install
A monitoring role on each cluster and an agent that runs inside your network. No superuser, no data egress beyond metadata and statistics.
- 02
One named owner on your side
Someone who knows the fleet and can say whether an alert was worth waking up for. Pilots without that person produce a dashboard nobody reads.
- 03
Blunt feedback, including the bad kind
We would rather hear that a detector is noisy in week one than read it in a churn note later. Design partners get changes shipped against their own findings.
Autonomy is earned during the pilot
The ladder has four rungs: observe, recommend, one-click, auto-apply. A pilot begins on the first, and nothing moves up because we think it is ready. You promote a class of action once you have watched it be right, and the fail-closed policy gate refuses anything you did not write down. Every action, approved or denied, lands in a signed ledger you can verify without asking us. We wrote about why we capped ourselves there on the engineering blog.
Commercial terms
There is no price list on this site while the product is in early access, and we would rather say that plainly than publish a number we would have to move. Design-partner terms are agreed per fleet, scoped to the size and shape of what you run, and they are settled after the pilot has shown you something, not before it starts. If a procurement process needs a figure earlier than that, say so in the form and we will get you one.
Who this is not for
- A single database rather than a fleet. The value here is comparison across clusters, and one cluster has nothing to compare against.
- MySQL, SQL Server or a mixed estate where Postgres is the minor part. We are Postgres-family only, on purpose.
- Teams who want an autonomous agent switched fully on from day one. Autonomy is earned here, and the first rung is watching.
If one of those is you, we will say so on the first call rather than spend ninety days proving it. There is a page for each role and each Postgres platform under solutions if you want to check the fit yourself first.
Apply for a pilot
Tell us what you run. An engineer reads it, replies within one business day, and either proposes a call or explains why we are not the right tool yet. If you would rather see the console before you talk about your fleet, ask for a demo through the contact page instead.