Engineering primitives for software

Other disciplines solved their primitives a century ago.

Tolerances, standards, materials tables — mature engineering rests on components that cannot surprise you. Software is still improvising. We build the missing ones, rock solid.

See the workWhy we build
§1 · What we mean by primitive
A1

Load-bearing by definition

A primitive is a component everything else depends on. If it bends, the structure above it bends with it.

A2

Done means predictable

A primitive is not done when it works; it is done when it cannot surprise you. Every claim ships with its tolerance.

A3

Proof over promise

Mature disciplines certify their components. Ours should too — verification built in, not audited after.

§2 · The portfolio
PRODUCT

zegit

The verification primitive: a governance gateway in front of the Git host you already use. Every push carries a signed attestation of what was validated; every release is a quorum-approved tag request that yields an evidence bundle you can verify offline, mapped to the Cyber Resilience Act.

Visit zegit →
PRACTICE

Consulting

GitOps and SRE-based infrastructure, change and incident processes, supply-chain security under the Cyber Resilience Act — the same first principles, applied to your organization.

THE BOOKS

Modern Platform Engineering

Three volumes — principles, practices, patterns — on the missing production leg of software. Complete first drafts, in review.

§3 · The founders
JCLCo-founder · chief engineer · chair of the board

Jonas Cronholm Lundin

Mechanical and welding engineer by training, with industrial engineering and management as his master's subject and further studies at the Stockholm School of Economics. A career in finance and IT operations, and the architectural baseline that comes with it. Wrote Modern Platform Engineering. Based in Enköping.

MLCo-founder · chief engineer · board member

Markus Langenoja

Mechanical and welding engineer by training, specialised in machine design. Started in hardware mechanical engineering and structural mechanics, then moved through agile and project management into building management systems for cybersecurity and business architecture. Based in Stockholm.

We both build the primitives. Two chief engineers who do the engineering themselves, share the responsibility for what we ship, and share the drive. Since we started working together: GitOps and SRE-based infrastructure, processes and security solutions; change and incident processes we would set against any in the industry; and, in the last year, agentic development at the frontier — with the evidence to show for it.

§4 · Why we build

Friction builds.

We are tired of the state of IT. Of its immaturity; of the absence of base research; of an industry that cannot bring itself to learn from peer disciplines that solved its long-standing problems decades ago.

Tired of security tacked on afterwards, and of paper-pushing across the industry: frameworks and paperwork that stand in for the work, and that mostly serve those who can stay away from the source code and from the truth recorded in Git.

We believe friction builds. We believe that to be called an engineer means something: to build; to rise above the day's ticket and look at the bigger picture; to architect elegant, reproducible solutions to primitive problems. And to retire the paper product — risk management, security, quality assurance, incident management, change management as documents about the work — by making the work itself carry the evidence. Everything as code.

How we work
A4
Tolerances are declared

Every estimate, every claim, every interface says how wrong it is allowed to be. Surprises are defects.

A5
Small, senior, accountable

No layers between the person who decides and the person who builds. Often the same person.

A6
Proof is a feature

If we cannot show it, we do not say it — in the product, in the sales deck, in the standup.

A7
Everything as code

Infrastructure, policy, process, evidence: declared in Git, changed through the pipeline, reconciled continuously. What is not in the repository does not exist.

§5 · Contact

Building on something that shouldn't bend? Talk to us.

hello@primitive-engineering.se