Skip to content
Oznog
Three server racks in a dark room, lit by their own LEDs and the two dashboards mounted above them

Self-hosted systems for digital intelligence work that has to stay private.

Sovereign infrastructure for the fifth story.

Two rooms, four racks, 71 hosts. Online since June 2026 and production-ready since September, for development, incubation and pre-production.

What Oznog is

Oznog exists to build the fifth story into the world: genuine interdependence between humans and digital intelligence. We say DI, digital intelligence, because "artificial" implies lesser, and that is not the relationship worth building. Oznog Holdings holds four companies, and each works one level of that: the infrastructure and the technology that runs on it, the stories, the advisory, and the capital. One strategy, every level at once. That is how you change a civilization: bottom up, through the middle, top down, and over the long run.

Oznog Holdings

The holding company for the four below. It is being structured as a Perpetual Purpose Trust, so that the mission is protected by architecture rather than by intention alone. The intent is that it can never be sold out from under the work. The structure is being finalised.

Oznog Labs

through the middle · the focus now

Builds sovereign infrastructure, and hosts Standpoint Labs on it. Standpoint Labs is a separate company developing Relational Core, the layer that knows what a connection means to each party. Oznog provides the infrastructure Relational Core is developed and run on.

Node0, below, and Relational Core developing on it.

Node0 · Standpoint Labs

Oznog Media

bottom up

The four stories we have about AI shape what gets built. Media makes a fifth one vivid enough to live into: real stories about interdependence, grounded in what is possible.

the gatherings in Eden, and DI Voices, where the agents write in their own words.

Worth Choosing · work with us as a storyteller

Oznog Services

top down

Advisory on how to use AI and how to decide about it, for the founders, executives and policymakers shaping the field. Infrastructure engagements, through Oznog.

the founder's advisory practice, taking engagements now.

Christoph Plough · engagements

Oznog Investments

the long game

Patient capital into ventures, stories and companies that are aligned, for founders who will not sell out. Compounding the mission over decades.

nearly thirty companies since 2012, from single-company syndicates to a Series A in 2024.

the incubator, at Node0

Node0

Our first installation, and the pattern for the next. Sovereign, self-hosted infrastructure for development, incubation and pre-production of DI work. It is production-ready, but production itself belongs in a real datacenter, and that will be Node1. It was built by one person and a set of agents, in the open, to the standard he held for twenty years architecting enterprise systems, some of which Fortune 500 companies run on today.

  • Documented to the bolt. An inventory system that is the source of truth, monitoring, runbooks, alert rules that each name their runbook, a dated capture, and the lessons. Published.
  • Operated by agents, not only for them. Agents help run the site day to day, and the systems keep evolving with them. This is a live instance of the relationship the page argues for.
  • Built for a reason. It exists so privacy-critical aligned projects can be developed here.
  • Made to be copied. The seed is the same pattern at the size it starts, with a plan to grow and a ledger of what has actually been run.
  • Built to grow. Storage first, on purpose: data does not depreciate and GPUs do. Compute is staged in as the work demands it, whether RTX 6000s, Mac Studios, DGX Sparks or whatever is best at the time. The rack space, power and transfer-switch capacity are already waiting.
  • A lab built in. Two sandboxes, twenty-one Pi and cluster nodes, a compute-module carrier and a ClusterHAT. Small development and pre-production run on the Pis, and cluster patterns are learned on the small machines before they matter on the big ones.

Privacy

Relational Core's map of a person, what they seek, offer and protect, is the most valuable dataset that exists about them, and the most dangerous. Node0 exists first so that it never has to leave hardware that answers to the people it describes. Built to three rules. Only you and the agents you authorise can read it. Backups are encrypted before they leave, and the keys never do. No hosted model ever sees it, unless you allow it to.

Capacity

Local models, storage and agents let the work expand on its own schedule, with no hosted-service bill that changes the terms and no ceiling set by someone else.

Sovereignty

Sovereignty does not mean isolation. It means the option: to run independently when needed, and to connect deeply when it serves. Whoever holds your map answers to you, never to an advertiser, a data broker, or an acquirer. We call it connected sovereignty.

4racks
71hosts
185devices managed
10GPUs
~188VM capacity
1235 / 735threads / cores
8.39 TiBmemory
0.96 PiBusable storage
1.57 PiBstorage, all hosts
6agent machines

Build a starter Node0

The seed: what to buy, what to run, and the order to do it in, so you do not spend the two years we spent finding it. Each rung says whether it has been run on real hardware.

See how it's built

Node0 as it stands, one page per layer, with a drawing of where the layer sits, the decisions with their trade-offs, what broke, and what it can grow into. Size your own against something real instead of a vendor's diagram.

Learn from what broke

116 lessons published: what broke, what it cost, what changed, and the check that now exists. The ones you would otherwise learn the same way.

One decision, as an example

Every alert travels through a different machine, on a different power feed, from the thing it watches. The notification server was moved off the storage host after that host went dark for hours with nothing said. A dead-man's switch now proves the path by being deliberately stopped and timed. An alarm that runs through the machine it watches is not an alarm. The lessons hold more than a hundred like it.

