Skip to content
    monk.io
    Get startedStart

    What should your
    application do next?

    Put a whole app on Hetzner. Find GPUs where capacity is available. Give a branch its own stack. Monk connects the request to the system that can carry it out.

    See it in practiceCompare approaches
    Monk operates the system

    Your Hetzner account

    Load balancer + TLS
    App nodesFrontend · API · workers
    Stateful servicesPostgres · Redis · queue
    Persistent volumes · object storage

    Hetzner compute. The whole app, operated.

    Hetzner prices, with Postgres, Redis and the queue run for you.

    Read the Hetzner story
    Monk operates the system
    Cloudflare R2Models + checkpoints
    Keep regional volumes warm
    Region AWarm volumeReady for capacity
    Region BWarm volumeGPU pod running
    Region CWarm volumeReady for capacity

    Hunt for GPUs. Don’t hold them idle.

    Pods start where the GPUs are, and stop when the work does.

    Read the GPU story

    From the first deploy
    to the next change.

    Keep working in your coding agent. Monk maintains the application model, connects the services and carries out the operations you approve.

    Deploy your app in your cloud.

    From a repository to an app with its database, storage and service connections.

    Keep a small team’s app running.

    Inspect the system, recover workloads and review fixes without building a platform team first.

    Give each branch room to run.

    Test branches with their dependencies, without competing for one shared staging environment.

    Find your starting point.

    Developers using agents

    Your agent writes the application. Give it a way to deploy and operate the whole thing.

    Ship your app

    Small product teams

    Inspect services, scale workloads and investigate failures while the team keeps shipping.

    Operate with a small team

    Ops & platform teams

    Set access boundaries and approval rules. Give developers a controlled path to infrastructure.

    See the team workflow

    Try it with your application.

    Start from your repository. Review the resources and costs before you deploy.

    Bring an existing app Start a new app