Sovereign life infrastructure — a personal operating system built on self-hosted, privacy-first, EU-sovereign technology. Your digital life belongs to you and no one else.
Most people think of infrastructure as something external — roads, servers, power grids. idea2.life begins from a different premise: your life has an operating system, whether you designed it or not. The question is whether that OS was chosen by you or assembled by default from whatever platforms were convenient at the time.
idea2.life is the EvoBioSys holon that treats personal and organizational infrastructure as a design problem. It asks: what does it take to own your communications, your data, your DNS, your hosting — without becoming a full-time systems administrator? The answer is an Open Tech Stack philosophy: every component is open-source, self-hostable, and replaceable. No vendor lock-in. No silent data extraction. No dependency on a single provider's continued goodwill.
idea2.life is not a server rack. It is the human dimension of the tech — the conviction that sovereign infrastructure is ultimately about autonomy, dignity, and the right to a digital existence that reflects your values rather than an advertising model. Technology serves life, not the other way around.
The project carries a dedicated Tana workspace with its own supertag (i2L idea2Life), a published OnePager, and a growing body of documentation under the idea2Life unboxing supertag — a collection of discovery moments where sovereign infrastructure reveals new possibilities.
idea2.life is not a single product but a constellation of sovereign services that form a complete digital operating system. Each layer handles a distinct concern; together they compose a stack where no external party holds the keys.
Self-hosted Matrix server at the heart of idea2.life's communication layer. A valid Element.io server, fully compatible with the Element client ecosystem and accessible from any Matrix-compatible app.
The communication nerve center that manages the flow of signals — messages, notifications, updates — across the sovereign infrastructure. Bridges multiple messaging protocols into a unified, self-hosted layer.
Sovereign infrastructure starts at the foundation: who controls your DNS, and where do your services run? The best hosting sub-holon manages private DNS records and EU-sovereign hosting.
idea2.life is evolving toward an incubator model — not just sovereign infrastructure for one person, but a replicable blueprint others can adopt. The document "Phases for idea2.Life as an Incubator" outlines this trajectory.
Core stack operational. Matrix server, Signal bridge, private DNS, EU hosting. Proving the model works for a single user/organization.
The open tech stack becomes a publishable blueprint. OnePager, unboxing discoveries, and operational runbooks formalized.
Others deploy the idea2.life stack. Tooling, templates, and support structures enable sovereign infrastructure without deep sysadmin expertise.
Federated idea2.life instances form a network of sovereign nodes — each independent, all interoperable. The incubator becomes an ecosystem.
idea2.life does not exist in isolation. It is connected to collaborators, adjacent holons, and the broader EvoBioSys infrastructure that sustains it. Manuel Spornberger has been a key collaborator through a series of working meetings ("Manuel & Jakob for Idea2Life"), shaping the project's direction and technical decisions.
The holon connects to the EvoBioSys Publication Pipeline workspace for documenting and sharing infrastructure patterns, and to kidur for the open-source tooling philosophy that underpins every technical choice.