Features
Capabilities that exist in the product
This list matches the running Zinprex application. Planned collectors and dedicated instances are labeled as such — they are not sold as current features.
PostgreSQL databases
- One isolated database and role per project on a shared cluster
- Ready state before connection details are treated as usable
- Credential rotation generated by the server
- Delete deprovisions the database and role
Instant provisioning
- Create project from the dashboard
- Provisioning SQL is isolated in a backend module
- Idempotency keys prevent double-create races
- Failed provisionings surface as failed — not as a fake ready database
Connection strings
- Host, port, database, user, password, ssl flag
- Copy from the dashboard
- Same payload via GET /v1/databases/:id/connection
- Requires databases:connect; databases:read is metadata only
API access
- Account-scoped keys, hashed at rest, shown once
- Scopes for projects, database metadata, connect, data read/write
- Parameterized data API on public tables
- No raw SQL, no control-plane access, no management routes
Usage visibility
- Storage from pg_database_size on ready databases
- Account-level allowance, not per database
- Dashboard shows not-measured instead of fake 0 MB
- Bandwidth and compute collectors are not implemented
Credits and billing
- Prepaid wallet on the account
- Catalog prices for extra solo projects, agency conversion, agency creates
- Bank transfer purchase, pending until confirmed
- No card gateway in v1
Details live in documentation. Limits and credit amounts are on pricing.