It's NOT a blockchain.
Promise.
Elevait Origin is a data ownership platform in development. We're exploring how encrypted records, verifiable history, and explicit sharing choices can help people retain more control over their information. This page describes design goals, not released or independently validated capabilities.
An illustration of the proposed record model: linked records, signatures, and ownership information. Security depends on implementation, key management, and independent validation.
Designed around data ownership.
Six capabilities we're designing toward, with one aim: give people clearer choices about their data. Availability and implementation details remain subject to development and review.
Encrypted Records
The design explores encryption for stored records. Key custody, recovery, and sharing flows must be implemented and reviewed before we can describe their security properties.
Hash-Chained & Signed
Signed, linked records are intended to make changes detectable. Verification depends on trusted keys and access to the relevant history; it does not establish that a record's contents are true.
Selective Disclosure
We're exploring proofs that let a recipient check a disclosed field against a signed record without receiving the entire document. The privacy properties still need testing.
Portable Records
Exportable records and offline verification are design goals. Useful exports will also require documented formats, compatible tools, and a way to preserve the necessary verification material.
Explicit AI Preferences
The proposed record model includes signed permissions and AI-use preferences. Recording a preference does not by itself prevent an external recipient from misusing a copy.
Revocable Access
The goal is to control future access through the platform. Revocation and key rotation cannot erase plaintext, keys, or copies that a recipient already received.
A clearer foundation for ownership.
The proposed architecture separates record verification, personal data storage, and application behavior. These are development concepts; a public SDK, production readiness, and independent security review have not been established.
Origin Core
The proposed cryptographic layer for signed records, linked history, and proofs. Its implementation and security properties need testing and independent review before release.
SAFE
Secure Asset & File Environment. The proposed space for managing records and sharing permissions. Storage, key recovery, and account access remain design decisions to validate.
Your App
Applications would build on these record and permission tools. Each application would still need its own access controls, privacy practices, and review for its intended use.
// 1. Create an identity
const origin = new OriginClient();
const identity = await origin.keygen();
// 2. Mint a record as an Original
const doc = {
name: "Grant Application",
budget: 150000,
narrative: "...",
visibility: {
budget: "public",
narrative: "shared"
}
};
const original = await origin.safe.mint(doc);
// 3. Share a Merkle proof instead of the document
const proof = await original.disclose("budget");
// Design goal: verify the disclosed field against the signed record.
Clear about what is still ahead.
Origin is in development. This website is an informational preview and does not provide account creation, record storage, or a working Origin service.
Security needs evidence
Cryptography is only one part of security. Key management, recovery, permissions, and deployment controls need implementation testing and independent review before production use.
Copies have limits
Access controls can restrict future platform access. They cannot remove information already downloaded or guarantee that an external recipient follows recorded permissions.
Policies are under review
Product policies and operating details are being reviewed. See the current policy status before relying on any description of future data handling.
More control. Fewer dependencies.
Reduce Vendor Dependence
We want documented exports and verification tools to help people keep useful records when they change providers.
Data as Asset, Not Liability
Selective disclosure aims to reduce how much information a person needs to share. Privacy and compliance still require careful choices in every application.
Verifiable History
We are exploring ways to preserve verification material over time. Long-term use will depend on maintained formats, keys, tools, and cryptographic migration.
Built for Mission
We want useful data ownership tools to be accessible to mission-driven organizations. Availability and pricing will be published when they are ready.
Practical Integration
The design aims to fit familiar application environments. Supported runtimes, dependencies, and integration documentation will be confirmed with the implementation.
The Foundational Commitment
People should understand and choose how their data is used. We aim to make those choices explicit in both the record model and the operating policies.
Building toward
more paths into AI careers.
Our mission is to connect useful software with opportunity. As Origin develops, we intend for its revenue to support Elevait.org and AI education for young people.
The aim is practical training, mentorship, and a path from curiosity toward employment. We will publish program and funding details as they are established.
We're not building this to get rich. We're building it to fund boots on the ground — in St. Louis and wherever else this travels — teaching kids that AI is a tool they can wield, not a force that replaces them.
of gross revenue is our planned commitment to Elevait.org.
Respect a person's choices about their data. Our guiding principle.
kids we intend to reach if this works the way we think it will.
Explore what we're building toward.
See the broader goElevait product concepts in the visual preview. These screens illustrate a direction; they are not a live application or an Origin SDK.