Postgres that thins its own history and tells you what happens next.
A managed Postgres database with horizon tables: time-series tables bounded in both directions. Old rows downsample themselves as they age. Future rows are forecast ahead and scored against what actually arrives.
Horizon tables
One statement, in both directions of time
A horizon table covers unbounded history in finite space. Tiered policies thin old chunks to coarser resolutions — raw, then five-minute, then hourly, then daily — so a query across years stays cheap while this week stays exact.
-- turn an ordinary table into a horizon table SELECT chrono.create_horizon_table('readings', 'ts'); -- history thins itself: 5m after 7d, 1h after 30d, 1d after a year -- future arrives paired: readings_predictions, 7 days ahead SELECT * FROM chrono.prediction_accuracy; -- error_rate_pct — forecasts scored as the real rows land
Continuous aggregates you configure and maintain are a different shape of answer. Here retention, downsampling and forecasting are properties of the table, and the error rate is a column you can query rather than a claim in a benchmark.
Also included
Vector search
pgvector with HNSW and IVFFlat. Embeddings sit beside the rows they describe, in the same transaction, with no second datastore to keep in sync.
Event streaming
A transactional outbox with change-data-capture triggers, so a committed write can drive other systems without a dual write.
A database, not a tenant in one
Every account gets its own isolated Postgres database with its own role and connection string. Standard wire protocol — your existing driver, psql, and migration tool all work unchanged.
Plans
| Plan | Price | Devices | Storage | Status |
|---|---|---|---|---|
| Loading plans… | ||||
Every account is set up by hand, so the free tier is by request rather than instant. The paid tiers are priced but not yet purchasable — checkout is not switched on. If one of them is the size you need, say so in your request; you will not be charged in the meantime.
Plan details could not be loaded just now. Every tier is by request; the paid ones are not yet purchasable.
What you actually get today
Managed PostgreSQL 18, provisioned for you as an isolated
database. The Postfinite engine — chrono horizon tables,
postfinite_auth, postfinite_nats — is applied to it as
schema. Self-hosting the engine as native extensions, on the PostgreSQL 18.4
fork, is the other way to run it.
There is no documentation site yet, and nothing here is charging money. Accounts are opened by invitation — ask for one and a person reads it. If you would rather talk first, the address below reaches the same person.