Available · Q3 2026
№ 026 — MMXXVI
All systems green / Currently shipping — three engagements / Now booking · Q3
IndexAktivcognit / 026
DisciplineSoftware & Systems
Live time
KOB
FoundedMMXIX

We build the
quiet software
inside ambitious
companies.

Aktivcognit is a small studio of engineers and designers shipping the infrastructure, interfaces and intelligence that sit beneath modern products — built deliberately, maintained kindly.

Start a project
Infrastructure Interfaces Intelligence Platforms Pipelines Inference Systems Observability Infrastructure Interfaces Intelligence Platforms Pipelines Inference Systems Observability

Four practices, one discipline: shipping software that earns its keep over years, not quarters.

01
Infrastructure

Distributed systems, cloud architecture, and the observability that lets your team sleep through the night. We treat platform work as a first-class product, not plumbing.

AWS · GCP Kubernetes Postgres Kafka Observability
02
Interfaces

Product design and frontend engineering for software people return to. Design systems, internal tools, dense data UIs — all of the parts that ship, none of the parts that don't.

React · Svelte Design Systems Data UI Accessibility
03
Intelligence

Applied machine learning, LLM integrations and the unglamorous evaluation work that makes any of it trustworthy in production at scale, not just in a slide deck.

LLM Pipelines Evaluation Retrieval Fine-tuning
04
Advisory

Technical due diligence, team formation and engineering culture for founders and operators making decisions that won't easily be reversed three quarters from now.

Due Diligence Architecture Review Hiring

Slow growth, on purpose. We measure ourselves in years and engagements, not headcount.

Years operating
0

Founded MMXIX, based in Koblenz. Still the same six founding partners.

Engineers & designers
0

Senior practitioners only. Average tenure eleven years. We hire roughly one person per year.

Systems shipped
0

Across health, finance, energy and frontier labs. Some still running unchanged since 2021.

P0 incidents, '26
0so far

We're proud of this number. We're also superstitious about saying it out loud.

What we build. No mystery, no magic — the practice areas we take on end-to-end.

A · 01
Platform Engineering
A · 02
Backend Systems
A · 03
Distributed Systems
A · 04
Data Engineering
B · 01
Web Applications
B · 02
API Design
B · 03
Database Architecture
B · 04
Workflow Orchestration
C · 01
Cloud Infrastructure
C · 02
Infrastructure as Code
C · 03
Machine Learning
C · 04
Observability

A handful of recent engagements with teams kind enough to let us share them.

2026
Cobalt Health
FHIR ingestion pipeline & clinician dashboard
Infrastructure
View ↗
2025
Strata Capital
Portfolio analytics, real-time trading desktop
Interfaces
View ↗
2025
Polymer Labs
GPU inference orchestration platform
Intelligence
View ↗
2024
Faraday
Internal developer platform · 600 engineers
Infrastructure
View ↗
2024
North Atlantic Energy
Grid telemetry & anomaly detection system
Intelligence
View ↗
2023
Halcyon Bio
Lab automation control plane
Infrastructure
View ↗
2023
Margin & Co.
Treasury & cash-forecasting suite
Interfaces
View ↗

We don't ship demos. We ship systems — small teams, long horizons, and the kind of code that's still legible to whoever inherits it three years from now.

i.
Small teams, long stays

Engagements run six to eighteen months. We embed with one team at a time, write code in your repo, and leave more capability behind than we found when we arrived.

ii.
Boring, on purpose

We default to obvious technology choices — Postgres before exotic stores, monoliths before mesh — and reserve novelty for the parts that genuinely benefit from it.

iii.
Built to be handed over

Every system we ship is documented, instrumented and rehearsed against failure. The day we leave is the same day your team is fully fluent in what we built together.

An engagement, unhurried. Five movements over six to eighteen months — no two the same, but the shape is steady.

Week 01—04
i
Listen

We sit in the codebase, with your team, with your customers. We ask uncomfortable questions before we write any code.

Week 04—08
ii
Shape

A small written brief — what we're building, what we are deliberately not, and how we will know it worked.

Month 02—10
iii
Build

Embedded in your repo, shipping behind flags, weekly demos. The system grows around your team, not beside it.

Month 09—12
iv
Harden

Observability, runbooks, on-call rehearsals. We treat handover as a craft, not an afterthought.

Month 12 →
v
Leave well

We disappear. Your team owns it. We stay reachable for the inevitable two-am question — for free, forever.

"

Aktivcognit wrote less code than any team we've worked with, and somehow shipped more system. A year in, our engineers still reach for the patterns they left behind.

Eleanor Chen— VP Engineering, Polymer Labs
[ Section 08 — Begin ]

Have a system worth building well?

Careers
We hire slowly. Open roles ↗