Deployment and operations in your cloud

Your repo, live in your own cloud.

It reads your code, shows the plan and the monthly cost, and deploys to AWS, Google Cloud, Azure, DigitalOcean or your own server once you approve. No DevOps team needed.

Start free Watch the 1:42 tour Or let your AI agent deploy it →

100+people have signed up so far
500+deploys run so far
4 cloudsAWS, Google Cloud, Azure and DigitalOcean, always in your own account
Your own serverHostinger, GoDaddy or any Ubuntu or Debian VPS you already pay for
Open sourceMIT-licensed on GitHub: thedeployer-mcp deploy-check thedeployer-plugins

Deploys into your account on

AWS
Google Cloud
Microsoft Azure
DigitalOcean
Hetzner planned

Or onto a server you already have

Hostinger VPS
GoDaddy VPS
Any Ubuntu or Debian server

Four providers supported today, plus your own servers; features vary by provider. Support matrix.

01How it works

From repository to running app, step by step.

Every deploy runs the same way: it reads your code, shows the plan and its price, waits for your approval, then builds and deploys into your account.

Your repo is analyzed, read only

You see the plan and the monthly cost

You approve

It builds and deploys into AWS, Google Cloud, Azure, DigitalOcean or your own server

The app is live with HTTPS

thedploy / product tour

Sound on · captions

Fig. 01 The 1:42 product tour, recorded in a sandbox workspace with fictitious data. Each step jumps to its part of the video.

02AI agents · MCP

Or just ask your AI coding agent to put it online.

Connect Claude Code, Codex, Cursor or VS Code once. The agent fixes what would block a deploy, sets up the project, shows you the plan and its price, launches, and fixes what fails.

What stays with you: spending waits for your yes, credentials are entered in The Deployer and never in a chat, and deleting things, billing and team access stay in the app.

Claude Code

claude mcp add --transport http --scope user thedeployer https://app.thedploy.com/api/v1/mcp --header "Authorization: Bearer dpl_your_key"

Create an agent key Codex, Cursor, VS Code setup →

The MCP server is open source (MIT) and listed in the official MCP Registry. Plugins for Claude Code and Cursor: thedeployer-plugins.

your editor / AI agent

MCP

Put this app online in my DigitalOcean account.

check2 things would stop a deploy: no health route, binds localhost

fixAdded GET /health, listen on 0.0.0.0:$PORT · committed, pushed

setupProject created · 3 env values set

Two plans fit. One small server, about $6–12 a month, is enough for now. Launch it?

Yes, launch it.

liveDeployed · health check 200 · HTTPS on

Fig. 02 Illustration of an agent session. Prices come from the plans The Deployer proposes for your app.

03What it handles

The parts after the code works

Domains and HTTPSCustom domains with certificates. Some registrars need one guided DNS step.
Databases and servicesPostgres, Redis, queues, buckets and email, wired in with encrypted settings.
Health-gated redeploysOn server-based setups the old version serves until the new one passes its health check.
Logs and monitoringA log for every run, app health, uptime checks and server metrics.
Bounded recoveryCommon failures are diagnosed and retried a limited number of times. Some still need you.
Env vars and SSHChange environment variables, redeploy only what uses them, open a browser terminal.
Scaling and schedulesResize servers, databases and containers; start and stop them on a schedule.
A copilot that asks firstIt proposes a change, and runs it only after you confirm.

ReadsNode.jsPythonGoRustJavaRubyPHPFlutter webStatic sitesYour Dockerfile or Compose

Runs onDockerCaddyPostgresRedisPrometheusGrafanaKubernetesManaged provider services

Open-source-first, with provider-native services where they fit better. Supported languages · App limitations

04Your cloud, your control

Your cloud account is the boundary. We have to earn access to it.

It runs in your accountApp, database and storage are created in the cloud account or server you connect, not with us.
Your provider bills youA Deployer plan covers the platform. Cost estimates are not spending caps.
You approve firstNothing is created until you review the plan and start the deploy.
AI proposes, the engine actsInfrastructure steps are the engine's own. Provider credentials stay out of AI prompts.
A record of changesEvery deploy, redeploy and resize is in the project's history.
Leave any timeWhat it created stays in your account. Nothing is deleted when a plan ends.

Today, connections use long-lived keys you create, with broad permissions. Give The Deployer its own cloud account. Security model · Cloud permissions

Your Git provider GitHub, GitLab or Bitbucket

