nowfound

Alternatives

Products that do what Afterburner – Capability-Sandboxed JavaScript/TS Runtime in Rust does

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…

  1. 1UR
  2. 2

    The better runtime for Next.js

    2022

  3. 3
    Reflag117

    First ever self-cleaning feature flags for TypeScript

    Sep 2025

  4. 4SJ

    Jan 2026 · docs.script-lang.org

  5. 5VW
  6. 6EA
  7. 7

    High performance secure & portable Rust functions in Node.js

    2020

  8. 8SS

    Raw performance (the lack of) is always a contentious point for JavaScript, especially in our post-Moore era of computing. Node.js gets around this issue through extensive of use of native libraries and modules written in C, including the V8 JS engine itself. But as application developers, how do YOU create high performance functions? Write in C and run as a NAPI module? Write in Rust and run as a V8 wasm? Well, there is another (better and faster) way now! The SSVM is a fully featured WebAssembly VM that is optimized for server-side applications.…

    2020

  9. 9NA

    Hi, over the past few months I've been working on this project: Numax is a small Rust runtime that does three things: it runs WebAssembly modules in a sandbox, has a built-in local key-value store, and syncs everything across nodes with CRDTs and gossip. Basically, you write a wasm module, run it on two machines, and they converge (I hope !). It's a decentralized system... I hope someone finds it interesting! There's a whitepaper I've put a lot into, and I think the code isn't bad either! I believe there's still room in this world for software that's fun and well made, and while building…

    Jun 2026 · github.com

  10. 10

    Build modern web applications fast: The Svelte 5 boilerplate

    2025

  11. 11IB

    Link: https://docs.trysoma.ai/ For the past ~9 months I’ve been building Soma, an open-source AI agent & workflow runtime written in Rust, with a TypeScript SDK (Python coming soon). It’s not a framework; it’s meant to sit underneath whatever agent/tooling code you already write (Vercel AI SDK, LangChain, custom code, etc.). It provides features around your framework + a better DX for building agents. I’ve tried to take a Next.JS model: open-source, good DX, self-deployable. I originally set out to build a vertical back-office/operations product for SMEs. I needed a…

    Dec 2025 · docs.trysoma.ai

  12. 12LW
  13. 13RR

    I built rapid-rs to eliminate the hours of boilerplate when starting a new Rust web service. One command gets you: - Auto-configured DB, logging, CORS - OpenAPI/Swagger UI at /docs - Request validation - Production-ready observability Built on Axum. Early benchmarks show ~50K req/s with 10-20MB RAM. This is v0.1 - feedback welcome! Crates: https://crates.io/crates/rapid-rs

    Nov 2025 · crates.io

  14. 14TF

    Hi folks, I started thinking some time ago about how to use ReactJS's server-side features with backends that aren’t specifically built with Node.js or Deno. After some research, I found that the only strict requirement is a JS engine for server-side rendering, while the rest of the runtime can be in any language. For this reason, I started developing a full-stack ReactJS web framework with a Rust-based backend (the API draws heavy inspiration from Next.js). The server performance is already impressive, with a 4x improvement over the latest Next.js. We’re tracking it in a separate…

    2025 · github.com

  15. 15SA

    I’ve been working on shuck, a shell script linter written in Rust. ShellCheck is excellent project and set the bar for this space. However, it's very slow and take up a far amount of resources. shuck is conservatively 20x faster than shellcheck and uses a fraction of the resources. shuck currently supports sh, bash, dash, ksh, mksh, and zsh. shuck should mostly be a drop in replacement for shellcheck but it is not a port since shellcheck is GPL. It is s clean-room implementation with its own parser and analysis engine, so behavior may differ in some cases. shuck is tested against shellcheck…

    Apr 2026 · github.com

  16. 16WJ

    Oct 2025 · shyam20001.github.io

  17. 17AF

    fasthex - a very optimized hex dumper with all the features other hex dumpers have too

    Jun 2026 · github.com

  18. 18AI

    Hi HN, I'm Kyle, the creator of Clipper, a container registry with 7x faster builds via lazy pulls and cache mount exports. In the process of implementing cache mount exports I ended up with a FUSE mounted filesystem backed by a remote content defined store. I went looking for fun things to do with it and found that there's not really a good way to keep Rust incremental build state around on ephemeral runners, so here we are. Rust generally uses https://github.com/mozilla/sccache for caching, but sccache disables itself when incremental compilation is enabled…

    Jul 2026 · github.com

  19. 19TA

    Hi HN! This Christmas I made `tysm`, a rust crates which simplifies using ChatGPT with Structured Outputs. Essentially you just tell it the rust type you want the output to conform to, and it handles creating the JSON Schema, passing it to ChatGPT's chat-completions API, and deserializing the response. Structured Outputs are very useful because they guarantee that the response will conform to whatever type you expect. I'm already finding my crate very useful since I love using Structured Outputs but I hate writing JSON Schemas myself. Technical details for rust heads: To generate the JSON…

    2024 · github.com

  20. 20ME
  21. 21AV

    We made a VS Code extension [1] that lets you visualise logs and traces in the context of your code. It basically lets you recreate a debugger-like experience (with a call stack) from logs alone. This saves you from browsing logs and trying to make sense of them outside the context of your code base. We got this idea from endlessly browsing traces emitted by the tracing crate [3] in the Google Cloud Logging UI. We really wanted to see the logs in the context of the code that emitted them, rather than switching back-and-forth between logs and source code to make sense of what happened. It's a…

    2025 · github.com

  22. 22HX
  23. 23IB

    I built a Rust drop-in replacement for svelte-check that's 10-30x faster for Svelte 5 projects. What it does: - Parses Svelte files with a custom Rust parser - Transforms them to TSX in parallel using Rayon - Runs type-checking via Microsoft's tsgo (the native Go port of TypeScript) - Maps errors back to original .svelte locations via source maps Why it's fast: The official svelte-check uses TypeScript's Language Service API optimized for IDEs with persistent connections. Great for autocomplete but slow for batch CLI checks. svelte-check-rs writes real TSX files to disk and runs tsgo as a…

    Jan 2026 · svelte-check-rs.vercel.app

  24. 24RL

    I've just released rust-loguru, a logging library for Rust that aims to combine intuitive API design (inspired by Go/Python's Loguru) with Rust's performance characteristics. Some highlights: - Consistently outperforms the standard log crate by 50-80% in benchmarks. - Multiple log levels and an extensible handler system -File rotation with better performance than log4rs and other alternatives - Error handling utilities and context helpers I built this because I wanted a logger that was both ergonomic to use and high-performance. The benchmarks comparing it to slog, log, and tracing are…

    2025 · crates.io

Ranked by how close each launch is in meaning, then by votes. Refine with a description →