← Back to Product Feed

Hacker News Show HN: Afterburner – Capability-Sandboxed JavaScript/TS Runtime in Rust

A secure, sandboxed environment for running untrusted JavaScript/TypeScript code, user scripts, plugins, business rules, or edge logic within Rust applications or existing toolchains.

3
Traction Score
2
Discussions
Jun 14, 2026
Launch Date
View Origin Link

Product Positioning & Context

AI Executive Synthesis
A secure, sandboxed environment for running untrusted JavaScript/TypeScript code, user scripts, plugins, business rules, or edge logic within Rust applications or existing toolchains.
Afterburner addresses a critical security and operational pain point for platforms and applications requiring safe execution of untrusted or user-defined code. Its capability-based sandboxing provides a robust solution for integrating third-party logic, plugins, or serverless functions without compromising host system integrity. The Rust implementation suggests high performance and reliability, crucial for enterprise adoption. This product aligns with significant B2B trends in secure extensibility, platform-as-a-service architectures, and the need for granular control over compute resources. The BSL-1.1 licensing model indicates a strategic approach to commercialization while fostering developer adoption.
Hey everyone! I've been working on something called Afterburner: a fast, embeddable JS/TS runtime written in Rust, with a capability sandbox baked right in.Scripts run locked down by default: no network, no filesystem, no environment variables. You explicitly grant whatever access a script actually needs, and every call gets hard caps on CPU, memory, and time.The goal isn't to replace your existing stack. It's to fit cleanly into it:Embed a JS/TS engine in your Rust app with a single crate. Run user scripts, plugins, business rules, or edge logic, each call fully sandboxed.
Wrap the tools you already use. Commands like `burn node app.js`, `burn npm test`, `burn bun`, `burn deno run`, and `burn npx tsx` run your existing toolchain under the sandbox. Take an unmodified Express, Fastify, or Hono app and run it with zero ambient I/O and a memory ceiling. No code changes needed.
Use the built-in registry at registry.afterburner.sh. Publish with `burn publish`, install with `burn install` or `burn add` dependencies are pinned by content digest. Every package ships with a capability manifest, so installed code is sandboxed by default. It also interops with npm, so you can still pull in npm libraries as needed.
Since nothing gets ambient authority, it's also just a clean, practical way to run untrusted code without having to cross your fingers and hope.Repo: https://github.com/afterburner-sh/afterburner
Site: https://afterburner.sh
Registry: https://registry.afterburner.shThe full walkthrough like how it works, what it can do, and benchmarks hitting up to ~16.8M rows/sec is all in one post. It's the best place to start:
https://vertexclique.com/blog/burn-after-reading/One licensing note: it's source-available under BSL-1.1, which automatically converts to Apache-2.0 four years after each release.
Free to use for your own projects so go build something.
JS/TS runtime Rust capability sandbox embeddable user scripts plugins business rules edge logic

Related Ecosystem & Alternatives

Discover adjacent products, open-source repositories, and developer tools sharing similar technical architecture.

Deep-Dive FAQs

What is Afterburner – Capability-Sandboxed JavaScript/TS Runtime in Rust?
Afterburner – Capability-Sandboxed JavaScript/TS Runtime in Rust is analyzed by our AI as: A secure, sandboxed environment for running untrusted JavaScript/TypeScript code, user scripts, plugins, business rules, or edge logic within Rust applications or existing toolchains.. It focuses on Afterburner addresses a critical security and operational pain point for platforms and applications requiring safe execution of untrusted or user-d...
Where did Afterburner – Capability-Sandboxed JavaScript/TS Runtime in Rust originate?
Data for Afterburner – Capability-Sandboxed JavaScript/TS Runtime in Rust was aggregated directly from the Hacker News community ecosystem, representing raw developer and early-adopter sentiment.
When was Afterburner – Capability-Sandboxed JavaScript/TS Runtime in Rust publicly launched?
The initial public indexing or launch date for Afterburner – Capability-Sandboxed JavaScript/TS Runtime in Rust within our tracked developer communities was recorded on June 14, 2026.
How popular is Afterburner – Capability-Sandboxed JavaScript/TS Runtime in Rust?
Afterburner – Capability-Sandboxed JavaScript/TS Runtime in Rust has achieved measurable traction, logging over 3 traction score and facilitating 2 recorded discussions or engagements.
Which technical categories define Afterburner – Capability-Sandboxed JavaScript/TS Runtime in Rust?
Based on metadata extraction, Afterburner – Capability-Sandboxed JavaScript/TS Runtime in Rust is categorized under topics such as: JS/TS runtime, Rust, capability sandbox, embeddable.
How does the creator describe Afterburner – Capability-Sandboxed JavaScript/TS Runtime in Rust?
The original author or development team describes the product as follows: "Hey everyone! I've been working on something called Afterburner: a fast, embeddable JS/TS runtime written in Rust, with a capability sandbox baked right in.Scripts run locked down by default: no ne..."

Community Voice & Feedback

No active discussions extracted yet.

Discovery Source

Hacker News Hacker News

Aggregated via automated community intelligence tracking.

Tech Stack Dependencies

No direct open-source NPM package mentions detected in the product documentation.

Media Tractions & Mentions

No mainstream media stories specifically mentioning this product name have been intercepted yet.

Deep Research & Science

No direct peer-reviewed scientific literature matched with this product's architecture.