QuickBEAM – run JavaScript as supervised Erlang/OTP processes
QuickBEAM is a JavaScript runtime embedded inside the Erlang/OTP VM.If you’re building a full-stack app, JavaScript tends to leak in anyway — frontend, SSR, or third-party code.QuickBEAM runs that JavaScript inside OTP supervision trees.Each runtime is a process with a `Beam` global that can: - call Elixir code - send/receive messages - spawn and monitor processes - inspect runtime/system stateIt also provides browser-style APIs backed by OTP/native primitives (fetch, WebSocket, Worker, BroadcastChannel, localStorage, native DOM, etc.).This makes it usable for: - SSR - sandboxed user code - per-connection state - backend JS with direct OTP interopNotable bits:- JS runtimes are supervised and restartable - sandboxing with memory/reduction limits and API control - native DOM that Erlang can read directly (no string rendering step) - no JSON boundary between JS and Erlang - built-in TypeScript, npm support, and native addonsQuickBEAM is part of Elixir Volt — a full-stack frontend toolchain built on Erlang/OTP with no Node.js.Still early, feedback welcome.
FL score
out of 100
Verdict
medium confidence
Competition
3
competitors found, emerging market
Trend
No signal yet
QuickBEAM offers a highly innovative, integrated JavaScript runtime within Erlang/OTP, solving significant pain for a niche but critical developer audience, but faces extreme build complexity for a solo founder.
The pain
The gap
Build angle
Strengths
- Addresses a highly specific and painful problem for a technical audience.
- Offers a unique, deeply integrated technical solution with a strong defensible moat.
- Clear value proposition: improved performance, reliability, and simplified development.
- Existing community interest (Hacker News, podcast).
Risks
- Extremely high build complexity and technical demands for a solo builder, potentially taking years.
- Monetization pathway is unclear for a standalone open-source project; commercial support or enterprise features required.
- Niche market size limits potential for massive scale compared to broader developer tools.
- Developer inertia/resistance to adopting a new JS runtime architecture.
Next steps
- Validate developer willingness to pay for a commercial version or support, given existing free alternatives.
- Break down the 'narrowest wedge' MVP into a truly minimal, shippable product that delivers core value quickly.
- Assess personal expertise and resources required to tackle the immense engineering challenge; consider co-founder or team if proceeding.
- Conduct in-depth interviews with target developers to confirm specific feature priorities and pain points QuickBEAM could solve first.
Fly Labs Method
Is the pain real, is there a gap, is it the right time, can one person build it.
- Problem clarity
- 27
- Solution gap
- 22
- Willingness to pay
- 14
- Buildability
- 5
High potential if the technical hurdle can be overcome; addresses a clear, specific pain for a niche but important audience, but the build complexity for a solo builder is extreme.
Value Equation
Dream outcome and how likely it feels, against the time and effort it costs.
A high-value, differentiated technical product for a niche market with good growth, but very high build complexity and a long path to monetization.
One-Person Business
Curiosity pull, identity fit, and a path from free value to paid for a solo creator.
A clear problem for a niche audience, but extremely complex to build and monetize as a solo venture.
Viral Frameworks
Hook strength, shareability, and how cheaply it can be tested.
Strong value proposition and specific audience, but challenging business model, high technical risk, and not ready for quick validation.
Builder Lens
Evidence the problem exists, timing, defensibility, and a model that fits on a napkin.
Strong core problem and desperate users, but the MVP is still a significant technical challenge.
Why this verdict
Five lenses, one composite. How scoring works
The angle
This weekend
- Validate developer willingness to pay for a commercial version or support, given existing free alternatives.
- Break down the 'narrowest wedge' MVP into a truly minimal, shippable product that delivers core value quickly.
- Assess personal expertise and resources required to tackle the immense engineering challenge; consider co-founder or team if proceeding.
- Conduct in-depth interviews with target developers to confirm specific feature priorities and pain points QuickBEAM could solve first.
Who is already there, emerging market
- AtomVMVisit
A minimal Erlang VM that runs unmodified BEAM binaries on small systems like MCUs, supporting a subset of ErlangVM features.
Pricing: Open source (Free)
- LunaticVisit
An Erlang-inspired actor system for WebAssembly, allowing multiple programming languages to run in a fault-tolerant environment.
Pricing: Open source (Free)
- erlv8 / Beam.JSVisit
An older project that aimed to integrate V8 (JavaScript engine) with Erlang, allowing JavaScript to interact with Erlang's messaging system.
Pricing: Open source (Free)
What they charge
Recent news
- Show HN: QuickBEAM – run JavaScript as supervised Erlang/OTP processes
Hacker News, March 29 2026
- GitHub - elixir-volt/quickbeam: JavaScript runtime for the BEAM — Web APIs backed by OTP, native DOM, and a built-in TypeScript toolchain.
GitHub, March 31 2026
- Thinking Elixir Podcast 297: JavaScript Joins the BEAM?
YouTube, March 31 2026
- GitHub - elixir-volt/quickbeam: JavaScript runtime for the BEAM - daily.dev
daily.dev, March 30 2026
Market signals
The market for integrating JavaScript runtimes directly into the Erlang/OTP VM appears to be a niche, but growing, area driven by the desire to leverage Erlang's fault tolerance and concurrency with the widespread use of JavaScript. Recent activity around QuickBEAM suggests renewed interest in this specific problem space. While there isn't a large number of direct competitors, the general trend towards polyglot persistence and leveraging the strengths of different runtimes (like the BEAM for reliability) is a key trend. No specific large funding rounds were identified for direct competitors, but the underlying Erlang/Elixir ecosystem sees ongoing development and adoption, which indirectly supports such innovations.
What frustrates people
- The overhead of traditional inter-process communication (like HTTP or JSON over stdout) between JavaScript (Node.js) and Erlang/Elixir for high-performance, low-latency asynchronous event processing is a significant pain point.
- The complexity and difficulty of debugging performance issues in asynchronous Node.js applications compared to the actor model in Erlang/Elixir.
- The desire for JavaScript runtimes to benefit from Erlang/OTP's supervision trees for fault tolerance and automatic restarts.
- The lack of a unified way to handle web APIs, native DOM, and build toolchains when integrating JavaScript with Erlang/Elixir, leading to fragmented development experiences.
Semble – Code search for agents that uses 98% fewer tokens than grep
Hey HN! We (Stephan and Thomas) recently open-sourced Semble. We kept running into the same problem while using Claude Code on large codebases: when the agent can't find something directly, it falls back to grep, reading full files or launching subagents. This uses a lot of tokens, and often still misses the relevant code. There are existing tools for this, but they were either too slow to index on demand, needed API keys, or had poor retrieval quality.Semble is our solution for this. It combines static Model2Vec embeddings (using our latest static model: potion-code-16M) with BM25, fused via RRF and reranked with code-aware signals. Everything runs on CPU since there's no transformers involved. On our benchmark of ~1250 query/document pairs across 63 repos and 19 languages, it uses 98% fewer tokens than grep+read and reaches 99% of the retrieval quality of a 137M-parameter code-trained transformer, while being ~200x faster.Main features:- Token-efficient: 98% fewer tokens than grep+read- Fast: ~250ms to index a typical repo on our benchmark, ~1.5ms per query on CPU (very large repos may take longer)- Accurate: 0.854 NDCG@10, 99% of the best transformer setup we tested- MCP server: drop-in for Claude Code, Cursor, Codex, OpenCode- Zero config: no API keys, no GPU, no external servicesInstall in Claude Code with: claude mcp add semble -s user -- uvx --from "semble[mcp]" sembleOr check our README for other installation instructions, benchmarks, and methodology:Semble: https://github.com/MinishLab/sembleBenchmarks: https://github.com/MinishLab/semble/tree/main/benchmarksModel: https://huggingface.co/minishlab/potion-code-16MLet us know if you have any feedback or questions!
AI
Postgres extension for BM25 relevance-ranked full-text search
Last summer we faced a conundrum at my company, Tiger Data, a Postgres cloud vendor whose main business is in timeseries data. We were trying to grow our business towards emerging AI-centric workloads and wanted to provide a state-of-the-art hybrid search stack in Postgres. We'd already built pgvectorscale in house with the goal of scaling semantic search beyond pgvector's main memory limitations. We just needed a scalable ranked keyword search solution too.The problem: core Postgres doesn't provide this; the leading Postgres BM25 extension, ParadeDB, is guarded behind AGPL; developing our own extension appeared daunting. We'd need a small team of sharp engineers and 6-12 months, I figured. And we'd probably still fall short of the performance of a mature system like Parade/Tantivy.Or would we? I'd be experimenting long enough with AI-boosted development at that point to realize that with the latest tools (Claude Code + Opus) and an experienced hand (I've been working in database systems internals for 25 years now), the old time estimates pretty much go out the window.I told our CTO I thought I could solo the project in one quarter. This raised some eyebrows.It did take a little more time than that (two quarters), and we got some real help from the community (amazing!) after open-sourcing the pre-release. But I'm thrilled/exhausted today to share that pg_textsearch v1.0 is freely available via open source (Postgres license), on Tiger Data cloud, and hopefully soon, a hyperscalar near you:https://github.com/timescale/pg_textsearchIn the blog post accompanying the release, I overview the architecture and present benchmark results using MS-MARCO. To my surprise, we were not only able to meet Parade/Tantivy's query performance, but exceed it substantially, measuring a 4.7x advantage on query throughput at scale:https://www.tigerdata.com/blog/pg-textsearch-bm25-fu
AI
Consus (YC F24) – LLM gateway for companies handling sensitive data
Hey Hacker News! I'm Eric, the founder of Consus. We route all AI requests to ITAR restricted and controlled unclassified information (CUI) compliant infrastructure. Consus itself satisfies ITAR restrictions, and we recently completed our FedRAMP equivalency audit against the 410 FedRAMP High controls. FedRAMP High is the U.S. government’s strictest security baseline for cloud services handling sensitive unclassified data. A breach of this data could cause severe or catastrophic harm. Achieving FedRAMP equivalency, or authorization, is required before processing CUI information.Demo: https://youtu.be/6MYxJe6P4oYAerospace and defense is experiencing rapid growth. Unfortunately, most companies are struggling to use AI because of necessary data protections & compliance risk. These companies can move even faster if they could use the AI tools that most other industries take for granted.I spent most of my career prior to Consus in aerospace & defense. I launched national security payloads at SpaceX, and was an early employee at Castelion. I’ve watched first hand how compliance red-tape makes it difficult for companies to adopt new technologies and trust vendors that touch their sensitive data. For example, I worked with a satellite manufacturer that doesn’t allow any AI tools, even for non-sensitive work.Even as AI has become extremely useful over the past 9-12 months, I was surprised by how many aerospace & defense companies refused to touch it. They could see how it could be helpful, but they were scared about model providers training on their data, violating an ITAR rule, or risk losing new business because of a failed cyber assessment. These are all rational fears.There were a lot of ways to solve some/all of these problems, but we focused on building a compliant AI inference layer that can "plug" into any AI tool or workflow. Just as OpenRouter integrates with most tools, Consus can connect to tools like ChatGPT or Clau
AI
Questions about this idea?
FlyBot reads the scoring and gives you a second opinion on “QuickBEAM – run JavaScript as supervised Erlang/OTP processes”.