The Deployer control plane analysis · planning · orchestration

Your cloud account app runtimedatabasestoragenetworkmonitoring

Fig. 03 Where things run. The control plane is ours; the application runtime is yours.

05Fit

Who it's for, and when to use something simpler.

A good fit

Technical founders who'd rather ship than learn a cloud console
Small teams without a platform or DevOps team
Agencies handing clients an app in the client's own cloud
Apps built with Cursor, Claude, Lovable or Bolt that need a real cloud

Something simpler may be better

A static site with no backend: a static host is enough
A Next.js app happy on Vercel, unless you need it in your own cloud
A prototype you'll throw away next week
GPU, regulated or highly custom infrastructure

▸From people using it

What users say

We had startup credits on AWS, Google Cloud and DigitalOcean. The Deployer let us connect all three and choose which cloud each app runs on, so we spread our apps across the credits and made them last far longer.

Rahul SiwachFounder, RPM AT 221 Solutions

What sold me is that everything runs in my own AWS account and AWS bills me directly. If I stop using The Deployer tomorrow, the app keeps running and nothing is locked in.

Himanshu GautamSDE II at GoKwik · Founder, Preptin AI

I connected Claude Code over MCP and asked it to put the app online. It fixed the health route, showed me two hosting options with prices, and only launched after I said yes.

Naman MishraSenior Data Engineer, 3SC

Custom domain, HTTPS, health checks and logs were set up as part of the deploy. On my server, redeploys wait for the new version to pass its health check before the old one stops serving.

Ashika BansalCo-Founder, DocPoc

I already had a Hostinger VPS. One setup command and The Deployer was deploying to it, without me sharing a password or paying for a new cloud server.

Avinash AnandCorporate Relations, Alliance Tek Solutions

I'm not an engineer, and I didn't need to be. The dashboard tells me in plain words whether the app is healthy, what it costs and what changed, so I don't have to ask a developer every time.

Diganta Kumar DasCustomer Success Lead, Stable Money

My staging server stops every night and over weekends on a schedule, and I sized it down when traffic was quiet. Each was a couple of clicks in the dashboard, and I stopped paying for a server nobody was using.

Samarth BansalBuilding new solutions

06Pricing

Pay for the platform. Your cloud bills you directly.

Paid plans upgrade from inside the app. Compare plans.

Rather we did it for you?

Launch puts a supported repository live in your cloud. Move brings an app from another host alongside the original and switches traffic once you approve. Fixed price; delivery conditions are in the Refund Policy. Launch · Move

07Questions

Frequently asked

Do I need to know AWS or Terraform?

No. You review the architecture and the changes without being a cloud specialist. You should still understand your own application. If you'd rather hand it over, Launch and Move are done for you.

What access does The Deployer need?

It depends on the provider and the architecture. Today connections use a long-lived key or token you create, with broad permissions, so give The Deployer its own cloud account or project. Cloud permissions lists, per provider, what you create, what it allows and how to revoke it.

Can the AI see my cloud credentials?

Provider credentials are not placed in AI prompts: the deployment engine uses them, and plans carry references instead of values. An AI coding agent connected over MCP can't read credentials or environment values back. When the copilot runs a command on your server, its output is redacted for known secret values before the model sees it, and redaction can miss a secret it doesn't recognise. Security has the details and limits.

Can I deploy to my own VPS, like Hostinger or GoDaddy?

Yes. Any server running Ubuntu 22.04 or newer, or Debian 12 or newer, with at least 1 GB of memory and ports 80 and 443 free, connects with one setup command; you never share a password. With a Hostinger API token you can also pick the VPS from a list, start and stop it, and take its snapshot from The Deployer. GoDaddy has no server API, so power and snapshots stay in its panel. Shared hosting and servers running cPanel or Plesk on ports 80 and 443 are not supported.

Can it cap my cloud bill?

No. You see an estimate before you deploy, but your provider's usage and pricing set the final bill. Use your provider's budgets and alerts as well; Costs and billing explains how.

What happens if I stop paying?

Resources running in your cloud account are not moved or deleted. Features The Deployer provides, such as deploy on push, alerts or higher limits, stop or drop to the Free plan's limits.

See what it would do
before you give it cloud access.

Check a repo Start free

No card needed: the Free plan includes one deployed project. Your cloud provider bills you directly.

Talk to us

A stack we don't list, a deployment, billing or a partnership: we reply by email.