monkMonk or a deployment platform?
A hosted platform bundles deployment with infrastructure it operates. Monk runs through your coding agent and creates resources in your cloud account. Choose the responsibility model that fits your app.
A deployment platform fits when…
Your app fits the platform’s services and regions, and you value a managed hosting experience with an integrated deployment workflow.
Monk fits when…
You need resources in your own cloud account and want Monk to manage the application and supported services together.
Try it alongside your current setupWhat changes for your team
| Responsibility | a deployment platform | Monk |
|---|---|---|
| Deploy | Connect source or images and configure the platform’s services. Platforms can provide builds, networking and previews. | Plans the app, infrastructure and service connections. Deploys after the required approvals. |
| System model | The platform tracks its resources and releases. External dependencies may use separate tools and accounts. | The orchestrator retains the application and resource model across agent sessions. |
| Operations | The provider runs its platform and offers service-specific recovery and monitoring. Capabilities vary by vendor and plan. | Configured workload recovery is automatic. Watcher diagnoses persistent issues and proposes fixes for approval. |
| Controls | Platform roles, deployment settings and approvals depend on the provider and plan. | The orchestrator enforces permissions and validation. Deployment plans have a separate approval screen. |
| Existing apps | Move source, configuration and data into the platform. Evaluate its export and migration options too. | Start with a separate deployment from source. Plan data transfer and traffic cutover explicitly. |
| Bill | The hosting provider bills for its services; external services can have separate bills. | Your cloud bills you directly. Monk and your coding agent are separate costs. |
Sources and comparison scope
Comparison baseline reviewed 12 September 2026. Workflow comparison, not a performance benchmark. Capabilities depend on configuration and plan. Primary documentation is linked below.
Give both the same job.
Deploy a frontend, API, database, export worker and storage. Create a task, run an export and retrieve the file.
With a deployment platform
Create web, API, database, job and storage services using the platform’s supported options. Configure their connections and deployment settings. Check where any external resources live, then test the same task-to-CSV workflow.
With Monk
Ask Monk to plan the app and its dependencies. Review resources, credentials and costs, then approve deployment. Create a task and retrieve its exported CSV. For an existing app, start in a separate environment.
Before you switch.
Owning the cloud account adds responsibilities: provider access, quotas, data policies and billing. Monk’s supported integrations are not a guarantee that every app can move unchanged between providers.
Can I evaluate Monk without replacing production?
Monk builds fresh infrastructure from your codebase. Your existing deployment stays untouched. Test the new environment before you switch. Allow for duplicate cloud costs during evaluation. Data transfer and cutover are separate decisions.
Will Monk take over my current infrastructure?
The default path is a new deployment from source. Do not have two infrastructure controllers manage the same resource. Keep ownership boundaries explicit during evaluation.
Try it with your application.
Start from your repository. Review the resources and costs before you deploy.