Databases and APIs

Real Postgres, defined over an API.

Describe your tables and JSONB collections once and get a real database with real constraints and indexes, read and written with a project key instead of a database account per app.

Service running, console unfinished. Schemas, constraints, indexes and per environment keys all work through the API. The console you would use to drive it is still being built, and the name above is a placeholder. There is no billing on this platform yet, so nothing can be bought and nothing here has a customer.

Tell us what you would need See the whole platform

What it does

Tables and collections, defined over HTTP

Declare a typed table or a JSONB collection through the API and get Postgres underneath it, with the constraints and indexes you asked for rather than a document store wearing a schema.

A project key, not a database account

Read and write with one key scoped to the project. Nothing has to hand out a database login per application, and a hostile schema definition is refused rather than escaped.

Environments that cannot reach each other

Development, staging and production are separate schemas with separate keys, so a key that leaks out of one cannot read another.

Not built yet

Named rather than left out.

The console

The service answers, and the screens for driving it are still being finished.

A settled name

The working name was dropped after a trademark search found a live earlier claim. A replacement has not been chosen.

Billing

There is no way to pay for anything on this platform.

Built on one control plane

Data Platform shares an account, a project and a bill with Monitor, Analytics and the rest. Two tools that already agree on what a release is beat two tools you reconcile by hand.