Skip to main content

​
Deploying with a Database

When deploying an app that uses a database, Monk detects it automatically:
Monk: “I detected your app uses PostgreSQL. How should I deploy it?”
  • Self-hosted (container)
  • Cloud-managed (RDS, Cloud SQL)
  • Third-party (Neon, Supabase)
→ Databases

​
Choose Deployment Option

Tell Monk your preference:
Switch between self-hosted, cloud-managed, or third-party managed.

​
Deploying with Redis

If your app uses Redis for caching or sessions, Monk detects it:
Monk: “I detected Redis. How should I deploy it?”
  • Self-hosted (container)
  • Redis Cloud (managed)

​
Deploying with Message Queues

If your app uses a message queue (RabbitMQ, Kafka, SQS), Monk detects and asks:
Monk: “Your app uses RabbitMQ. Self-hosted or managed service?” → Essential Services

​
Configure Database Settings

Adjust database configuration. → Configuration & Wiring

​
Resize Database

Scale database resources.

​
Add Object Storage

Add object storage for files and assets.

​
Backup Database

Create on-demand backups of your database.
List all database backups and snapshots. → Backup & Restore Guide

​
What Monk Asks

Deployment choice:
  • Self-hosted in container?
  • Cloud-managed (RDS, Cloud SQL)?
  • Third-party (MongoDB Atlas, Redis Cloud)?
Credentials:
  • For managed services: Provider credentials
  • For third-party: Service API keys
→ Obtaining Credentials for setup guides

​
Database Options

Relational:
  • PostgreSQL
  • MySQL
  • MariaDB
NoSQL: Others:
  • Elasticsearch
  • TimescaleDB
  • And 20+ more
→ See all supported databases

​
Next Steps