PostgreSQL that fails over on its own.
Three-node clusters with automatic failover and restore to any second in seven days, where you choose, private by default.
Quoted per sizeFree tier: one shared-CPU database[1]
On your own devices or ours, inside your private cloud's own network. Billed by the hour, no minimum term.
What you get
Four things to know.
- Application databases
- Document stores
- Analytics copies
- Dev and test
PostgreSQL 17 and FerretDB 2.7
FerretDB speaks the MongoDB wire protocol on top of PostgreSQL.
Three nodes, automatic failover
High-availability mode runs Patroni. Standalone mode for dev and test.
Restore to any second in 7 days
Continuous WAL archiving. Backups are kept in a separate region.
Private by default
A private endpoint inside your network. A public endpoint is optional, chosen at creation.
Price
Modes
| Mode | Nodes | Use |
|---|---|---|
| Standalone | 1 | Development and testing |
| High availability | 3 | Production, automatic failover |
Sizes list vCPU, memory and disk; each is quoted in writing. Leave any time with pg_dump or mongodump.[1]
Not yet
- MySQL and Redis are coming; no date is published.
- No read replicas yet. Retention is fixed at 7 days.
Where it runs
On our nodes or your own devices, inside your private cloud's own network. If a node fails, work moves across the network under the policy you set.
Get started
Start on the free tier today.
Or talk to Triple X about running it on your own devices.
- 01
Join the waitlist.
Tell us what you want to run and where. No credit card.
TakesTwo minutes
- 02
Create a database.
PostgreSQL 17, backed up, with a 7-day restore.
TakesMinutes
- 03
Bring your own servers.
Triple X sets up your private cloud on them.
WhoTriple X
We never ask for your root credentials, API keys or bank details by email.
All productsAt a glance
The numbers a buyer asks for.
Engines, failover, restore and exit for a managed database, each with where to check.
| What | Triple X Cloud | Where to verify |
|---|---|---|
| Engines | PostgreSQL 17 and FerretDB 2.7 | Docs, August 1, 2026 |
| Price | Quoted per size, in writing | Your quote from Triple X |
| High availability | Three nodes, Patroni, automatic failover | Docs, databases overview |
| Restore | Any second in the last 7 days | Docs, point-in-time restore |
| Backup location | A separate region | Docs, databases overview |
| Endpoint | Private by default; public optional | The create screen |
| Free tier | One shared-CPU database, 256 MB | Pricing page |
| Exit | pg_dump or mongodump; transfer from $0.01 per GB | Docs and Pricing page |
Questions
What buyers ask before they sign.
In the order they come up. Every answer ends with where to check it.
10 answers
All questionsIs it real PostgreSQL, and what about MongoDB?
PostgreSQL 17 on port 5432, with psql and the usual drivers. FerretDB 2.7 speaks the MongoDB wire protocol on top of PostgreSQL, so mongosh and pymongo connect. Check FerretDB's compatibility notes against your queries.
Proofthe managed databases overview, August 1, 2026.[1]
What does a database cost?
Sizes list vCPU, memory and disk, and each is quoted in writing; no public rate is published. The free tier includes one database on shared CPU with 256 MB. Billing is hourly with no minimum term.
Proofa written quote from Triple X and the free tier in the published pricing.[2]
What does it cost to leave?
Outbound transfer from $0.01 per GB and nothing else. Leave with pg_dump or mongodump at any time; the formats are standard and any PostgreSQL or MongoDB host reads them. No exit fee, no minimum term.
Proofthe transfer bands in the published pricing and the exit tools named in the documentation.[1]
Who can reach my database?
Only clients inside your private cloud's own network, by default. A public endpoint is optional and chosen at creation. The platform underneath sees that a cluster exists, its size and its cost, not your rows. Operator actions are logged.
Proofthe private-endpoint default in the documentation and the access table on the Security page.[1]
Can the cluster run on my own servers?
Yes. Three nodes on devices you own, inside your private cloud, with the same console and API. Backups are kept in a separate region, so plan a second site or hosted capacity for them. Triple X quotes it in writing.
Proofthe Sovereign page and a written quote from Triple X for your private cloud.
Where does it run, and where do backups go?
In the region you pick at creation, on your devices or on hosted nodes. Backups are kept in a separate region by design. If a residency rule limits where backups may sit, say so before creation.
Proofthe backup location statement in the documentation, August 1, 2026.[1]
What happens when a node fails?
In high-availability mode, three nodes run Patroni and a replica takes over on its own. Continuous WAL archiving lets you restore to any second in the last seven days, into a new database, while the source keeps running.
Proofthe failover and point-in-time restore guides in the documentation.[1]
What proof exists behind it?
A SOC 2 Type II examination with an unqualified opinion, period November 1, 2025 to January 30, 2026, no exceptions noted, under NDA. A HIPAA business associate agreement is available for covered workloads. Test a restore yourself on the free tier.
Proofthe SOC 2 Type II report under NDA and the Security page.[3]
How do I start, and what do I need?
Create an account, pick standalone for dev and test or high availability for production, and connect from inside your private cloud. You need a client such as psql or mongosh and a machine or cluster in the same network.
Proofthe create-database flow in the documentation, August 1, 2026.[1]
What is not included yet?
MySQL and Redis are coming, with no date published. No read replicas yet. Retention is fixed at seven days, so export older restore points yourself. Public rates are not published; sizes are quoted in writing.
Proofthe Not yet list on this page, checked October 2026.
No questions under this term yet. Ask Triple X.