TL;DR
Get networking and server gear delivered free — and shop member deals
- Fast, free delivery on millions of items
- Access to Prime Big Deal Days deals on October 6–7
- Prime Video, Amazon Music and more included
FTL’s developers describe a cloud-oriented operating system design in which each container runs a userspace OS library above a minimal kernel. The project reports Linux HTTP server support in v0.0.1 and async Rust application support in v0.1.0; its claims about security, performance and future capabilities have not been independently established in the supplied material.
The developers of FTL are presenting a new operating-system design for cloud workloads that moves much of the operating system into a library running in userspace inside each container. The project says its early releases can run a Linux HTTP server and support async Rust applications, while its broader aim is to make lightweight containers as secure as virtual machines without giving up performance.
According to the project website, each FTL container runs its own userspace OS, implemented as a shared library. That library is intended to provide operating-system functions such as Linux process handling, a virtual filesystem and TCP/IP networking. A smaller FTL kernel supplies the underlying mechanisms, including virtual CPUs, memory and drivers, and a minimal interface through which the userspace OS implements Linux system calls.
FTL says this arrangement can run Linux binaries as well as specialized applications that do not need POSIX interfaces. As an example, the site says the Rust-based HTTP server serving the FTL website is a Linux application running on the system. The project’s roadmap marks a simple Linux HTTP server as released in v0.0.1 in September 2026, and async Rust app support, including Linux threads and epoll, as released in v0.1.0 in October 2026.
The roadmap lists a filesystem for November 2026, Node.js and Go support for December, and SMP, container images and 64-bit Arm support for January 2027. These are presented as planned milestones, not as completed features. The supplied project material does not include independent testing or performance and security measurements.
A Different Boundary for Cloud Containers
FTL’s design targets a long-running cloud infrastructure trade-off: conventional containers share a host kernel, while virtual machines typically use a hypervisor boundary and run separate guest operating systems. The project proposes placing more OS functionality in a library for each container while keeping a smaller kernel underneath. If the design works as described, it could give application developers more control over operating-system behavior without requiring them to change the host kernel.
The potential implications include easier debugging and updates, as well as application-specific changes to OS features. FTL says developers could add logging, apply security fixes and extend Linux functionality from userspace rather than through kernel or eBPF programming. Those are project claims and design goals, not demonstrated outcomes in the source material. Whether they translate into stronger isolation, simpler operations or acceptable performance will depend on implementation details and testing.
As an affiliate, we earn on qualifying purchases.
How FTL Splits OS Responsibilities
In a conventional Linux setup, applications make system calls into the Linux kernel, which handles services such as processes, memory, networking and device access. FTL’s published diagram instead places a userspace OS between Linux applications and a minimal kernel interface. The application can use Linux-compatible interfaces, while the library supplies many OS concepts that a traditional kernel would handle.
The project describes this as combining flexibility associated with microkernels and simplicity and performance associated with monolithic kernels. That is the developers’ characterization, not a verified comparison. FTL also says it does not require bare-metal machines, positioning the system for use on cloud infrastructure rather than limiting it to direct hardware deployment. The available material does not specify supported cloud providers, production deployment procedures or compatibility limits.
“You can build your own OS as a library.”
— FTL project website
As an affiliate, we earn on qualifying purchases.
Security and Performance Still Need Testing
The project’s central claims about isolation, security and performance remain unverified in the supplied source material. It does not provide benchmark results, threat-model details, third-party audits or comparisons with existing container and virtual-machine systems. The claim that FTL isolates containers better than existing monolithic kernels is therefore attributable to the project, rather than established here.
It is also unclear how broad Linux binary compatibility is, which workloads are supported beyond the examples and roadmap, and what limitations apply to networking, filesystems and device access. The site marks some roadmap items as released but provides no release notes or test results in the source provided. Those details will matter to operators deciding whether FTL can support production services.
As an affiliate, we earn on qualifying purchases.
Roadmap Milestones Through January 2027
The next listed milestone is filesystem support, scheduled for November 2026, followed by Node.js and Go support in December. The January 2027 plan adds symmetric multiprocessing (SMP), container images and 64-bit Arm support. These dates are the project’s roadmap and could change; the supplied material does not identify a separate launch date for general availability or production use.
Readers evaluating the system will need further releases and documentation to establish how the planned features work, how compatible it is with Linux applications, and how its isolation and speed compare with existing options. The project points readers to its GitHub repository and an introductory blog post for additional information.
As an affiliate, we earn on qualifying purchases.
Key Questions
What is FTL?
FTL is a project describing an operating system for cloud workloads in which each container runs a userspace OS library above a minimal kernel.
Can FTL run Linux applications?
The project says FTL is compatible with Linux binaries and reports a Linux HTTP server example. The supplied material does not define the full scope or limits of that compatibility.
Which FTL features are marked as released?
The roadmap marks a simple Linux HTTP server in v0.0.1, September 2026, and async Rust application support in v0.1.0, October 2026, as released.
Has FTL proved that it is as secure as a virtual machine?
No such proof is included in the supplied material. Matching VM security is described as an FTL project goal; independent security testing and detailed comparisons are not provided.
What features are planned next?
The roadmap lists a filesystem in November 2026, Node.js and Go support in December, and SMP, container images and 64-bit Arm support in January 2027. These are planned milestones, not confirmed releases.
Source: hn
Fall Picks
fall essentials
As an affiliate, we earn on qualifying purchases.