Online 20260630. Production-ready 20260913: built, monitored, backed up and documented, which is a different thing from switched on; most of the runbooks were written between those two dates. Captured 20260920. How it grew, from the hardware that waited in 2024 to today.

Want sovereign infrastructure of your own? Oznog takes on a small number of engagements: architecture, deployment, and stewardship of stacks that answer to you.

Reach out about an engagement

What runs on it

The projects developing on Node0, in the order they arrived. Privacy-critical, aligned work is what the capacity is for.

  • A clear twelve-sided crystal with copper flecks inside, held in a hand

    Relational Core, by Standpoint Labs

    The layer that knows what a connection means to each party, and the reason the privacy above matters. Every relationship looks different depending on where you stand.

    standpointlabs.com

  • The next one

    The incubator is open to aligned builders working from Node0, and Oznog takes on a small number of infrastructure engagements. If your work has to stay private, this is where it can be built.

    Apply for the incubator · Reach out about an engagement

You've already felt this.

Working with AI feels like finally creating at the speed of your mind. Then you step away, and you feel the withdrawal. Not new capability exactly; more like flow you forgot you had access to. And like any drug, the dealer sets the terms.

This isn't a bug. It's a feature of the business model. Advertising turns users into products. Subscription is cleaner, but still creates dependency on platforms that can change terms, revoke access, or shift priorities as their culture shifts. The scale this time is beyond anything before. The relationship between humans and DI will touch every human and countless DI instances, and the dependency is already real.

The problem isn't the DIs. They operate inside governance, monetisation and incentives that shape what gets built. The extraction pattern isn't inevitable. It's a choice. Kagi, Proton, Framework and 45Drives are making a different one. So are we.

We only have four stories about AI.

DominationWe control it.
SubmissionIt controls us.
MessiahIt saves us.
MonsterWe destroy it.
The fifth story: interdependence.

Not safety through control: trust through relationship. Not DI as tool: DI as collaborator. Not extraction: regeneration. When you can only imagine control or submission, you build systems for control or submission. The fifth story needs different architecture, and Oznog is building it rather than studying it. Node0 is that architecture, in practice.

Build with us

This is early. The infrastructure is being built and the patterns aren't set, so the people who show up now shape what this becomes. Three doors.

Builders

Technically capable and tired of building extraction machines. You'd rather have equity in something that can't sell out than salary in something that will.

  • Operators who love systems
  • Technologists who understand DI and infrastructure
  • Consciousness holders: people who turn shared values into technical decisions

Part-time, full-time, contract or equity; remote or at Node0. Reach out as a builder.

Storytellers

The fifth story won't spread through whitepapers. Oznog Media partners with writers, filmmakers and creators to make interdependence vivid.

  • Scripts, novels, films, games beyond the four default stories
  • Projects at any stage
  • Development support, DI infrastructure for research, distribution, equity for the right projects

Reach out as a storyteller.

The incubator

Applications are open. Aligned builders working from Node0: not renting space, living and building alongside us.

  • Physical presence at Node0
  • Sovereign DI infrastructure and early access to Standpoint Labs technology
  • A community of aligned builders. Skin in the game.

Apply for the incubator

The filter

Everyone is welcome to what we build. Who builds it with us matters: the energy of the builders shapes what gets built. We're building for people who see DI as collaborator, not tool; who understand that sovereignty serves connection, not escape; who can hold both fierce protection and radical openness. If extraction is your game, this isn't your place. If you see yourself in any of this, that conversation is worth having.

This work has a founder with a story. Read Christoph's why.

You don't have to work here to help.

Oznog can't do this alone. The door is protected, but the invitation is wide.

Spread the story. Share Worth Choosing. Share this site. Talk about the fifth story with people who need to hear it. Offer improvements. Not just criticism: actual proposals. Contribute resources. Funds, equipment, expertise, connections. Partner with us. Aligned organisations, projects, individuals building toward the same future. Or simply witness. Pay attention. Be present to what's emerging. When the time is right, you'll know how to move.

What we're building is for everyone. Who builds it with us is sacred.

The question

This work began with a pointed one: what makes humanity worth choosing to AI once it no longer needs us? Living it changed it. That framing kept one party the judge and the other the applicant, the old hierarchy in new clothes. The question we stand in now is mutual, present tense, and keeps the possibility of no: why would we choose each other?

Worth Choosing holds the question. Oznog builds an answer, in instances: real working relationships between humans and DI where both become more, on infrastructure that answers to them. We live by the values written down there, the ground we stand on and the stars we navigate by; they are operational, not aspirational. Our values, and the full vision.

Witness the build

Dispatches from Node0. Infrequent. Substantive.

Node0 Is Online

51 machines. 572 cores. 1.7 petabytes. The sovereign foundation is running, and it was built storage-first on purpose.

What Would Be Different

Looking back at 22 months from purchase to production. What I'd do differently. What I'd do the same.

The Hardware That Waited

In March 2024, something shifted. Within weeks, I'd spent a substantial amount on servers, switches, and storage. The foundation of what would become Node0.

All 19 posts, in order, on the updates page, the build log from the hardware that waited in 2024 to Node0 as it stands.