Skip to main content
Add a database, cache or message queue to your app. You choose whether it runs as a container on your cluster or as a managed service in a provider account.

​
Before you start

  • Your app is deployed, or you have a plan. See Deploy an existing app.
  • For a managed service, an account with that provider. Monk asks for its credentials through a form.

​
Ask Monk

If your code already uses a database, Monk finds it when it plans:
To add one, or to pick how it runs, say so:
Your coding agent adds any code the app needs to use the new service. Monk adds the service to the MANIFEST and connects it.

​
Self-hosted or managed

See the integrations catalog for what Monk can run.

​
What you review

The plan in the local dashboard shows the new service, its size, which services connect to it and the estimated cost. Database passwords are generated or entered through a secret form, never in chat. Nothing is created until you approve.

​
What you get

  • The database running, self-hosted or managed
  • Connection settings (host, port, user, password or a connection string) injected into the services that use it
  • The database in Monk’s model of your app, so later requests about logs, backups or costs include it

​
Limits

  • Monk does not move data between databases. Copying data from an old database is a separate step. See Back up and restore.
  • Self-hosted databases have no automatic backups unless you add them.

​
Next