Lagon

What Lagon actually is

Lagon is (or, more accurately now, was) an open-source runtime and platform for running TypeScript and JavaScript serverless functions at the edge. The pitch was the one every Cloudflare Workers competitor makes: write functions against standard Web APIs — Request, Response, fetch() — deploy them globally, and serve requests close to users with cold starts in single-digit milliseconds. Lagon's own site claims 2ms. The runtime is written in Rust on top of V8 isolates, the same execution model used by Cloudflare Workers and Deno Deploy, and it follows WinterCG conventions so that ordinary npm packages and frameworks could run on it.

The feature list was surprisingly complete for an alpha. Every function got a unique URL and could carry custom domains; cron triggers fired functions on a schedule; preview deployments could be promoted to production, or rolled back, in seconds; and the dashboard held realtime logs and usage analytics. Deployments arrived through a CLI, a browser playground or a GitHub Action, with HTTP/2, gzip and Brotli compression and automatic HTTPS as standard. The target workloads were the usual edge set — APIs, server-rendered websites, webhooks and cron jobs — and the compatibility goal was deliberate: Web-standard APIs so that frameworks and npm packages written for other WinterCG runtimes would largely work unchanged. Lagon positioned itself as an open-source alternative to Cloudflare Workers, Deno Deploy and Fastly's edge platform.

The project was started in 2022 by Tom Lienard, and its full stack — runtime, serverless HTTP entrypoint, CLI, dashboard and integrations — was published on GitHub under AGPL-3.0. You could use Lagon Cloud (alpha access via waitlist) or self-host the whole platform on your own infrastructure. That dual story is what made it interesting in our edge computing coverage: an open-source Workers alternative you could actually run yourself, with cron triggers, custom domains, preview and production deployments, rollback, realtime logs and analytics in the dashboard.

All of that ended in a way that matters more than any feature list. Lagon is discontinued. The GitHub organisation states the project was acquired by Vercel — Lienard's own profile now reads "Compute @ Vercel, founder of @lagonapp (acquired by Vercel)" — and the repository was archived on 15 March 2026, making the code read-only. Third-party documentation updated in step: Nitro's deploy docs now describe Lagon as "discontinued from private Alpha" and tell users to migrate to another edge provider. Lagon never left alpha; the cloud never opened beyond a waitlist.

We are keeping this review live for readers who still land on lagon.app, because the website is still up and still advertises a live product — "deploy in seconds", "14 regions", "get a generous free tier" — with no banner about the shutdown. Marketing pages outliving the product is common; knowing the difference is what a review is for.

Pricing: what you really pay

At the time it operated, Lagon was free. Access to Lagon Cloud was gated by a waitlist during the alpha, and the site promised a "generous free tier" with pay-as-you-go pricing by request count afterwards. Concrete per-request rates were never published on a pricing page we can still reach — the pricing URL now returns nothing — so there is no price table to reproduce and no way to model what the service would have cost at scale.

Today the only price is zero, in a different sense: the code is free under AGPL-3.0 and you can self-host it. We would treat that as a source-code acquisition rather than a product. There is no vendor to invoice, no paid support tier, and no hosted service to buy; anything you run, you run and maintain yourself. If budget is the driving concern in your serverless platforms decision, Cloudflare Workers' free tier, Deno Deploy's free tier and Koyeb's free instance are all live, staffed products that cost nothing to start with.

Performance & infrastructure

The engineering underneath was genuinely credible for an alpha. V8 isolates give near-zero cold starts compared with container-based functions, because an isolate is a lightweight sandbox rather than a booted process — Lagon's 2ms claim, while unverified by us, is the right order of magnitude for that model. The runtime exposed native Web APIs, deployed via CLI, dashboard playground or GitHub Action, served HTTP/2 with gzip and Brotli compression, and terminated TLS automatically. The cloud reportedly spanned 14 regions.

We have not benchmarked Lagon and never ran it: our benchmarks page covers raw cloud VMs from Hetzner, DigitalOcean, UpCloud, Vultr and Linode, not edge runtimes, and this product was never generally available for us to test. Anyone quoting performance numbers for Lagon today is quoting marketing copy.

