Skip to content

    Your stack.
    Connected.

    Cloud services and software running on your machines, operated together. Connect managed services or deploy databases, queues and tools from Monk’s runnable packages.

    Connect your coding agent

    Start in your coding agent.

    Find your integrations.

    Entities operate resources through provider APIs. Runnables deploy software onto your compute. Both become part of the same application model.

    Cloud accounts

    Provision compute in your own account. Choose the provider, region and machine in the plan.

    Application services

    Databases, identity, payments and hosting, connected to the rest of your application.

    AWS services

    Managed resources operated through Monk entity packages, using your AWS permissions.

    Google Cloud services

    Managed data, serverless compute, networking and identity in the GCP entity package.

    Azure services

    Managed storage, data and messaging through Azure entity packages.

    DigitalOcean services

    Managed resources alongside the Droplets running your application.

    Development workflow

    Connect your release process, private images and operational notifications.

    Databases & storage

    Run databases, caches, search engines and object storage on your own compute.

    Data pipelines & analytics

    Move data, coordinate workflows, publish APIs and explore business metrics.

    AI & vector search

    Host models, store embeddings and observe LLM applications.

    Content & collaboration

    Self-host publishing, customer support, internal tools and team applications.

    Development tools

    Run source control, CI servers, artifact repositories and database administration tools.

    Networking & security

    Web serving, traffic routing, service coordination, identity and secrets on your infrastructure.

    Monitoring & logs

    Collect metrics and logs, monitor networks and build operational dashboards.

    One application.
    Your accounts.

    Connect credentials through Monk’s local forms. Cloud and service permissions determine what Monk can operate; provider bills stay with the provider.

    Entities manage provider resources through APIs. Runnables define software that Monk runs on your compute, with configuration, connections and storage. Your agent can inspect either package before proposing a deployment.

    How access and approvals work

    Bring the app you’re building.

    Monk finds what it needs to run, and prepares the next step.

    Get started