PlugLayer Data Layer

Your database,already wired.

Launch a production-ready data service on PlugLayer compute. Credentials, persistent storage, service discovery, and app environment variables arrive with it.

PG READY
APIDATABASE_URL
WORKERDATABASE_URL
CREDENTIALS · GENERATED

Service catalog

Pick the shape of the data.

Vetted templates with operational defaults, not a directory of containers.

PG

RELATIONAL

PostgreSQL

Primary application data

READY TO PROVISION
RD

CACHE / KV

Redis

Sessions, queues, hot paths

READY TO PROVISION
MG

DOCUMENT

MongoDB

Flexible product data

READY TO PROVISION
CH

ANALYTICS

ClickHouse

High-volume analytical reads

READY TO PROVISION
QD

VECTOR

Qdrant

Embeddings and retrieval

READY TO PROVISION
MI

OBJECT

MinIO

S3-compatible file storage

READY TO PROVISION

MySQL, MariaDB, and more are available in the live catalog.

Connection contract

No credential scavenger hunt.

The data service and the application share a project model, so the connection is an intentional product action—not a value copied between browser tabs.

api / production.env SYNCED
DATABASE_URL=postgresql://app:••••••••@orders-db:5432/app
POSTGRES_HOST=orders-db.project.svc
POSTGRES_PORT=5432
POSTGRES_DB=app
POSTGRES_USER=app
POSTGRES_PASSWORD=••••••••••••••••

One data-service lifecycle

01

Provision

Choose an engine. PlugLayer creates the service, storage, network identity, and credentials.

02

Connect

Pick the apps that need it. The correct connection variables land in the correct environments.

03

Operate

Inspect logs, restart, change access, retrieve credentials, or remove it from the same project.

Add the database. Skip the plumbing.

Choose an engine, connect it to an app, and let PlugLayer handle the operational middle.