Sovereign software platforms

We build it on your servers, hand you the keys, and delete our own.

ESPO Dev deploys a complete software operation — code, pipelines, databases, and an AI build crew — on infrastructure you control. What we hand over runs without us.

Talk to us Read how we work

A practice of ESPO Engineering · Since 1965

Software you cannot leave is software you do not own. Most vendors build dependence — their cloud, their keys, their renewal. We build the opposite: systems that run entirely on your infrastructure, sealed to a master key only you hold, with no escrow, no vendor copy, and no quiet tether back to us. When an engagement ends we delete our access, and the platform doesn't notice. A firm confident in its work builds the exit into the contract.

A complete operation, installed in about an hour.

One command installs code hosting, pipelines, databases, file storage, dashboards, and certificates on machines you control. Nothing is configured by hand, and nothing depends on an outside service.

Eighty-six applications run on the platform today.

The install, in one command

$nix run .#up

✓cluster ready~2 min

✓code hosting onlineyour own git service

✓pipelines onlinetests gate every change

✓databases onlinebacked up to your storage

✓dashboards online60 days of history

✓build crew readygoverned, metered

your platform — master key: yours · our copy: none

Describe the work. Approve what you can see.

Your team files a request in plain language. The build crew delivers a working preview, and an independent inspector attacks it before anything ships. People and AI leave the same permanent record.

Every AI-written change carries its author, model, and session — permanently.

The record — one trail for people and AI

a1f3c92Add intake validation to transport requestsoperations engineer
b7e01d4Rework the export queue for batched runsbuild crew · inspected and approved before release
c4928aaRaise retention on the audit logplatform administrator

Ownership is the deliverable.

Your master key is minted on your machine during the install; there is no second copy anywhere. Engagements end with a handover, not a renewal — the code, the keys, the evidence, the exit.

446 encrypted files, sealed to a single key. Held by you.

The handover, itemized

Source codeyours, in your repositories
Master keyone copy — held by you
Infrastructureyour servers, your accounts
Our accessdeleted
Continuing obligationsnone

0years

ESPO has engineered for organizations whose systems cannot fail since 1965. This practice brings that discipline to software.

Teams run what we build long after we've gone.

The platform's source is public, and every number below is checkable in it.

applications in production on the platform, each in its own sealed compartment

outside dependency in the entire stack — the optional AI model. Everything else is yours

written security rules enforced automatically, readable by your auditors as documents

Read the source

Two ways to engage.

Implementations

Scoped per project. We deploy the complete platform on your infrastructure, verify it end to end, and hand over the only key. It arrives whole — and it runs without us.

Development

Senior hours at $250 an hour — rolling, for steady counsel, or batched for a defined build. Nothing renews on its own.

Every engagement is structured so you can walk away with everything — the code, the keys, the knowledge. That is precisely why clients stay.

Tell us what you're running, and what you'd rather own.

A brief goes straight to the practice. There is no account to create, and a person replies within one business day.

Talk to us Read how we work

Sovereign software platforms

We build it on your servers, hand you the keys, and delete our own.

ESPO Dev deploys a complete software operation — code, pipelines, databases, and an AI build crew — on infrastructure you control. What we hand over runs without us.

Talk to us Read how we work

A practice of ESPO Engineering · Since 1965

A complete operation, installed in about an hour.

One command installs code hosting, pipelines, databases, file storage, dashboards, and certificates on machines you control. Nothing is configured by hand, and nothing depends on an outside service.

Eighty-six applications run on the platform today.

The install, in one command

$nix run .#up

✓cluster ready~2 min

✓code hosting onlineyour own git service

✓pipelines onlinetests gate every change

✓databases onlinebacked up to your storage

✓dashboards online60 days of history

✓build crew readygoverned, metered

your platform — master key: yours · our copy: none

Describe the work. Approve what you can see.

Your team files a request in plain language. The build crew delivers a working preview, and an independent inspector attacks it before anything ships. People and AI leave the same permanent record.

Every AI-written change carries its author, model, and session — permanently.

The record — one trail for people and AI

a1f3c92Add intake validation to transport requestsoperations engineer
b7e01d4Rework the export queue for batched runsbuild crew · inspected and approved before release
c4928aaRaise retention on the audit logplatform administrator

Ownership is the deliverable.

Your master key is minted on your machine during the install; there is no second copy anywhere. Engagements end with a handover, not a renewal — the code, the keys, the evidence, the exit.

446 encrypted files, sealed to a single key. Held by you.

The handover, itemized

Source codeyours, in your repositories
Master keyone copy — held by you
Infrastructureyour servers, your accounts
Our accessdeleted
Continuing obligationsnone

0years

ESPO has engineered for organizations whose systems cannot fail since 1965. This practice brings that discipline to software.

Teams run what we build long after we've gone.

The platform's source is public, and every number below is checkable in it.

applications in production on the platform, each in its own sealed compartment

outside dependency in the entire stack — the optional AI model. Everything else is yours

written security rules enforced automatically, readable by your auditors as documents

Read the source

Two ways to engage.

Implementations

Scoped per project. We deploy the complete platform on your infrastructure, verify it end to end, and hand over the only key. It arrives whole — and it runs without us.

Development

Senior hours at $250 an hour — rolling, for steady counsel, or batched for a defined build. Nothing renews on its own.

Every engagement is structured so you can walk away with everything — the code, the keys, the knowledge. That is precisely why clients stay.

Tell us what you're running, and what you'd rather own.

A brief goes straight to the practice. There is no account to create, and a person replies within one business day.

Talk to us Read how we work