RELATIONAL
PostgreSQL
Primary application data
READY TO PROVISIONDatabases
Your database,already wired.
Ask for Postgres, Redis, Mongo or a vector store and it is set up on compute dedicated to you. Credentials, storage and connection details arrive with it.
PostgreSQLRelational READY · CREDENTIALS GENERATED
No database background needed
Just say what you need.
Tell your coding agent, or use the portal. PlugLayer creates the database, generates the credentials and connects it to the app that needs it.
Your data stays with youStandard enginesNo lock-in
your agent
Give the api a Postgres and wire it up.
- Postgres database created
- Credentials generated
- DATABASE_URL added to api
orders-db · ready Connected
In the portal
Four steps from nothing to a database.
Prefer to click? The portal walks you through it, and checks it fits your compute before anything is created.
Search databases by name or engine…
PostgreSQLRelational
RedisCache / key-value
MongoDBDocument
QdrantVectorAdd a database
Or ask your coding agent to do it for you.
Every engine
Postgres, Mongo, Redis, Qdrant … and any open source.
Pick a database
Pick the shape of the data.
Vetted templates with operational defaults, not a directory of containers.
CACHE / KV
Redis
Sessions, queues, hot paths
READY TO PROVISIONDOCUMENT
MongoDB
Flexible product data
READY TO PROVISIONVECTOR
Qdrant
Embeddings and retrieval
READY TO PROVISIONANY CONTAINER
…and any open source
MySQL, MariaDB, ClickHouse and the rest, run as an app
RUNS AS AN APPThe portal shows the current catalog, and whether it fits your compute, before anything is created.
Not on the list?
Any open-source database that runs in a container runs here.
The engines above are managed for you: credentials generated, storage attached and connection details delivered. For anything else, such as MySQL, MariaDB or ClickHouse, deploy its image or compose file as an app, give it storage, and point your other apps at it. It runs on your dedicated compute like everything else.
Connected for you
No credential scavenger hunt.
The database and your app live in the same project, so connecting them is one action, not a value copied between browser tabs.
api / production.env SYNCED
DATABASE_URL=postgresql://app:••••••••@orders-db:5432/app
POSTGRES_HOST=orders-db
POSTGRES_PORT=5432
POSTGRES_DB=app
POSTGRES_USER=app
POSTGRES_PASSWORD=••••••••••••••••After launch
Still in your hands.
Each database has its own page: connection details and docs, who is allowed to connect, logs, restart, and remove. Nothing is hidden behind a support ticket.
Connection detailsIP allowlistLogs and restartYour data stays with you
orders-db · PostgreSQL Ready
Connection details
DATABASE_URL
postgresql://app:••••••••@orders-db:5432/appHost
orders-dbPort
5432Password
••••••••••••IP allowlist · 1 address
LogsRestartDocsRemove
Add the database. Skip the plumbing.
Choose an engine, connect it to an app, and let PlugLayer handle the operational middle. Ask your agent or use the portal.