Attached services (databases, caches, queues)

Apps need stuff. Suzko Deploy provisions and manages it.

Available

Service	Purpose
Postgres	Relational DB. Pick a version (15, 16, 17).
MySQL / MariaDB	Relational DB.
Redis	In-memory cache + key-value.
MongoDB	Document DB.
RabbitMQ	Message broker.
Meilisearch	Search engine.
MinIO	S3-compatible object store (use Cloud Storage for prod).
ClickHouse	Analytics DB.

Provisioning

/tools/deploy/ → Services → Add service → pick → pick tier → Provision.

We:

1. Spin up a managed container for the service.
2. Auto-generate strong credentials.
3. Inject the connection string as an env var:
   • Postgres → DATABASE_URL
   • MySQL → DATABASE_URL
   • Redis → REDIS_URL
   • MongoDB → MONGO_URL
   • RabbitMQ → RABBITMQ_URL
   • Custom name available too
4. Restart your app container so the var takes effect.

Connection details

Click the service → Connection to see:

• Internal connection string (only your project can reach it — use this from your app)
• External connection string (for migrations from your laptop — rotates the password if you regenerate)
• Direct host + port + creds for advanced use

Backups

• Postgres / MySQL — automatic daily backups, kept 7 days.
• Redis — backups optional (Redis is usually cache; persist if you need it).
• MongoDB / others — automatic daily.

Restore from backup: Backups → Restore on the service page. Pick the snapshot, confirm. App restarts with the restored data.

Connecting from outside

Useful for migrations or local dev. Get the external connection string. By default external access is off — toggle on, IP- allowlist your IP, then connect.

Costs

Attached services bill on the same usage cycle as Deploy. Tier pricing on each service page.

Removing

Services → Remove on the service. Data deletes. There's no "soft delete" — backups too. Export anything you need first.