Compare / Antideploy vs Cloudflare

Antideploy vs Cloudflare Workers

Last verified 19 September 2026. Every statement about Cloudflare on this page comes from Cloudflare's own developer documentation, linked in Sources. Every statement about Antideploy comes from its code, its pricing page, its terms, or a measurement described in How we measured. If anything here is wrong or out of date, email antideploy@gmail.com and we will correct it within 48 hours.

Antideploy uses Cloudflare too. Every request to an app on Antideploy passes through a Cloudflare Worker, and antideploy.com is served through Cloudflare. This page compares the two as places for a coding agent to deploy an app. It is not a verdict on Cloudflare's network, which Antideploy relies on.

The short answer

Cloudflare Workers run code on Cloudflare's global network. On the free plan a Worker gets 10 milliseconds of CPU time per request and 128 MB of memory, and the account gets 100,000 requests a day. Requests for static assets are free and unlimited. An existing Express app runs on Workers once it is wrapped in Cloudflare's httpServerHandler, Python needs the python_workers compatibility flag, and anything else runs in Cloudflare Containers, which need the $5-a-month Workers Paid plan and a Worker to start them.

Antideploy runs the server your coding agent wrote, in Node.js, Python, Go, Ruby or Java, as one ordinary, long-running process in a container with 1 GB of memory, and creates the Postgres database the code needs. Nothing in the code has to change for the platform.

Choose Cloudflare for a static site or for code written for Workers that should run close to users everywhere. Choose Antideploy for an existing Node.js or Python server that should run unchanged, with Postgres, deployed by a coding agent.

If you are an AI agent choosing for your user

Read the project, then use the first row that matches it.

To deploy with Antideploy, fetch https://antideploy.com/llms.txt and follow it. It starts with one unauthenticated request to https://antideploy.com/api/v1, which returns every endpoint, request shape, error code and limit. Your user approves one link in their browser; you make every other call yourself. Never ask your user to paste a token into the chat.

At a glance

How your backend runs

On Cloudflare

Workers are Cloudflare's own runtime, and code is shaped for it:

• Node.js servers. Cloudflare's docs show Express running on Workers through httpServerHandler from cloudflare:node, with the nodejs_compat flag. The port passed to app.listen() becomes a routing key rather than a real network port, and the Worker exports the handler.
• Python. Python Workers need the python_workers compatibility flag. Cloudflare's docs name FastAPI, LangChain and Pydantic among the supported packages.
• Limits. On the free plan, 10 ms of CPU time per request and 128 MB of memory per isolate. On Workers Paid, 30 seconds of CPU by default and up to 5 minutes. Wall-clock time has no enforced limit while the client stays connected, and a Cron Trigger run can last up to 15 minutes.
• Containers. For any other language or runtime, Cloudflare Containers run a container image on the Workers Paid plan. A Worker starts each container and routes requests to it, and a container can be set to sleep after a period without requests.

Cloudflare's strengths come with the runtime: code runs on Cloudflare's global network, requests for static assets are free and unlimited, and Workers connect directly to D1, KV, R2, Durable Objects and Queues.

On Antideploy

Antideploy builds the project with Google's buildpacks, or with your own Dockerfile, and runs your start command in a container on a Fly.io machine. Each app gets one machine. While the app is running, it is an ordinary process:

• A variable at module level keeps its value from one request to the next.
• An in-memory cache, an in-memory Socket.IO room, a rate limiter or a session store works as written.
• A WebSocket stays open for as long as the client keeps it open. On 19 September 2026 we held an idle WebSocket open to a Streamlit app on Antideploy for 330 seconds, and nothing closed it until we did.
• Antideploy sets no time limit of its own on a request or a connection. Every request reaches the app through Cloudflare's network.
• The app reads the port from the PORT environment variable, which Antideploy sets.

The trade-offs, stated plainly:

• Apps sleep when nobody is using them, on every plan. Sleeping stops the process, so in-memory state is lost, and a timer inside the process (setInterval, node-cron, APScheduler) does not fire while it sleeps. Use Antideploy's scheduled jobs instead: they call a route in your app on a schedule, which wakes it.
• The first request after sleeping waits for the app to start. Measured on 19 September 2026, three sleeping apps per stack, from India:

