Skip to main content

​
Deploying with a Database

When deploying an app that uses a database, Monk detects it automatically: 
deploy this project
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: 
use MongoDB Atlas instead of self-hosted

use AWS RDS for PostgreSQL
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: 
deploy this project
Monk: “I detected Redis. How should I deploy it?”
  • Self-hosted (container)
  • Redis Cloud (managed)
use Redis Cloud instead of self-hosted

​
Deploying with Message Queues

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

​
Configure Database Settings

change the database connection pool size to 20
Adjust database configuration. → Configuration & Wiring

​
Resize Database

increase database RAM to 16GB
Scale database resources.

​
Add Object Storage

add S3 for file uploads
Add object storage for files and assets.

​
Backup Database

back up my database
Create on-demand backups of your database. 
show me available backups
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