What we build
Languages, compilers, runtimes, systems software, packages, binaries, container images, and machine images for specific hardware and operating systems.
Lithespan builds new software and maintains optimized releases of existing projects. Scope is defined by the software, hardware, OS, workload, format, and support term.
Languages, compilers, and runtimes
Work can cover language implementations, compilers, interpreters, standard libraries, build tools, and runtimes across C, C++, Go, Java, JavaScript, .NET, Python, Ruby, Rust, and other languages.
Optimization can cover profiling, PGO, LTO, JIT or AOT policy, garbage collection, allocators, linking, startup, and hardware-specific code paths.
Systems and infrastructure software
Examples include proxies, schedulers, container tooling, data planes, messaging systems, databases, caches, storage, and other native software. Tests preserve the workload’s durability, topology, failure, kernel, network, and storage assumptions.
Packages, binaries, and images
Native outputs target a specific distribution, libc, system ABI, architecture, and dependency set. Delivery can include Debian, RPM, Alpine, FreeBSD, Nix, and signed archives.
OCI images use the same tested payload. Machine images can combine the OS, kernel, drivers, runtimes, libraries, and application configuration for a defined fleet. Outputs can include AMIs, Azure managed images or VHDs, Google Cloud custom images, qcow2, and OVA.
Image tests can cover boot, workload behavior, upgrades, rollback, and failure recovery. Immutable references connect each output to its benchmarks, compatibility results, SBOM, provenance, and support record.
What becomes a stable release
A release becomes stable when Lithespan can maintain its source watch, tests, benchmark baseline, build pipeline, outputs, and support date. See the release process.