{"slug": "deno-deploy-is-generally-available", "title": "Deno Deploy is Generally Available", "summary": "Deno Deploy has officially launched as a general availability service, offering a zero-config platform for deploying JavaScript and TypeScript applications that supports all major frameworks and automatically detects build processes. The platform includes built-in databases (Deno KV and Postgres), automatic environment variable management, and a new Deno Sandbox service for securely running code in microVMs. Additionally, Deno Deploy provides features like automatic continuous deployment from GitHub, isolated databases for each pull request, and a `--tunnel` flag for streamlined local development with shared environment variables.", "body_md": "Deno Deploy is Generally Available\nWhat if deploying a web app was as simple as running it locally? No adapters. No build config. No vendor-specific config files. Sveltekit, Next, Astro — whatever you’re using.\nThat’s Deno Deploy, the easiest way to deploy and run any JavaScript or TypeScript to the web, and today it is generally available.\nAs part of this announcement, we’ll share how Deno Deploy simplifies building and deploying code, as well as introduce Deno Sandbox, a new service on Deno Deploy that allows you to programmatically manage microVMs for executing any code securely.\nAny framework, any build process\nDeno Deploy supports all major JavaScript frameworks, regardless of whether you\nare building or running with Deno. Not only that, but it will automatically\ndetect which framework you’re using, and run the build commands specific to your\nframework. This allows us to make the most of your framework’s features, such as\nwith the \"use cache\"\ndirective in Next.js 16.\nZero-config continuous deployment\nDeno Deploy is built for modern development workflows and is flexible enough to fit you and your team’s needs.\nIf you connect your GitHub repo to Deno Deploy, you’ll automatically get zero-config continuous delivery:\n- live previews for every git commit\n- each pull request will be tracked as a “timeline”, each with their own isolated database (more on that below)\n- promoting to prod and easy rollbacks via the UI\nIf you want more control over your release process, there’s the new\ndeno deploy\nsubcommand\nthat you can use from your terminal (great for testing and quick iterations) or\nfrom your CI environment.\nBuilt-in databases\nIn addition to supporting Deno KV, our global key-value store, Deno Deploy now also supports Postgres databases. Not only can you easily link third party databases, but thanks to our partnership with Prisma, you can also provision new databases for free right through our dashboard.\nDeno Deploy will provision a new database for every pull-request opened. This avoids dangerous mistakes and makes development easier.\nNot only that, but your application code remains the same in all contexts, even though the database is different. That’s because environment variables are managed automatically by Deno Deploy:\nimport { Pool } from \"npm:pg\";\n// No configuration needed - Deno Deploy handles this automatically\nconst pool = new Pool();\nDeno.serve(async () => {\n// Use the database\nconst result = await pool.query(\"SELECT * FROM users WHERE id = $1\", [123]);\nreturn new Response(JSON.stringify(result.rows), {\nheaders: { \"content-type\": \"application/json\" },\n});\n});\nIn addition to all that, you can now explore your data right in the Deno Deploy console.\nWant to see a specific database supported? Let us know on Twitter, Bluesky, or Discord!\n--tunnel\nStreamlined local development with One of the biggest headaches when deploying software is that a project that\nworks locally behaves differently in production. We’ve bridged those two\nenvironments, making it easy to develop locally with confidence using the flag\n--tunnel\n.\nSimply add the flag to your command and you will automatically pull centrally managed environment variables from Deno Deploy, run your dev server locally, expose a public, shareable URL instantly, and send telemetry data to Deno Deploy.\nThe --tunnel\nflag simplifies working on the same code base across a team, as\nyou can all access the same environment variables, as well as serving your local\nversion on a public URL for easier sharing. Also, it is currently available for\nthe run\nand\ntask\ncommands, but expect\nthat it will become even more powerful as more utilities are added.\nFirst class, automatic observability\nAny project hosted on Deno Deploy, regardless of Node or Deno, or even if there are specific telemetry instrumentation, will automatically show logs, traces, and metrics in the application console.\nBy default, Deno will capture the following: console.log\n, fetch\n, http\n, V8\nevents, garbage collection, and IO. Your\nlogs will also be automatically associated with the request,\nso triaging and debugging is much simpler. Check out our documentation for more\nexamples.\nSafe, Instant Compute with Deno Sandbox\nRead the full Deno Sandbox announcement here.\nWe’ve noticed a rise of LLM generated code deployed to Deno Deploy and wanted to make that path as smooth as possible. Our key design considerations were:\n- speed: the user edits, AI regenerates, and changes appear immediately, and\n- security: full isolation and a secrets model that survives prompt injection\nWith this in mind, we have built a new primitive called Deno Sandbox, which are real linux microVMs that boot in under a second, offering instant safe compute programmatically.\nHere’s an example of a script that will create a Deno Sandbox, writes a dev server, runs it, and exposes a port for anyone to access:\nimport { Sandbox } from \"@deno/sandbox\";\nawait using sandbox = await Sandbox.create({ port: 8000 });\nawait sandbox.fs.writeTextFile(\n\"main.ts\",\n\"export default { fetch: () => new Response('hi') }\",\n);\nconst p = await sandbox.sh`deno serve --watch main.ts`.spawn();\nconsole.log(\"deno now listening on\", sandbox.url);\nawait p.output();\n$ deno -NRE main.ts\ndeno now listening on https://22313a1bbdf94b27803a3f929a5af33a.sandbox.deno.net\nWatcher Process started.\ndeno serve: Listening on http://0.0.0.0:8000/\nRead the full announcement on Deno Sandbox.\nPricing\nDeno Deploy comes with a generous free plan, offering one million requests per month, 100 GB of egress, and 15 CPU hours. For those needing more resources, there are various pro plans available, allowing for flexible scaling based on usage.\nFor teams with greater security, support, and performance needs, we offer custom enterprise pricing. Learn more on our pricing page.\nWhat’s next\nDeploying one of the simple starter apps here is an easy way to dive into the new Deno Deploy and see what it’s all about. You can sign up, create an organization, and start deploying apps for free.\nWe’re excited to see what you — or your AI agents — build with Deno Deploy.\nWhat are you building with Deno? Let us know on Twitter, Bluesky, or Discord!", "url": "https://wpnews.pro/news/deno-deploy-is-generally-available", "canonical_source": "https://deno.com/blog/deno-deploy-is-ga", "published_at": "2026-02-03 12:00:00+00:00", "updated_at": "2026-05-22 12:19:51.594625+00:00", "lang": "en", "topics": ["developer-tools", "cloud-computing", "open-source", "products"], "entities": ["Deno Deploy", "Deno Sandbox", "Sveltekit", "Next.js", "Astro", "GitHub"], "alternates": {"html": "https://wpnews.pro/news/deno-deploy-is-generally-available", "markdown": "https://wpnews.pro/news/deno-deploy-is-generally-available.md", "text": "https://wpnews.pro/news/deno-deploy-is-generally-available.txt", "jsonld": "https://wpnews.pro/news/deno-deploy-is-generally-available.jsonld"}}