Anyone can claim expertise. We'd rather show you the systems. Everything below exists, runs, and was built by the three of us.
Our flagship. A content-addressed, airgap-first artifact repository in pure Rust: atomic versioned transactions, O(1) random access into archives, ~2 MB resident memory, and roughly 9× the HTTP throughput of the established JVM repository managers, measured on identical hardware. In early access with pilot users.
Product page →A self-hosted Security Operations Center in a single Rust binary, where an LLM agent investigates every detection with read-only tools (log history, IP intelligence, host baselines, past cases) and posts a triaged verdict to Matrix for about half a cent per investigation, under a hard daily budget. It has watched our own infrastructure 24/7 since spring 2026: embedded Apache Iceberg storage, Sigma detections, correlation rules, eBPF endpoint telemetry, risk-based alerting and a MITRE ATT&CK coverage view.
Read the write-up →A git server and client in Rust that implements the protocol itself: no shell, no git or ssh subprocess, no libgit2, and no database. Refs, keys and grants live in memory and persist through an Apache Arrow IPC log, while stock git 2.53 acts as both client and test judge. SSH and smart HTTP ride one implementation, Git LFS rides the same authorisation, and the whole server is one 15 MB file that runs under systemd, in a scratch container, or as PID 1 on a 29.5 MB ISO with no operating system at all.
Read the write-up →One Rust application over the Swedish open-data stack: Spark pipelines, live graph queries, time-travelling Iceberg tables, maps and investigations. The entire data path, from simulated population through Iceberg to a graph and into the UI, runs from a single command and ships as a bootable appliance that asserts its own output. The whole UI state serialises to JSON several times a second, so the interface is testable headlessly without a display.
Read the write-up →A framework for building distroless VPN client appliances in Rust, where a single binary runs as PID 1, the WireGuard tunnel comes up before any other packet, and the same artifact boots in a QEMU VM or on real hardware. No shell, no package manager, static IP only. A pure-Rust harness builds each appliance, boots it under QEMU + OVMF (UEFI) + KVM, and asserts it reached runtime against a strict boot contract, with content-addressed provenance on every build. Early: the Buildroot track is live, the bare-metal Rust OS variants are still on the drawing board.
Read the write-up →The internal build, benchmark and documentation pipeline behind our products. Its defining feature: every benchmark table in our docs is rendered from an actual measured run, with host, core count and date stamped, so published numbers can never drift from reality. It is why we can put performance claims on this site with a straight face.
Production Kubernetes platforms, AI-assisted document-processing pipelines, systems integration and security hardening for Swedish businesses, including structured production-readiness programs and purple-team exercises. Built, deployed and operated by us. We keep client details private; ask us for references in a conversation.
What we offer →We write about our systems on the blog, and we're happy to go deeper in a call.