
Start with one table. We will help.
ColdCTL is in early access. We are working with a small number of PostgreSQL teams to run their first archives together and measure the space they get back.
Early access program
For teams on PostgreSQL with tables that keep growing.
- The full agent, Archive Gateway and Cloud dashboard
- Hands-on help planning and running your first archive
- A direct line to the engineers building it
- Before-and-after measurement of size and cost
- Influence over what we build next
Team and Enterprise
Public plans will follow once early partners are in production.
- MySQL and MongoDB alongside PostgreSQL
- Team invites, roles and alerts
- SQL access to archived data
- Retention rules and legal hold
A great fit if you…
- Run PostgreSQL on RDS, Aurora, Cloud SQL or your own servers
- Have tables in the hundreds of gigabytes that keep growing
- Must keep old records for audits, support or compliance
Probably not yet if you…
- Need SQL Server or Oracle today
- Need certified legal-hold storage on day one
- Want a fully managed service that hosts your archives
Estimate the storage tradeoff.
Start with an illustrative 10 TB database (10,000 GB), 70% cold data and an archive half the source size. Replace the rates with your RDS, Aurora or other provider bill and use a measured archive ratio. These are hypothetical rates, not a provider quote or guaranteed savings.
Deleting records does not automatically shrink provisioned storage or reduce your bill. This excludes gateway compute, temporary disk, requests, retrieval, egress, replicas, backups, software fees and operational costs. No inputs are submitted.
About early access.
How does pricing work during early access?
Terms are agreed with each design partner directly. Public plans have not been announced yet.
When will public plans be announced?
After the first design partners are running ColdCTL in production. Partners will hear first.
What do we need to get started?
A PostgreSQL database with a large table of old, rarely-changed rows, a bucket in S3, Azure or Google Cloud, and a Linux or Windows server or container to run the agent.