{"slug": "deno-sandbox", "name": "Deno Sandbox", "category": "security", "category_name": "Security and passwords", "description": "", "recommenders": 5, "commenters": 10, "warners": 1, "score": 3.667, "rising": -1.64, "first": "2026-02-03", "latest": "2026-03-21", "why": "They also have a new Deno sandbox feature which is great for running untrusted code", "why_is_quote": true, "has_verdict": false, "sentiment": {"recommend": 5, "neutral": 2, "compare": 2, "warn": 1}, "spark": [0, 0, 0, 4, 1, 0, 0, 0, 0, 0, 0, 0], "listed": true, "loved": [], "caveat": "", "short_quote": "They also have a new Deno sandbox feature which is great for running untrusted code", "kind": "", "icon": false, "domain": "deno.com", "github_repo": null, "official_url": "", "pricing": "", "aliases": ["Deno Sandbox"], "verdict": null, "praise": [{"label": "", "summary": "", "quotes": [{"id": 759497089, "item_id": 47468568, "url": "https://news.ycombinator.com/item?id=47468568", "by": "mattvr", "date": "2026-03-21", "version": null, "stance": "recommend", "quote": "They also have a new Deno sandbox feature which is great for running untrusted code", "excerpt": "Deno Deploy is actually an excellent product. My choice ranking is Deno Deploy > Fly.io > AWS for new projects, depending on complexity and needs. They also have a new Deno sandbox feature which is great for running untrusted code, AI agents, etc. The real question is can they adapt to customer feedback fast enough, focus priorities, adequately market & grow, make it profitable, etc. Bumpy road but definitely not doo", "context": "", "use_case": "running untrusted code", "switched_from": "", "story": "404 Deno CEO not found"}, {"id": 754180640, "item_id": 47136290, "url": "https://news.ycombinator.com/item?id=47136290", "by": "syhol", "date": "2026-02-24", "version": null, "stance": "recommend", "quote": "Like deno sandbox", "excerpt": "Like deno sandbox https://deno.com/deploy/sandbox", "context": "", "use_case": "Sandboxed code execution", "switched_from": "", "story": "Show HN: enveil \u2013 hide your .env secrets from prAIng eyes"}, {"id": 750578368, "item_id": 46911148, "url": "https://news.ycombinator.com/item?id=46911148", "by": "angristan", "date": "2026-02-06", "version": null, "stance": "recommend", "quote": "Very neat idea!", "excerpt": "Very neat idea! I implemented it into my self hosted remote coding agent: https://stanislas.blog/2026/02/netclode-self-hosted-cloud-coding-agent/#secret-proxy-api-keys-never-enter-the-sandbox", "context": "", "use_case": "", "switched_from": "", "story": "Deno Sandbox"}, {"id": 749999568, "item_id": 46874973, "url": "https://news.ycombinator.com/item?id=46874973", "by": "simonw", "date": "2026-02-03", "version": null, "stance": "recommend", "quote": "Yeah, this is a really neat idea", "excerpt": "Yeah, this is a really neat idea: https://deno.com/blog/introducing-deno-sandbox#secrets-that-cant-be-stolen await using sandbox = await Sandbox.create({ secrets: { OPENAI_API_KEY: { hosts: [\"api.openai.com\"], value: process.env.OPENAI_API_KEY, }, }, }); await sandbox.sh`echo $OPENAI_API_KEY`; // DENO_SECRET_PLACEHOLDER_b14043a2f578cba75ebe04791e8e2c7d4002fd0c1f825e19... It doesn't prevent bad code from USING those s", "context": "", "use_case": "Sandboxed code with secrets", "switched_from": "", "story": "Deno Sandbox"}]}], "caveats": [{"label": "", "summary": "", "quotes": [{"id": 750157568, "item_id": 46884848, "url": "https://news.ycombinator.com/item?id=46884848", "by": "nihakue", "date": "2026-02-04", "version": null, "stance": "warn", "quote": "pretty quickly ran into a wall", "excerpt": "Not sure if anyone from the deno team is monitoring this forum, but I was trying to stand up a dev-base snapshot and pretty quickly ran into a wall. Is it not currently possible to create a bootable volume from the CLI? https://docs.deno.com/sandbox/volumes/#creating-a-snapshot has an example for the js API, but the CLI equivalent isn't specifying --from and the latest verson of the deno CLI installed fresh from deno", "context": "", "use_case": "Dev environment snapshots", "switched_from": "", "story": "Deno Sandbox"}]}], "who": [], "tags": [], "use_cases": ["sandboxed code execution", "running untrusted code", "dev environment snapshots", "sandboxed code with secrets"], "compared": [{"slug": "fly-io", "name": "Fly.io", "co": 2, "switched_from": 0, "switched_to": 0}], "makers": [{"id": 750291088, "item_id": 46893193, "url": "https://news.ycombinator.com/item?id=46893193", "by": "earlence", "date": "2026-02-04", "version": null, "stance": "neutral", "quote": "Our work from 10 years ago introduced the secrets protection technique being used in Deno", "excerpt": "Fun! Our work from 10 years ago introduced the secrets protection technique being used in Deno: https://www.earlence.com/assets/papers/flowfence_sec16.pdf and fly's tokenizer. We called it \"opaque computation\" and it did a lot more than secrets protection.", "context": "", "use_case": "", "switched_from": "", "story": "Deno Sandbox"}], "threads": [{"url": "https://news.ycombinator.com/item?id=46874097", "title": "Deno Sandbox", "mentions": 8}, {"url": "https://news.ycombinator.com/item?id=47133055", "title": "Show HN: enveil \u2013 hide your .env secrets from prAIng eyes", "mentions": 2}, {"url": "https://news.ycombinator.com/item?id=47467746", "title": "404 Deno CEO not found", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=47041456", "title": "Running NanoClaw in a Docker Shell Sandbox", "mentions": 1}], "sentiment_by_month": {"2025-11": {}, "2025-12": {}, "2026-01": {}, "2026-02": {"recommend": 4, "compare": 2, "warn": 1, "neutral": 2}, "2026-03": {"recommend": 1}, "2026-04": {}, "2026-05": {}, "2026-06": {}, "2026-07": {}, "2026-08": {}, "2026-09": {}, "2026-10": {}}, "versions": [], "version_unnamed": 0, "family_ref": null, "runs_on": null, "lines": [], "quotes": [{"id": 759497089, "item_id": 47468568, "url": "https://news.ycombinator.com/item?id=47468568", "by": "mattvr", "date": "2026-03-21", "version": null, "stance": "recommend", "quote": "They also have a new Deno sandbox feature which is great for running untrusted code", "excerpt": "Deno Deploy is actually an excellent product. My choice ranking is Deno Deploy > Fly.io > AWS for new projects, depending on complexity and needs. They also have a new Deno sandbox feature which is great for running untrusted code, AI agents, etc. The real question is can they adapt to customer feedback fast enough, focus priorities, adequately market & grow, make it profitable, etc. Bumpy road but definitely not doo", "context": "", "use_case": "running untrusted code", "switched_from": "", "story": "404 Deno CEO not found"}, {"id": 754203392, "item_id": 47137712, "url": "https://news.ycombinator.com/item?id=47137712", "by": "canadiantim", "date": "2026-02-24", "version": null, "stance": "compare", "quote": "", "excerpt": "Tailscale's new aperture also solves this elegantly: https://aperture.tailscale.com/", "context": "", "use_case": "", "switched_from": "", "story": "Show HN: enveil \u2013 hide your .env secrets from prAIng eyes"}, {"id": 754180640, "item_id": 47136290, "url": "https://news.ycombinator.com/item?id=47136290", "by": "syhol", "date": "2026-02-24", "version": null, "stance": "recommend", "quote": "Like deno sandbox", "excerpt": "Like deno sandbox https://deno.com/deploy/sandbox", "context": "", "use_case": "Sandboxed code execution", "switched_from": "", "story": "Show HN: enveil \u2013 hide your .env secrets from prAIng eyes"}, {"id": 752748416, "item_id": 47046776, "url": "https://news.ycombinator.com/item?id=47046776", "by": "domh", "date": "2026-02-17", "version": null, "stance": "neutral", "quote": "This is similar to Deno Sandbox", "excerpt": "This is similar to Deno Sandbox[1] which was announced a couple of weeks back. Apparently also something similar is done with fly.io's tokenizer[2][3] [1]: https://deno.com/blog/introducing-deno-sandbox [2]: https://news.ycombinator.com/item?id=46874959 [3]: https://github.com/superfly/tokenizer", "context": "", "use_case": "", "switched_from": "", "story": "Running NanoClaw in a Docker Shell Sandbox"}, {"id": 750578368, "item_id": 46911148, "url": "https://news.ycombinator.com/item?id=46911148", "by": "angristan", "date": "2026-02-06", "version": null, "stance": "recommend", "quote": "Very neat idea!", "excerpt": "Very neat idea! I implemented it into my self hosted remote coding agent: https://stanislas.blog/2026/02/netclode-self-hosted-cloud-coding-agent/#secret-proxy-api-keys-never-enter-the-sandbox", "context": "", "use_case": "", "switched_from": "", "story": "Deno Sandbox"}, {"id": 750419712, "item_id": 46901232, "url": "https://news.ycombinator.com/item?id=46901232", "by": "rdhyee", "date": "2026-02-05", "version": null, "stance": "neutral", "quote": "", "excerpt": "Took this idea and ran with it using Fly's Sprites, inspired by Simon's https://simonwillison.net/2026/Feb/3/introducing-deno-sandbox/. Use case: Claude Code running in a sandboxed Sprite, making authenticated API calls via a Tokenizer proxy without credentials ever entering the sandbox. Hit a snag: Sprites appear network-isolated from Fly's 6PN private mesh (fdf:: prefix inside the Sprite, not fdaa::; no .internal D", "context": "", "use_case": "sandboxed code execution", "switched_from": "", "story": "Deno Sandbox"}, {"id": 750157568, "item_id": 46884848, "url": "https://news.ycombinator.com/item?id=46884848", "by": "nihakue", "date": "2026-02-04", "version": null, "stance": "warn", "quote": "pretty quickly ran into a wall", "excerpt": "Not sure if anyone from the deno team is monitoring this forum, but I was trying to stand up a dev-base snapshot and pretty quickly ran into a wall. Is it not currently possible to create a bootable volume from the CLI? https://docs.deno.com/sandbox/volumes/#creating-a-snapshot has an example for the js API, but the CLI equivalent isn't specifying --from and the latest verson of the deno CLI installed fresh from deno", "context": "", "use_case": "Dev environment snapshots", "switched_from": "", "story": "Deno Sandbox"}, {"id": 750040416, "item_id": 46877526, "url": "https://news.ycombinator.com/item?id=46877526", "by": "EGreg", "date": "2026-02-03", "version": null, "stance": "compare", "quote": "So is this Deno Sandbox like that, but for server?", "excerpt": "We already have a pretty good sandbox in our platform: https://github.com/Qbix/Platform/blob/main/platform/plugins/Q/web/js/methods/Q/Sandbox/run.js It uses web workers on a web browser. So is this Deno Sandbox like that, but for server? I think Node has worker threads.", "context": "", "use_case": "", "switched_from": "", "story": "Deno Sandbox"}, {"id": 750000240, "item_id": 46875015, "url": "https://news.ycombinator.com/item?id=46875015", "by": "simonw", "date": "2026-02-03", "version": null, "stance": "neutral", "quote": "Note that you don't need to use Deno or JavaScript at all to use this product.", "excerpt": "Note that you don't need to use Deno or JavaScript at all to use this product. Here's their Python client SDK: https://pypi.org/project/deno-sandbox/ from deno_sandbox import DenoDeploy sdk = DenoDeploy() with sdk.sandbox.create() as sb: # Run a shell command process = sb.spawn(\"echo\", args=[\"Hello from the sandbox!\"]) process.wait() # Write and read files sb.fs.write_text_file(\"/tmp/example.txt\", \"Hello, World!\") co", "context": "", "use_case": "Sandboxed code execution", "switched_from": "", "story": "Deno Sandbox"}, {"id": 749999568, "item_id": 46874973, "url": "https://news.ycombinator.com/item?id=46874973", "by": "simonw", "date": "2026-02-03", "version": null, "stance": "recommend", "quote": "Yeah, this is a really neat idea", "excerpt": "Yeah, this is a really neat idea: https://deno.com/blog/introducing-deno-sandbox#secrets-that-cant-be-stolen await using sandbox = await Sandbox.create({ secrets: { OPENAI_API_KEY: { hosts: [\"api.openai.com\"], value: process.env.OPENAI_API_KEY, }, }, }); await sandbox.sh`echo $OPENAI_API_KEY`; // DENO_SECRET_PLACEHOLDER_b14043a2f578cba75ebe04791e8e2c7d4002fd0c1f825e19... It doesn't prevent bad code from USING those s", "context": "", "use_case": "Sandboxed code with secrets", "switched_from": "", "story": "Deno Sandbox"}, {"id": 749999344, "item_id": 46874959, "url": "https://news.ycombinator.com/item?id=46874959", "by": "motrm", "date": "2026-02-03", "version": null, "stance": "recommend", "quote": "", "excerpt": "Reminds me a little of Fly's Tokenizer - https://github.com/superfly/tokenizer It's a little HTTP proxy that your application can route requests through, and the proxy is what handles adding the API keys or whatnot to the request to the service, rather than your application, something like this for example: Application -> tokenizer -> Stripe The secrets for the third party service should in theory then be safe should", "context": "", "use_case": "", "switched_from": "", "story": "Deno Sandbox"}]}