# systemd adopts Rust for standalone components, keeps core libraries in C

> **Key takeaway:** The systemd project will allow Rust in standalone components but prohibits its use in core shared libraries due to compatibility and maintainability concerns.

**Published:** 2026-11-16T07:56:15+00:00 
**Source:** Linux Today 
**Category:** distro-news 
**Canonical URL:** https://fosswire.org/news/systemd-adopts-rust-for-standalone-components-keeps-core-lib.html 

## Summary
The systemd development team has formalized its position on Rust adoption, welcoming the language for standalone components while explicitly excluding it from core shared libraries. This policy reflects a calculated balance between leveraging Rust's memory safety guarantees and preserving the long-term stability of systemd's foundational C-based infrastructure.

The decision affects downstream Linux distributions, embedded vendors, and enterprise users who depend on systemd's predictable ABI and broad architecture support. By compartmentalizing Rust to non-critical components, the project aims to mitigate risks around build system complexity, toolchain portability, and the challenges of maintaining stable interfaces across language boundaries.

## Rust boundaries in systemd's architecture
- **Standalone components only:** Rust is permitted in self-contained systemd components that do not expose shared library interfaces, limiting cross-language ABI complexity.
- **Core shared libraries excluded:** The prohibition on Rust in core libraries preserves stable C ABIs that numerous downstream projects and distributions depend upon.
- **Memory safety rationale:** The policy explicitly acknowledges Rust's memory safety advantages as a motivation for adoption where feasible.
- **Maintainability constraints:** Compatibility concerns and long-term maintenance burden are cited as primary reasons for keeping core infrastructure in C.

## Why it matters
This policy provides clarity for Linux distribution maintainers who must balance Rust toolchain requirements against minimal base system dependencies, particularly for embedded and long-term support releases. The compartmentalized approach may serve as a template for other foundational Linux projects grappling with similar incremental language migration decisions.