Skip to main content
Real apps need more than their own code: a database, a cache, object storage, a login provider, a payment provider. Wiring each one means credentials, networking and config in several places. With Monk you ask for the service. It goes into the same plan as your app and is connected to the services that use it.

​
What you can do

​
Run a service yourself or use a managed one

Many services come both ways. Self-hosted packages run as containers on your cluster, with more than 20 databases and services available. Managed services are created in the provider’s account through its API, using your credentials for that provider. How: Ask Monk. You approve the plan in the local dashboard. See Add a database and MongoDB Atlas.

​
Choose from a wide catalog

Examples of what Monk can create and connect:
  • Databases: AWS RDS, DynamoDB, Google Cloud SQL, Firestore, Azure PostgreSQL, Cosmos DB, DigitalOcean Managed Databases, MongoDB Atlas, Neon, Supabase, Redis Cloud, Upstash
  • Storage: S3, Google Cloud Storage, Azure Blob, DigitalOcean Spaces, Cloudflare R2
  • Queues and messaging: SQS, SNS, Pub/Sub, Azure Service Bus, Resend for email
  • Auth: Auth0, Clerk, WorkOS, Cognito
  • Payments: Stripe
  • DNS and CDN: Route 53, CloudFront, Cloud DNS, Cloudflare
  • Hosting: Vercel, Netlify, Firebase Hosting, Cloudflare Pages
The full list is on monk.io/integrations. How: Ask Monk. See Services and data.

​
Get connections and secrets wired

Your services connect to a database or API through Monk connections, not hard-coded hostnames. Monk passes the endpoint and generated secrets, such as a database password, to the services that use them. Secrets only you can provide, such as an API key, are entered in a form in the local dashboard and stored in your OS keychain. Monk pushes them to the cluster when a deploy needs them. How: Ask Monk, with the value entered in the local dashboard. Cluster secrets need your approval. See Secrets and config.

​
Keep Auth0 and Stripe settings in sync

Auth0 callback URLs and Stripe webhook endpoints are declared in your Monk config and applied again on every deploy, so they follow the app. Signing secrets are stored as Monk secrets. How: In your Monk config, written by your coding agent and deployed after a plan review. See Services and data.

​
Back up and restore managed databases

For AWS RDS, MongoDB Atlas, Google Cloud SQL and DigitalOcean databases, Monk can create a snapshot, list backups, restore and check restore status. How: Ask Monk. You approve each action in the local dashboard. See Back up and restore.

​
Try it

​
Good to know

  • Monk does not move data between databases. Switching a database points the app at the new one. Copying data is a separate step.
  • Backup actions cover the services listed above. Self-hosted databases have none unless their template provides one.
  • Managed services are billed by the provider, on top of your cluster.

Add a database

Self-hosted or managed

MongoDB Atlas

Atlas, DigitalOcean or a container

Secrets and config

Keys and settings your app needs

Back up and restore

Snapshots and restores

Services and data

Packages, entities and limits