This product was not featured by Product Hunt yet.
It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).

Product upvotes vs the next 3

Waiting for data. Loading

Product comments vs the next 3

Waiting for data. Loading

Product upvote speed vs the next 3

Waiting for data. Loading

Product upvotes and comments

Waiting for data. Loading

Product vs the next 3

Loading

sandbin

Run untrusted code and survive it — no Docker, no root

Sandbin runs untrusted code in a real sandbox — bubblewrap + seccomp + cgroups, not a container. No Docker daemon, no root, no VM. ~20ms cold start (17.6× faster than Docker, measured), a 146-syscall allowlist instead of a blocklist, CLI + HTTP/WebSocket API + browser playground. MIT licensed.

Top comment

Hey everyone 👋 I built sandbin because every time I needed to run untrusted code — a user-submitted script, an LLM's output, a coding-challenge submission — the "correct" answer was always "just spin up a Docker container." That's a daemon, root or rootless plumbing, an image pull, and real seconds of cold start for something that should be near-instant. sandbin skips Docker entirely. It's bubblewrap for namespace isolation, seccomp-bpf for a strict syscall allowlist (146 explicitly permitted, everything else returns EPERM — not a blocklist of "known bad" calls), and cgroup v2 for hard memory/CPU/PID ceilings. Cold start is ~20ms — 17.6× faster than Docker by median, measured with the methodology written up in the docs, not just claimed. A submission gets its own PID namespace, its own empty network stack, its own filesystem view, and hard resource ceilings. When it misbehaves — fork bombs, memory bombs, ptrace, raw sockets, nested user namespaces — the test suite proves it dies and the host never notices. 111 adversarial test cases, all against real spawned sandboxes, no mocking: cgroup counters read directly from the kernel, not the guest's own claims about what happened. Three ways to use it: CLI: sandbin run script.py, local or against a remote server with --server HTTP + WebSocket API: submit code, stream stdout/stderr live Browser playground: try it right now at the link below, no install Runs Python, Bash, Node, C, and Go today. It's a side project, MIT licensed, single maintainer — I'd genuinely love feedback, especially from anyone who's fought with Docker-per-request architectures before. And if you find a way to break the sandbox, that's the best kind of comment I could get. 🙂 GitHub: https://github.com/ayazdoruck/sa... Live visual playground: https://sandbin.vercel.app

About sandbin on Product Hunt

Run untrusted code and survive it — no Docker, no root

sandbin was submitted on Product Hunt and earned 2 upvotes and 1 comments, placing #160 on the daily leaderboard. Sandbin runs untrusted code in a real sandbox — bubblewrap + seccomp + cgroups, not a container. No Docker daemon, no root, no VM. ~20ms cold start (17.6× faster than Docker, measured), a 146-syscall allowlist instead of a blocklist, CLI + HTTP/WebSocket API + browser playground. MIT licensed.

On the analytics side, sandbin competes within Open Source, Developer Tools, GitHub and Security — topics that collectively have 633k followers on Product Hunt. The dashboard above tracks how sandbin performed against the three products that launched closest to it on the same day.

Who hunted sandbin?

sandbin was hunted by Ayaz. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.

For a complete overview of sandbin including community comment highlights and product details, visit the product overview.