Skip to content
    monk.io
    Get startedStart

    Deploy alongside your app.

    Monk builds fresh infrastructure from your codebase. Your existing deployment stays untouched. Test the new environment before you switch.

    Deploy alongside my app

    Start with plugin setup and a reviewed plan.

    I’m starting a new app

    Try a new environment.
    Keep serving customers.

    The new deployment gets fresh infrastructure. Your current app, database and traffic stay where they are. Source code alone cannot recreate production data, undocumented settings or external account state.

    Transfer data and switch traffic only after testing, as separate reviewed steps. Both environments incur cloud costs while they run.

    Start with a repository assessment

    After setup, use this request to discuss the work before deploying:

    Review this repository for running with Monk. List the services, unsupported dependencies and migration steps. Do not provision, deploy or change resources.

    Bring your app.

    HTTP services, workers and jobs, databases and storage. Cloud infrastructure on AWS, Google Cloud, Azure, DigitalOcean, Hetzner.

    You’ll need repository access, a Monk account and provider permissions. Support depends on the selected integration and region. See services and custom integrations.

    Set up Monk in your coding agent.

    You’ll need a Monk account, access to your repository and credentials for the cloud you choose. On your phone? Save this page and continue on your development machine.

    1. Install the plugin for Claude Code

      Add the marketplace

      /plugin marketplace add monk-io/monk-plugin

      Install the plugin

      /plugin install monk@monk-plugins

      Reload plugins

      /reload-plugins

      Paste these into Claude Code in order. Restart the host if reload is unavailable.

      Restart or reload the host after installation. Full installation instructions.

    2. Connect your Monk account

      The plugin opens a browser sign-in on first use. You can also create your account here, then return to these instructions with your starting point and agent choice saved in the link.

      Create account or sign in

    3. Open your app and ask for a plan

      Use Monk to plan a new, separate environment for this repository in my cloud account. Leave my existing deployment untouched. List missing settings, data migration steps and estimated costs. Wait for my approval before provisioning.

    4. Review, deploy and verify

      Provide credentials in Monk’s local credential form. Review resource changes, warnings and cost estimates in its approval screen. Approve when ready, follow progress and test a complete app workflow.

      You can decline the plan and request changes before provisioning. If deployment fails, inspect the status and logs before retrying; check for resources that were already created.

    If setup needs attention.

    Monk does not appear in my agent

    Complete both marketplace registration and plugin installation. Reload or restart the host, then check that the monk MCP server is enabled. Follow the plugin’s installation guide for your host.

    The plugin asks me to authenticate again

    Website sign-in and the plugin’s MCP authorization are separate steps. Complete the browser sign-in opened by your coding agent. Do not paste tokens or cloud credentials into the conversation.

    My stack or provider is not supported

    Ask for the unsupported dependencies and the proposed alternatives before approving a deployment. Contact support@monk.io with the component names and error message, leaving secrets out.

    A credential or approval is missing

    Return to the local Monk approval or credential form linked by the agent. Supply the requested information there, or decline and revise the plan. Review the status before starting another deployment.