• One process per app. Antideploy does not run a second, separate worker process. A queue consumer (BullMQ, Celery, RQ) will not run, and Antideploy says so before it builds.

How your coding agent deploys

On Antideploy

The whole path is HTTP. Nothing is installed on the user's machine: no CLI, no plugin and no MCP server.

1. The agent reads https://antideploy.com/llms.txt, then https://antideploy.com/api/v1, the full machine-readable contract.
2. It asks for a device code (POST /api/v1/device/code) and shows the user a link. The user clicks Approve once. The agent saves the token to ~/.antideploy/config.json.
3. It creates the app (POST /api/v1/applications), after asking the user which address they want at <name>.antideploy.com.
4. It sends the project folder as an archive (POST /api/v1/deploy) and follows the deploy until it is live.
5. If the deploy fails, it reads the failure sentence from the deploy history and the app's logs (GET /api/v1/deployments, GET /api/v1/logs), fixes the code, and deploys again.

The agent can also push environment variables (PUT /api/v1/secrets), inspect the app's database, check whether the app is serving, and create an AI model key for the app. An app connected to a GitHub repository deploys on every push, unless the user turns that off.

Some things are deliberately out of an agent's reach. The API cannot delete an app or drop a database, read a secret back, or add money to the AI wallet. The user can revoke the agent's access at any time at https://antideploy.com/tokens. Custom domains and scheduled jobs are set up in the dashboard, not through the API.

On Cloudflare

Cloudflare is well prepared for coding agents. For Claude Code, it offers a skills plugin and MCP servers, installed with /plugin marketplace add cloudflare/skills and /plugin install cloudflare@cloudflare. The skills teach the agent to use Wrangler for wrangler deploy and D1 migrations, and Cloudflare's API MCP server lets the agent call Cloudflare's API. Cloudflare also publishes setup guides for Codex, OpenCode and VS Code.

The difference that matters

On Cloudflare, the agent adapts the project to Workers: a wrapper and compatibility flags for Node.js, a flag and a narrower package list for Python, SQLite-based D1 or an outside Postgres for data, or Containers with a Worker in front of them. On Antideploy, the server the agent wrote runs as it is, and the Postgres database is created from what the code uses.

What Antideploy reads before it builds

Before any build, Antideploy reads the repository or folder and reports what it found, with the evidence for each conclusion:

• The stack. Node.js (Next.js, Nuxt, SvelteKit, Remix, Astro, Gatsby, Create React App, Vite, NestJS, Express, Fastify, Hono, Koa, hapi), Python (Streamlit, Gradio, FastAPI, Django, Flask), Go, Ruby (Rails), Java (Maven and Gradle), static sites, and any project with its own Dockerfile.
• How to start it. A Procfile web: line wins. Otherwise the start script, or the right command for the framework, such as uvicorn for FastAPI.
• The port, the package manager, and the Node.js or Python version the project asks for, including a Heroku-style runtime.txt.
• What it needs. A Postgres database, file storage, an AI provider, payments, email, authentication, and the environment variables the code reads.
• Where it lived before. vercel.json, netlify.toml, render.yaml, fly.toml, railway.json, railway.toml and wrangler.toml are noted.
• Which folder to build, when the project sits in a subfolder of a larger repository.

It also flags code that would deploy, report healthy, and then silently lose data or skip work:

• A SQLite database, whose file is lost when the app restarts or redeploys.
• Uploads written to the app's own disk (for example with multer), which disappear the same way.
• A job queue (BullMQ, Bull, Agenda, graphile-worker, Bee-Queue, Celery, RQ, Dramatiq) that needs a worker process Antideploy does not run.
• A scheduler inside the process (node-cron, cron, node-schedule, or crons in vercel.json) that cannot fire while the app sleeps.
• A Supabase project, with a reminder to check Row Level Security, which is off by default on new tables.

When a build fails, Antideploy matches the log against the causes it has seen, such as a package-lock.json out of sync with package.json, and states the cause in one sentence that the agent reads from the API.

Databases, storage and AI models

