Me · Skyzai for individuals
Stay close. Keep your choices.
A personal space for your conversations, connections and ideas. Choose who sees what, shape what reaches you, and keep the thoughts that help you move forward.
Your presence. Your keys. Your memory. Your exit.
Try the experienceExplore the design. Account features are in development.
Make a plan with a friend.
Share a moment with your people.
Find something worth your attention.
The point is not more time in an app.
It is more choice in the life around it.
Here the machine proposes — and you sign.
Interactive design preview · in development
A little closer to your everyday.
Try the intended interactions. This is a local illustration, not a working account or service.
Private messages
One to one · example conversation
You & Alex
A little time, just for you two.
Shall we meet
by the garden?
Be present.
Leave less behind.
The intended experience is encrypted one-to-one messaging with read notifications and a temporary conversation that fades when the other person leaves.
Media opens in an immersive view.
A reaction is an invitation, never a hidden recording.
A camera reaction would require the viewer’s separate consent—not hidden capture or an inferred emotion.
No encryption, sending, camera or deletion service runs here. A visibility timer cannot guarantee that recipients have not made copies.
How connection feels
Four shapes the network can take.
As screens, not abstractions.
Every connection is one of four functions: one to one, one to many, many to one, many to many. These are intended product screens — fictional people, predefined words, nothing sent or stored. Play them. The audience is a grant. Small talk can go. A useful note stays only if you keep it.
Private. You and one person. The thread is ephemeral unless you keep a note.
Broadcast. You speak to people you grant. The milestone stays on your outline.
Your inbox. Many people reach your one space. Conversations fade; a kept note does not.
Shared context. Several people coordinate in one place. A curator may rank the room; your typed API is the gate.
Ephemeral → Ambient → Kept. Permanence is an explicit act. The four shapes live on the substrate: FLOW, RELAY, AXIOM, MESH. These screens send nothing.
What the four names mean
Each shape has a name in the protocol, and each name says what the shape keeps.
- FLOW · one to one
- Two people, one channel. Neither side needs the other's permission — or the platform's — to reach the other, and neither holds the other's keys.
- RELAY · one to many
- One person publishes; everyone they granted receives it, and can check that it was sent. Being heard by many makes it neither true nor theirs to reuse.
- AXIOM · many to one
- Many people reach one place. What arrives keeps who it came from, so a single answer never erases who said what, or who disagreed.
- MESH · many to many
- The shared space where everyone can reach everyone. It carries the conversation and finds another path when one route fails. It is not a vote and decides nothing by itself.
These are routing designs [S/D], not live services: intended shapes with screening previews, no network, no settlement and no market behind them today.
A presence of your own
Be yourself.
Beyond one app.
Your identity should be something you carry—not something you start again whenever you change tools.
Explore the exampleClose the example
A presence of your own
Be yourself. Beyond one app.
Your identity should be something you carry—not something you start again whenever you change tools.
Explore the exampleClose the exampleA design you can explore
Skyzai uses Nostr-based identity as its starting point. The design connects your presence across compatible experiences, while keeping signing, storage and recovery choices explicit.
Illustration of the idea, not an app screenshot. The example uses fictional details.
How identity is designedIdentity design · fictional example
You
One identity. Different contexts.
Plans, people, things to learn.
A place to decide what belongs in your life.
What “your keys” should mean
A public key identifies an account; a private key can sign for it. Compatible tools may recognise that identity. A key alone does not move every file, permission or relationship.
Key storage, backup and recovery need explicit choices. Losing a key can mean losing access; exposing it can let someone act as you. This preview generates no keys and does not demonstrate recovery.
Closeness, with boundaries
Your people.
Not your whole profile.
An invitation needs a meeting place. A friend may need your number. Neither needs access to everything.
Explore the exampleClose the example
Closeness, with boundaries
Your people. Not your whole profile.
An invitation needs a meeting place. A friend may need your number. Neither needs access to everything.
Explore the exampleClose the exampleA design you can explore
Nexus is the permission layer. The intended controls let you share individual details with specific people, connections or uplinks—or keep them to yourself.
Illustration of the idea, not an app screenshot. The example uses fictional details.
How permissions are designedTry the permission design · fictional details
A detail, not your whole life.
For this example, Alex, Connections and Uplinks are separate audiences. A relationship group is not automatic permission to see your profile.
In the app design, permissions would also depend on actual membership and purpose. Changing a grant limits future access; it cannot recall copies already received.
Thoughts with a direction
Keep the useful.
Let the chatter pass.
Less time filing conversations. More room for the plans, questions and ideas you want to return to.
Explore the exampleClose the example
Thoughts with a direction
Keep the useful. Let the chatter pass.
Less time filing conversations. More room for the plans, questions and ideas you want to return to.
Explore the exampleClose the exampleA design you can explore
APU starts with the open note or objective. Its intended memory keeps useful context, not an endless conversation archive. Cortex keeps sources and revisions distinguishable, including things that are still uncertain.
Illustration of the idea, not an app screenshot. The example uses fictional details.
Explore APUAPU memory design · predefined example
Walk with Alex this weekend
No example note kept yet.
“Let’s meet at the garden’s north gate on Sunday. We still need to choose a time.”
When meaning is unclear, APU should ask. An unresolved question stays unresolved; tidying must not turn a possibility into a fact. These examples stay only in this page’s memory and reset on reload—no AI or note storage is connected.
What you can explore today
A clear direction.
An honest starting point.
This website
Explore the design, try fictional interactions, and install this public website for convenient reading. Signing up, sending messages and saving personal notes are not connected here.
The app being built
Portable identity, meaningful sharing and purpose-linked memory are the direction. Encryption, expiration, recovery and permission enforcement need completion and verification—not just a convincing preview.
Also on the roadmap: money & identity checks
The roadmap includes separate checking, trading and saving wallet experiences, WalletConnect support, multisignature savings and privacy-preserving identity checks. These are designs under development—not live wallets, banking services or available identity verification.
Your life. On your own terms.
Stay connected without making everything public.
Keep what matters without keeping every conversation.
And when you leave — leave with everything.