Four domains.
Each one load-bearing.
We did not assemble these as a capability matrix. Each is something one of our five systems forced us to get good at, and each is still in use in production today.
Sovereign infrastructure
Bare metal, immutable operating systems and a network you can reason about. We run our own ASN and sit between Tier-1 transit and the customer edge, which means the routing story is ours to fix rather than a ticket with somebody else.
- ▸ Immutable Talos clusters, GitOps-reconciled end to end
- ▸ Cilium L7 policy, mTLS between workloads, eBPF datapath
- ▸ Anycast and BGP from our own AS207819
- ▸ Private PKI and OIDC — step-ca and Authentik, not a SaaS dependency
Wireless & device management
Firmware at carrier scale across MediaTek Filogic, Qualcomm IPQ and Broadcom BCM, and the management plane that keeps a fleet of them coherent. Bring-up through OTA, plus the standards work — TR-069, USP and the conformance that comes with them.
- ▸ 802.11ax and 802.11be bring-up, radio tuning, mesh
- ▸ TR-069 and TR-369 / USP 1.3 agents and controllers
- ▸ BSP work, security hardening, signed OTA paths
- ▸ Fleets in the millions, multi-tenant by construction
AI & inference engineering
Private model serving where the weights and the prompts stay inside your boundary, and the GPU work underneath it. We maintain a CUDA backend for mistral.rs built on pure Rust kernels rather than a vendored C++ dependency, because the inference path is something we need to be able to fix.
- ▸ OpenAI-compatible gateway, zero retention, EU-only inference available
- ▸ mistralrs-oxide — CUDA backend in pure Rust
- ▸ Quantised serving on constrained GPUs
- ▸ On-device classification for sensor firmware
Embedded & sensing
When the product is a board in a hard place, someone has to own the whole column: the hardware, the firmware, the radio link and the thing that receives it. We design sensor hardware and write what runs on it — including the near-field seismic stack behind glacier.
- ▸ Sensor board design through firmware and field radio links
- ▸ LoRa mesh where there is no backhaul
- ▸ Camera ISP tuning, H.265 / AV1 encode, streaming under WAN jitter
- ▸ Power budgets measured on the bench, not assumed
The same people, all the way down
The team writing firmware is the team operating the cloud your control plane runs on. There is no SDR layer between you and whoever is on call when a chipset throws an oops.
We publish what we can
aether-af and aether-sensord are open source; optimacs has a self-hostable edition that is a single binary and a Postgres. You can read the parts that matter to you.
Claims get audited
Marketing copy on this site is linted in CI against a ledger of what our own validation work supports. Figures that an audit withdrew do not come back as a headline.
Tell us who you are.
We'll tell you which of these actually matters for what you're building — and which parts you would be better off not buying.