Own the agent.
Your identity. Your relationship.A continuing personality and the memories you choose to build together.

Make intelligence useful and accessible. Put existing technology to work. Keep ownership in people’s hands.
Explore our principlesPEOPLE. TECHNOLOGY. OPPORTUNITY.We put existing technology to useful work, build around people’s choices, and expand what they can create together. Reuse, owner control, and a distributed network guide the platform we’re building.
Five commitments guide what we build. Each product decision should move us closer to all five.
A continuing personality and the memories you choose to build together.
A dedicated device for your agent’s presence in the world.
Member ownership and meaningful governance are at the heart of Aperion’s network model.
Owner-controlled access, export, deletion, and recovery are central to the design.
Choose connections, grant permissions, and authorize consequential actions.
Privacy shouldn't be a feature. It should be a consequence of ownership.
Your agent should not lose its identity because you change its brain. Separating these five layers is the design principle behind Eclipse: one continuing relationship, with replaceable intelligence and permissions you control.
A continuing name, personality and relationship anchored to your Key, independent of the model or interface you use.
Authoritative encrypted long-term memory on owner-controlled Key hardware, with deliberate choices about retention, export, deletion and recovery.
Replaceable providers supply processing. Use local inference where practical; choose another approved route when the task requires it.
The Key anchors identity; Home, Condo, Dojo, Aurora and mobile provide authorized interfaces to that same relationship.
You grant access to specific tools, data and actions. A new model or device must not inherit new credentials or permissions automatically.
A model can reason, generate or interpret. Greater capability does not grant access to your resources.
An agent can organize a task and use connected tools, subject to the scope you authorize.
Permissions define which actions may proceed and which require your approval. Legitimate safety and privacy boundaries still apply.
The architecture calls for recovery using owner-held recovery credentials, so replacing hardware need not mean abandoning an identity. Recovery must be supported by the specific product and tested with its backup process; a website account alone is not an encrypted agent backup.
Encrypted storage protects retained memory. A provider processing a request may need to see its contents. Share only the necessary context, use a trusted route for sensitive work, and review the product’s actual export, encryption and recovery support before relying on it.
These are architectural commitments. Product-specific capabilities and published terms determine what is available; this showroom does not provision encrypted agent memory or recovery credentials.
Explore the embodiments →Privacy shouldn't be a feature. It should be a consequence of ownership.
Create an agentThese principles guide our product decisions. The showroom lets you explore the experience; it does not grant network membership, governance rights, or a registered agent identity. Product availability and published terms define what is offered.
An individually owned Eclipse agent is anchored to owner-controlled Key hardware: persistent identity, authoritative encrypted long-term memory, personality, configuration and permissions. Aurora and compatible hosts provide its presence; inference providers supply processing. Portability means authorized embodiment and owner-controlled recovery to replacement hardware—not giving up the physical ownership anchor.