Nexus

Households deserve the capabilities of a cloud — shared identity, photos and documents, applications, private AI agents — without surrendering their data to one. Nexus is that as a product: a physical appliance a non-technical family administers through a web UI, never a terminal. Its design is derived from two frameworks I wrote, on platform architecture and on data-extraction dynamics; the venture is the constructive proof that household data sovereignty is buildable.

The shape of it

Four layers, each knowing only the layer above and below: a bare-metal node controller that must keep working when Kubernetes is down; the k3s substrate; a unified operator that owns twelve platform capabilities as CRDs — identity, databases, TLS, ingress, DNS, storage, registry, brokers — plus the app-lifecycle and request CRDs; and the household applications on top. A custom installer ISO and a guided first-boot wizard take a box to a working household in one evening.

What it proves

• Broker, not store. Applications never hold external-provider secrets; a sole-egress broker injects credentials only on the way out.
• Delegation, not impersonation. A household security-token service mints short-lived, consented, scoped tokens so an agent acts for a member — and custody is architecture, not policy: keys never enter the agent’s context.
• Records, not bytes. The household knowledge graph lives one layer above storage; apps keep their bytes, filtered by Postgres row-level security.
• Live, not a demo. A release and update control plane with staged rollouts and rollback, contract-validated interoperability between every service, self-healing infrastructure — the operational spine a product needs before it can leave the builder’s house.

More at nexus.teknios.tech.