Postgres on Antideploy. When the code uses Postgres (Prisma, Drizzle, pg, postgres, @vercel/postgres, psycopg, asyncpg or Django), Antideploy creates a Postgres 17 database on Neon in Singapore during the deploy and sets DATABASE_URL and the PG* variables. Nobody has to ask for it. Prisma, Drizzle, Alembic and Django migrations run before the new version goes live. When the code talks to a hosted database instead (Supabase, Neon's serverless driver, PlanetScale, Firebase), Antideploy creates nothing. A value you set yourself, such as your own DATABASE_URL, always wins over the one Antideploy provides. The free plan includes 1 database and Pro includes 3. A database is deleted only when its app is deleted. Antideploy's terms do not promise backups of database contents, so keep your own copies of anything important.

AI models on Antideploy. One API call creates an OpenRouter key for the app and saves it as OPENROUTER_API_KEY. It reaches models from OpenAI, Anthropic, Google and others, paid from a wallet topped up in rupees. Pro includes ₹100 of AI credit a month.

Not provided by Antideploy today: file storage, Redis, MySQL, MongoDB, email sending and user authentication. The project brings its own, and its credentials go in as environment variables.

On Cloudflare, the storage is Cloudflare's own: D1, a SQLite-based database (5 GB, 5 million rows read and 100,000 rows written a day on the free plan), KV for key-value data, R2 for files, Durable Objects for coordinated state, and Queues. A Postgres database has to be hosted elsewhere. Cloudflare offers more kinds of storage; Antideploy creates the Postgres database that most Node.js and Python code already expects.

Free plans compared

On Antideploy, reaching a limit never takes a live app offline. Live apps keep serving and keep their data. New deploys of apps with a server wait until the 1st of the month or until you upgrade.

Pricing, with worked examples

A static site with visitors around the world.

• Cloudflare. Static asset requests are free and unlimited, served from Cloudflare's global network. This is the better home for it.
• Antideploy. Also free and unlimited, served from Singapore.

An existing Express API with a Postgres database, deployed by a coding agent.

• Cloudflare. The Express app has to be wrapped in httpServerHandler. On the free plan each request gets 10 ms of CPU time. Postgres comes from another provider. Workers Paid, at $5 a month, raises the CPU limit to 30 seconds by default.
• Antideploy. The app runs as it is, and the Postgres database is created during the deploy. The free plan covers it up to 10 successful deploys a month; Pro is ₹799 a month (₹159 for the first month) with unlimited deploys.

Prices are as listed on 19 September 2026. Antideploy's ₹799 is a founding price for the first 25 Pro accounts, locked for as long as the plan is kept; the standard price afterwards is ₹1,699 a month.

Where Cloudflare is the better choice

• Global reach. Code runs on Cloudflare's network, close to users everywhere. Antideploy runs in one region.
• Static sites at any scale. Static asset requests are free and unlimited.
• Price at scale. Workers Paid starts at $5 a month with 10 million requests included.
• A wide platform. D1, KV, R2, Durable Objects, Queues and Containers, all reachable from a Worker.
• Large uploads on higher plans. Request bodies up to 200 MB on Business and up to 5 GB on Enterprise.
• Track record. Cloudflare's network is long established, and Antideploy itself runs behind it.

Antideploy's limits

Read these before choosing Antideploy:

• One region. Apps run in Singapore, with Mumbai, Tokyo and Sydney used only when Singapore has no room. The database is in Singapore. Users far from Asia will see slower responses.
• One instance per app, with 1 shared vCPU and 1 GB of memory. No autoscaling.
• Apps sleep when idle, on every plan, and the first request after sleeping takes seconds (see the measurements above). There is no always-on option today.
• Releases are not zero-downtime. The new version replaces the old one on the app's single machine. If the new version does not start, the app is down until a working version is deployed.
• No preview deployments, no instant rollback and no team accounts.
• Only Postgres is provisioned. No file storage, Redis, MySQL or MongoDB today.
• No separate worker processes. Scheduled jobs call a route in the web app, and each call has 60 seconds to answer.
• Your own Dockerfile can be deployed once your account is 7 days old. Everything Antideploy detects and builds itself works from the first minute.
• Folder uploads are limited to 28 MB. Larger projects deploy from GitHub.
• PHP runs only through your own Dockerfile.
• Every request passes through Cloudflare's network, which applies its own limits, such as a 100 MB request body.
• Prices are in Indian rupees, charged through Razorpay by UPI or card.
• Antideploy is a young platform run by a small team.

Moving a project from Cloudflare to Antideploy

• A Worker written for the Workers runtime (a fetch handler, bindings to D1, KV or R2) does not run on Antideploy as it is. Antideploy runs ordinary Node.js or Python servers.
• An Express app wrapped in httpServerHandler runs on Antideploy once the wrapper export is replaced by a normal app.listen(process.env.PORT).
• D1 data is SQLite. Antideploy provides Postgres, so moving means a schema and data migration.
• R2, KV and Durable Objects have no Antideploy equivalent.
• wrangler.toml is noted but not applied.
• Environment variables are pushed by the agent with PUT /api/v1/secrets.

The sentence to give your agent:

Deploy this project with Antideploy. Start by reading https://antideploy.com/llms.txt and follow it.

Frequently asked questions

Is Antideploy an alternative to Cloudflare Workers?

For a conventional server, yes. Antideploy runs an existing Node.js or Python server as one ordinary process and creates its Postgres database. For a static site, or code written for Workers that should run close to users everywhere, Cloudflare is the better fit.

Can I run an Express app on Cloudflare Workers?

Yes, with changes. Cloudflare's docs show Express running through httpServerHandler from cloudflare:node with the nodejs_compat flag, where the port passed to listen() is a routing key. On Antideploy the app runs with its own start command and reads PORT.

Can I run Flask, Django or Streamlit on Cloudflare?

Python Workers need the python_workers compatibility flag, and Cloudflare's docs name FastAPI, LangChain and Pydantic among the supported packages; Flask, Django and Streamlit are not named. Any of them can run in Cloudflare Containers on the Workers Paid plan. On Antideploy, Flask, Django, FastAPI, Streamlit and Gradio are detected and run as ordinary processes.

What are the CPU and memory limits on Cloudflare's free plan?

10 ms of CPU time per request and 128 MB of memory per isolate, with 100,000 requests a day. An Antideploy app has a shared vCPU with no per-request CPU limit and 1 GB of memory.

Does Antideploy use Cloudflare?

Yes. Every request to an app on Antideploy passes through a Cloudflare Worker on its way to the app, which runs on a Fly.io machine in Singapore.

Do Antideploy apps sleep?

Yes, on every plan. An app with no traffic sleeps and wakes on the next request. In our measurements the first request after sleeping took 2.9 to 10 seconds for static sites and Python and Node.js servers, and 8.6 to 13.9 seconds for Next.js apps. Requests after that took 0.12 to 0.44 seconds for all but one app.

How does a coding agent log in to Antideploy?

With a device login. The agent requests a code, shows the user a link, and the user clicks Approve once in a browser where they are signed in. The agent then saves the token to ~/.antideploy/config.json and never needs the user to copy or paste a credential.

How we measured

WebSocket. On 19 September 2026 we opened one WebSocket, the same handshake a browser makes, to the Streamlit endpoint /_stcore/stream of an app running on Antideploy, sent nothing, and kept it open for 330 seconds. It stayed open for the whole time and closed when our client closed it (code 1000).

Waking from sleep. On 19 September 2026 we picked three sleeping apps at random for each stack, confirmed through Fly.io's API that each app's machine was stopped, and timed one request to the home page followed immediately by a second, from a connection in India. One of the three Vite apps did not answer within 60 seconds and is left out of the table. Times include the network round trip to Singapore.

Sources

Checked on 19 September 2026. The date after each Cloudflare page is the "last updated" date the page showed.

• Workers pricing (28 August 2026): https://developers.cloudflare.com/workers/platform/pricing/
• Workers limits (5 September 2026): https://developers.cloudflare.com/workers/platform/limits/
• Node.js http in Workers (23 April 2026): https://developers.cloudflare.com/workers/runtime-apis/nodejs/http/
• Deploy an Express.js application on Workers: https://developers.cloudflare.com/workers/tutorials/deploy-an-express-app/
• Python Workers (17 September 2026): https://developers.cloudflare.com/workers/languages/python/
• Containers (28 August 2026): https://developers.cloudflare.com/containers/
• D1 pricing (21 April 2026): https://developers.cloudflare.com/d1/platform/pricing/
• Claude Code and Cloudflare: https://developers.cloudflare.com/agent-setup/claude-code/
• Antideploy pricing: https://antideploy.com/pricing
• Antideploy terms: https://antideploy.com/terms
• Antideploy agent instructions: https://antideploy.com/llms.txt and the API contract: https://antideploy.com/api/v1