TL;DR
Get monitors, keyboards and dev 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 is an early operating-system project that runs a separate userspace OS library for each container, using a minimal kernel interface. Its developers say the design could combine container flexibility with stronger isolation, but the project is in an early release stage and has not supplied independent security or performance results.
FTL’s developers have introduced a userspace operating-system design for cloud workloads, in which each container runs its own OS as a library above a minimal kernel. The project says this architecture can run Linux binaries while making containers easier to extend and safer to update; those security and performance benefits remain project goals, not independently demonstrated results in the material provided.
Under the proposed architecture, each container includes a shared library implementing operating-system functions such as process management, virtual filesystems and TCP/IP. The FTL kernel supplies a smaller interface for functions including virtual CPUs, memory and drivers. The project compares that interface to a hypervisor, while describing the userspace OS as responsible for much of what a conventional kernel would handle.
FTL says the design can support Linux-compatible applications as well as specialized programs that do not depend on POSIX abstractions. As an example, its website says the Rust-based HTTP server serving the project site is a Linux application running on FTL. The source does not provide independent testing or detailed compatibility results for that demonstration.
The project also says developers can modify OS features in userspace, potentially adding debugging output, security updates or other changes without kernel or eBPF programming. Its roadmap lists a simple Linux HTTP server in v0.0.1 and asynchronous Rust application support in v0.1.0 as released milestones, followed by planned filesystem work, Node.js and Go support, and SMP, container images and 64-bit Arm support.
A Different Boundary for Cloud Containers
FTL targets a persistent trade-off in cloud infrastructure: containers are lightweight and convenient, but their isolation model and shared operating-system foundations differ from the boundary provided by a virtual machine. The developers say FTL aims to make lightweight containers as secure as VMs while retaining performance. If later testing supports that claim, the model could give operators more flexibility in how they package and update software.
Moving more OS behavior into an application-level library could also let developers tailor an environment to a workload rather than wait for changes to a shared host kernel. That may be useful for services that need custom debugging or faster feature updates. But the approach also places responsibility on the userspace OS implementation: its reliability, compatibility and isolation properties will matter to anyone considering it for production.
For now, readers should treat FTL as an early project rather than an established cloud platform. The published material describes an architecture and a development plan, but does not include comparative benchmarks, a security audit, or evidence of broad deployment. Those omissions make it too soon to judge whether the proposed design will deliver its stated balance of security and speed.
As an affiliate, we earn on qualifying purchases.
How FTL Splits Kernel Responsibilities
In a conventional Linux system, applications make system calls to a kernel that provides services such as process and memory management, networking and device access. FTL’s diagram instead places a userspace OS between applications and the FTL kernel. That library implements many OS concepts and translates application needs through the smaller kernel interface.
The project presents this as a combination of ideas associated with microkernels and monolithic kernels: flexible OS components outside the kernel, alongside a direct interface intended to keep the system simple and performant. Its site says users do not need bare-metal machines. The source material does not specify the supported deployment environments or hardware requirements, so the practical scope of that claim remains unclear.
The roadmap gives a staged view of development. It marks the September 2026 HTTP-server milestone and October 2026 asynchronous Rust support as released, with filesystem work listed for November, Node.js and Go for December, and SMP, container images and 64-bit Arm for January 2027. These are dates and statuses published by the project; the supplied source does not independently verify releases beyond its own roadmap.
“You can build your own OS as a library.”
— FTL project website
As an affiliate, we earn on qualifying purchases.
Security and Compatibility Still Need Testing
The available project description does not include independent security evaluations, performance benchmarks or comparisons with Linux containers and virtual machines. It is also not clear how much of the Linux system-call interface is supported, which workloads have been tested, or what limitations apply to running applications in the current releases.
The roadmap lists several features as future work, including filesystems, Node.js and Go support, container images, SMP and 64-bit Arm. The source does not establish whether those items remain on schedule or whether releases have changed since the roadmap was published. Claims about security equivalence and performance therefore remain unverified goals.
As an affiliate, we earn on qualifying purchases.
Roadmap Sets the Next Milestones
According to the published roadmap, the next listed development step after asynchronous Rust support is filesystem work in November 2026, followed by Node.js and Go support in December. SMP, container images and 64-bit Arm support are listed for January 2027. These are project schedules, not guarantees that features will ship on those dates.
The most useful evidence to watch for will be updated release notes, details on Linux compatibility, and reproducible security and performance testing. Those would help establish whether FTL’s userspace design works beyond its initial examples and whether it can meet the project’s stated goals for cloud deployments.
As an affiliate, we earn on qualifying purchases.
Key Questions
What is FTL?
FTL is an operating-system project that runs a userspace OS library for each container, with a minimal kernel providing lower-level services such as memory and drivers.
Can FTL run Linux applications?
The project says it is compatible with Linux binaries and identifies a Rust-based HTTP server running on FTL as an example. The supplied material does not give broad compatibility test results.
Has FTL shown that its containers are as secure as VMs?
No independent security findings are included in the source material. Making lightweight containers as secure as VMs is described as FTL’s goal, not as a proven result.
What features are planned next?
The roadmap lists filesystem support for November 2026, Node.js and Go support for December, and SMP, container images and 64-bit Arm support for January 2027. The dates are planned milestones and may change.
Source: hn
Fall Picks
fall essentials
As an affiliate, we earn on qualifying purchases.
