FTL: A new operating system for clouds
- ID
- 31672
- Status
- summarized
- Published
- 03 Oct 2026, 11:02 PM
- Fetched
- 05 Oct 2026, 1:27 AM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://ftl-os.org/
- Source URL
- https://hnrss.org/best
Summary
- Score
- 5.5
- Created
- 05 Oct 2026, 1:27 AM
- Tags
- Audience
- developers
What happened
FTL is a proposed cloud OS where each container runs a userspace OS implemented as a shared library (Linux process, VFS, TCP/IP), while a minimal FTL kernel exposes only a hypervisor-like interface — vCPU, memory, drivers — so Linux system calls are implemented in userspace on top of user-mode hardware isolation. The project claims Linux binary compatibility (the Rust HTTP server serving ftl-os.org is a Linux app running on FTL) and that lightweight containers can be made as secure as VMs without bare-metal machines, also allowing Unikernel-style apps without POSIX abstractions. It drew 191 points and 74 comments on Hacker News, but the page shows no benchmarks, release artifacts, download instructions, or version numbers.
Why it matters
This is a design to read, not a platform to adopt this week: there are no syscall-overhead or I/O numbers to compare against gVisor, Firecracker, or plain runc, and no stated release or availability. The one concrete action is to check whether FTL publishes measurements and Linux compatibility coverage — the claim 'containers as secure as VMs' is exactly the claim gVisor already makes, and without numbers you can't tell whether FTL's userspace-OS-as-a-shared-library approach is cheaper or more expensive per syscall.
Discussion angle
If your OS is a shared library you link into each container, who patches it when there's a CVE — and does that model beat gVisor's syscall interception or Firecracker's VM-per-container, given FTL hasn't published a single benchmark yet?