Databases & projects
How databases, projects, and organizations are organized on Silos.
Silos organizes your resources into a simple hierarchy. Understanding it makes the CLI, the Console, and the REST API feel consistent — they all operate on the same objects.
The hierarchy
Organization
The top-level account that owns projects, members, and billing.
Project
A grouping of databases. Projects are the unit the REST API creates databases under.
Database
A real PostgreSQL database, served on demand from snapshot + WAL storage.
Branch
A copy-on-write fork of a database, with its own endpoint.
Databases
A database is the core resource. Each one is a real PostgreSQL database whose durable
state lives as compressed snapshots and WAL segments in object storage, materialized
into a runtime when something queries it. Every database starts with a primary branch
named main and gets a unique connection endpoint:
postgres://user:password@db-xxxx.silos.sh/main?sslmode=requireCreate, list, and manage databases with the CLI:
silos db create my-app
silos db list
silos db connection-string my-appProjects
Projects group related databases. The REST API creates databases under a project, which is why the create endpoint is nested:
curl -X POST "https://api.silos.sh/v1/projects/{project_id}/databases" \
-H "Authorization: Bearer $SILOS_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "database": { "name": "my-app" } }'If you're migrating from Neon, this shape will look familiar — the Silos REST API is modeled on Neon's so that projects, databases, branches, and endpoints map cleanly. See the API reference.
Organizations
Your organization is the account that owns everything: projects, databases, members, API keys, and billing. Access control and billing are managed at the organization level.