For self-hosters, the honest assessment is that a Rust/V8 isolate platform is a real asset but also a real commitment. The repo's own status line was explicit: alpha, missing features, bugs to fix, breaking API changes. That was the state of maintenance while the team was still working on it. Now that the repository is archived and the team works on Vercel's compute platform, there will be no compatibility fixes for new V8 versions, no security patches, and no answered issues. Running an unmaintained JavaScript runtime that parses untrusted code on your own servers is a risk we would not take on production traffic.

The AGPL-3.0 licence is worth pausing on, because it shapes what the code is good for. It is the strongest common copyleft in wide use: if you run a modified version and offer it to users over a network, you must publish your source. Inside a company's private tooling that is manageable; for a commercial hosted platform built on Lagon it means your improvements cannot stay proprietary. That choice is one reason the code remains genuinely free to study and reuse, and one reason no hosted Lagon successor has appeared. For forks, the practical bar is not the licence but the V8 treadmill: a JavaScript engine needs constant updates for performance and security, and an archived repository stops running that treadmill for you.

Where it falls short

The first line of any honest review is the product's discontinuation. Lagon was acqui-hired by Vercel and the cloud shut down from private alpha; the repo is archived. There is no roadmap, no support channel that will answer, and no hosted service behind the website that is still advertising one.

Second, maturity — even before the shutdown. Lagon never reached beta: its own README listed missing features, breaking API changes and bug debt as the standing state. There was no SLA, no published pricing, no status page history to judge reliability against, and a community measured in GitHub stars (1,340 on the main repo) rather than production users.

Third, ecosystem depth. Framework integrations existed (Remix, Astro, a GitHub Action, a web-platform-tests runner for standards compliance), but the surface area was a fraction of Cloudflare Workers' or Deno Deploy's. Compatibility gaps showed up exactly where users feel them: APIs that Workers supports and Lagon did not yet.

Finally, the website problem. lagon.app still presents a functioning service, complete with a waitlist link and feature tour. If you arrived here from a stale bookmark or an old comparison article: the product is gone, and the correct next step is migration, not sign-up.

Who should pick this

Nobody should pick Lagon as a hosted platform today — it does not exist anymore. If you are looking for what it offered, the honest shortlist is Cloudflare Workers (the broadest edge runtime and the biggest free tier), Deno Deploy (closest in Web-API philosophy), Fastly Compute, or Vercel's own edge functions, which is where Lagon's team and technology now live.

If you still have functions running on a self-hosted Lagon somewhere, plan the migration now rather than after an incident. The closest API surface is Cloudflare Workers — many functions port across with modest changes — while Deno Deploy matches the Web-API philosophy most closely and Fastly Compute covers the compiled end of the same idea. Check each function's dependencies against the target's supported APIs, re-create cron triggers in the new provider's scheduler, and repoint DNS last. The portability WinterCG bought you is real; it is the one durable benefit of having built on Web standards instead of a vendor SDK.

There is one audience for whom Lagon still matters: self-hosters and researchers who want an AGPL-3.0 reference implementation of a Rust/V8 isolate edge platform. For learning, for internal tooling on isolated networks, or as a starting point for a fork with its own maintainers, the code is a legitimate resource. We would frame that as archaeology with potential, not as infrastructure. If you do fork it, budget for a V8 upgrade path and a security process first.

Key takeaways

• Lagon is discontinued: acquired by Vercel, cloud shut down from private alpha, GitHub repo archived on 15 March 2026.
• The code remains available under AGPL-3.0 — a Rust runtime on V8 isolates with CLI, dashboard and WinterCG-style Web APIs.
• It never left alpha: no SLA, no published pricing, breaking API changes documented by the project itself.
• lagon.app is still online and still advertises a live product; treat it as a historical page, not a sign-up form.
• For hosted edge functions today, look at Cloudflare Workers, Deno Deploy, Fastly Compute or Vercel — not at Lagon.
• Self-hosting the archived code is viable only if you are prepared to own V8 upgrades and security maintenance yourself.

Sources

• https://lagon.app/
• https://lagon.app/blog-unveiling-the-new-website.html
• https://github.com/lagonapp/lagon
• https://github.com/nitrojs/nitro/commit/17f922aa
• https://github.com/QuiiBz
• https://toolradar.com/tools/lagon
• https://dev.to/tomlienard/v8-isolates-are-taking-over-the-world-3h4m