Where data sovereignty is structural.
IdSolid® is the sovereign-by-architecture identity, memory, and data platform for the moment personal information stops being an asset to defend and starts being a liability to redesign around. Built for organisations and individuals who would rather not see their own name in the next breach headline. Each subject's data lives inside an individually encrypted Sovereign Pod. Verified identity attributes are exposed through an open API. An AI memory layer travels with the subject across whatever models, tools, and providers they use. Runtime-agnostic. Vendor-neutral. Personal storage, enterprise data architecture, AI memory continuity, and source-of-truth identity for other organisations - one sovereign primitive underneath all of it.
For organisations holding sensitive personal data, and for individuals who would rather hold their own.
Traditional corporate data architectures aggregate. They were built when storage was expensive and centralisation was the obvious efficiency. Personal records get pulled into a single database, the database gets surrounded by progressively heavier perimeters, and the result is a honeypot that grows more valuable to attackers with every customer added. The breach surface is the entire customer base, every time.
IdSolid distributes. Each subject's data lives inside its own cryptographically isolated Sovereign Pod. The pods cannot be queried in aggregate. A breach of one pod is not a breach of any other. The pod owner - the subject - is the only entity who can grant access, and access is per-pod, per-scope, per-transaction. The architecture inverts the central assumption underneath every major data breach in the past twenty years: that holding everyone's data in one place is more efficient than holding each person's data with the person.
A traditional data store answers: who is in our database, and what do we know about them? IdSolid answers: who has chosen to make themselves verifiable, what have they chosen to share, and with whom?
Both architectures hold personal data. Only one of them does so in a shape that survives determined attackers.
The current internet stores personal data in two ways, and neither serves the subject.
Corporate aggregation - your data sits inside someone else's commercial system because they need it to provide you a service. Their business model depends on holding it, their security depends on defending it, their continued existence depends on you not asking for it back. When they fail at any of these, the failure is yours to bear, not theirs.
AI vendor lock-in - your AI memory sits inside the model provider's proprietary silo. The context you build up with one model cannot move to the next. Each new tool starts from zero. Your accumulated intelligence is the thing the platform is selling back to you, and the switching cost scales with the depth of memory you have built.
Both gaps share an architectural cause: data is held by the system that processes it, not by the subject it describes. The sovereignty conversation that has been running for two decades has not closed either gap because it has been a policy conversation, not an architectural one. Promises about data ownership do not bind storage architecture. Architecture binds storage architecture.
IdSolid closes both gaps by removing the architectural assumption underneath them. The subject's data lives with the subject. Tools and providers operate on the data through scoped, revocable access. When the subject changes provider, the data does not move - the access permissions do.
At the core of IdSolid is a single primitive: the Sovereign Pod. In plain terms, it is an individually encrypted, cryptographically isolated data store assigned to one subject - one person, one household, one organisation - that holds everything that subject has chosen to make portable and verifiable.
Each pod contains four governed layers.
The identity layer - bank-verified attributes, government-issued credentials including those issued under frameworks such as eIDAS and the EU Business Wallet, professional certifications, and other high-assurance identity primitives that the subject has chosen to bring into IdSolid. Provenance is preserved end-to-end so any organisation querying the pod can verify which attributes are bank-verified, which are self-attested, and which are signed by recognised credentialing authorities.
The data layer - personal records, organisational records, transactional history, and any other structured data the subject controls. The schema is the subject's, not IdSolid's. Other organisations can request access to specific fields under specific scopes; the pod owner decides per-request.
The Open Brain memory layer - AI memory, context, and accumulated intelligence stored in a format any compliant AI model can read. When the subject changes AI provider, the new model gets read access to the same context the previous one had. Memory travels with the subject, not with the AI.
The provenance layer - a cryptographically signed record of every access granted, every attribute used, every memory recall, every change made. The pod owner can audit their own pod completely. Other organisations consuming pod data can verify the chain of evidence behind anything they receive.
"The Sovereign Pod is not a policy decision. It is not a terms-of-service promise. It is an architectural primitive that makes sovereignty a property of storage, not a clause in a contract."
Three goods, structural and portable.
Every subject owns their own pod outright. Magentix cannot read pod contents. Hosting providers cannot read pod contents. Other organisations consume only what the subject explicitly grants, only for the duration the subject grants it. When a regulator asks where your customers' personal data lives, you can point at every individual pod in your customer base, and the honest answer is "with the subject, not in our database."
Identity, data, and AI memory all travel with the subject across providers, tools, and models. Switching AI vendors does not reset your accumulated context. Moving between healthcare providers does not erase your history. Changing employers does not strand your professional credential record. The architecture makes lock-in structurally impossible, which means competition between providers happens on the quality of the service rather than the size of the switching cost.
Every identity attribute, every data record, every credential carries its origin and its signature. Other organisations can subscribe to a pod as a source of truth - a bank can verify a customer's identity from their pod rather than running its own duplicate KYC, an employer can verify a credential from the pod rather than calling the issuing institution. The honest answer to "is this person who they say they are" becomes a single signed read from the pod, not a six-week verification cycle.
"When a customer's data leaves your environment, you should be able to look the regulator in the eye and explain not just where it went, but why every byte of access was authorised, by whom, and for how long. IdSolid is built to make that explanation a single audit query, not a six-month investigation."
IdSolid is SaaS-first and runtime-agnostic. Pod isolation is absolute because sovereignty depends on the architectural guarantee that no pod can read another. Cryptographic isolation is enforced at the storage layer, not the application layer - the database itself cannot return aggregate queries across pods. No raw secrets are persisted at provider level. Bank-verified attribute integration uses signed, revocable credentials from accredited identity providers. The open API framework allows any organisation to integrate IdSolid as an identity, memory, or data layer alongside or behind their existing systems. The Open Brain memory layer uses PostgreSQL with pgvector and is MCP-ready, so memory written by any compliant model can be read by any other. GDPR-compliant by design. The architecture is extensible across personal, organisational, healthcare, financial, and regulated-industry use cases without changing the underlying pod primitive.
This is the discipline that makes the architecture defensible at scale, not just sovereign on the page.
The personal data sovereignty market is splitting into layers, not converging into one crowded category. IdSolid's lane is the sovereign-by-architecture identity, memory, and data platform that operates as a source of truth for both subjects and the organisations that need to verify them.
The market is not becoming one personal data platform. It is becoming a network of sovereign storage surfaces. IdSolid helps subjects keep their identity, memory, and data sovereign across that network, and helps organisations consume verified attributes from those subjects without holding the data themselves.
IdSolid and ARBITR are independent products. Each functions on its own and can be subscribed to separately. Between them they cover identity, memory, and the evidence of execution - the part of the trust question most current governance frameworks leave unanswered.
IdSolid governs identity and memory: who is acting, what context informs the action, what credentials they carry, what they have chosen to expose.
ARBITR governs the neutral evidence of execution: under what authority an action occurred, against which target system, with what result, at the moment of commit. The two together close the gap between "is this subject who they claim to be" and "was this action authorised in the way the subject intended."
Consider the case an autonomous AI agent is increasingly asked to handle: presenting a credential under a framework such as eIDAS or the EU Business Wallet on an organisation's behalf, then committing an action against a target system. IdSolid is what makes the credential presentable and verifiable. ARBITR is what makes the resulting action accountable. Either layer in isolation answers half the question. Together they answer all of it.
Organisations adopting one without the other still get a complete product. Organisations adopting both get an architectural answer to the question every regulator will eventually ask: when something acted on your behalf, was it authorised, by whom, with what evidence, and is the record of it portable across the providers you might use tomorrow?
The IdSolid Early-Design-Partner Programme is open. Twenty places are being selected on lifetime-access partnership terms. The Sovereign Pod primitive is stable, the V1 product scope is defined, and the architecture is being pressure-tested through the design-partner cohort before general availability opens. The design-partner programme is the only commercial path today.
IdSolid is best suited, today, to organisations holding sensitive personal data they would rather not be holding, or individuals who want sovereign control over their own digital identity and AI memory, and identity-issuing institutions looking for a sovereign storage surface their citizens or customers can carry across providers.
Twenty places will help shape IdSolid while structural feedback can still influence the product. Each early-design partner pays a single fixed entry fee and receives lifetime access thereafter. This is not a discount scheme. It is a partnership.
The twenty places are designed to accommodate both organisational adopters (banks, healthcare providers, regulated industry, governments, identity-issuing institutions) and individual high-assurance subjects (founders, executives, privacy-sensitive professionals) who want to test the architecture from both sides of the table. Final composition of the cohort will be balanced to give the programme breadth across personal, organisational, and institutional use cases.
Submit an Expression of Interest and, if the fit is strong, you will be invited to a qualification call. Shortlisted partners receive the Prospectus and, under mutual non-disclosure, the Architecture Brief and the Sovereign Pod schema.
Not ready for either? For advisory, integration, or partnership enquiries that sit outside the early-design-partner route, email contact@magentix.ai.
