01 · Brass
Your Hardware
The machines its people already run. A triadic network does not begin with a datacentre you rent; it begins with the computer on your desk and the node in the room.
Create your Secure Private Cloud
Your Hardware
Your Network
Your Software
Your Control
Triverse is the seat where those four meet: people, the machines they run, and what they publish to each other — joined by identity, not by a platform.
Request admission
Reviewed at triadic.cloud. A request is not access.
A drawing of the Triverse window. Outside: Triadic World, the four lines, Create and Join. Inside: the Network window for triadic.cloud, with spaces Chat and Factory and their publications.
Triadic World
Your Hardware
Your Network
Your Software
Your Control
Create a network, or join one from the directory.
A drawing of the Seat. Outside is a small window; inside is the network: its name, its spaces, and what its people publish. The ribbon is the sum of the machines that report.
Four Foundations
What a triadic network is
02 · Purple
Your Network
A name, a purpose, and the people who share them. Joining is a decision made by people, not a row in someone else's database.
03 · Blue
Your Software
The services the network runs and the publications it places. Chat, a factory, a gateway: each has a name, an owner, and a place.
04 · Green
Your Control
Identity decides who enters. A passport is issued by the authority the network trusts — at triadic.cloud — not by the website that invited you.
Separation of Authority
How admission works
-
01
Stamp your passport.
This browser creates a key and triadic.cloud stamps the passport that holds it. The admission request is signed with that key. This website issues nothing.
-
02
triadic.cloud reviews.
The authority reads the request. It may admit you, hold it, or decline. A request is not access.
-
03
Your passport opens the shield.
If you are admitted, a steward at triadic.cloud issues the trust stamp on your passport. With it, the shielded resources open, starting with triadic.world.
This site never sees your private key.
First Shielded Destination
Behind the shield
triadic.world
Public pages stay public. Stamped surfaces open with a passport stamped and admitted at triadic.cloud.
The list of shielded resources is held at triadic.cloud, not here.
Admission List
Request admission
This is a request to the authority at triadic.cloud. Your passport is the request: it is created and stamped in this browser, and triadic.cloud reviews the stamp. No account, no password, and no private key leaves this device.
Reading this browser's passport…
← Back to Triverse
Admission Status
Your passport
triverse.app does not decide. triadic.cloud does. This page reads the passport in this browser and the stamps the authority holds for it.
Passport
none
No passport in this browser
—
No passport yet.
Create a passport on the launch page, or load a backup from another browser. The passport is the reference; there is no code to keep.
The private key never leaves this browser. Status is read from triadic.cloud and cached locally for the last check.
What the states mean
- no passport
- This browser holds no key. Create one or load a backup.
- passport
- The key exists here. It has not been stamped by triadic.cloud yet.
- stamped
- triadic.cloud has confirmed key control. No admission request has been sent.
- requested
- The signed request is on the admission list. A request is not access.
- approved
- The desk approved the request. The trust stamp is still pending.
- admitted
- A steward at triadic.cloud has issued the trust stamp. The shield opens.
- declined
- The authority dismissed the request. No access was granted.
- revoked
- The authority revoked the trust stamp. The shield is closed.
- expired
- The trust stamp passed its expiry. Request admission again.
← Back to Triverse
Privacy
What is kept
Plain facts about the passport and the admission request at triverse.app.
What stays in this browser
The passport is an Ed25519 private key, its public identity, and the stamps issued for it. They are stored in this browser's IndexedDB under triverse-passport. triverse.app keeps no server-side account, no request database, and no status tokens.
What leaves this browser
To request admission, the browser sends the public key, a signed proof that it controls the private key, the display name you chose, and the optional note to triadic.cloud. The private key is never sent, logged, or placed in a URL.
What triadic.cloud keeps
triadic.cloud records the admission request against your passport ID: the display name, the optional note, the time, and the decision. It also keeps the stamps it issues. Its retention and deletion policy applies to that record; ask the operator desk there with your passport ID.
How to remove the local passport
Use Forget this passport on the launch page. That deletes the key and stamps from this browser. Download a backup first if you want to keep the passport. Deleting the local copy does not delete the request record at triadic.cloud.
What is not used
No advertising cookies, no ad pixels, no third-party analytics, no behavioural trackers, and no third-party fonts. The page loads only its own assets. The only network calls are the passport and admission calls to triadic.cloud through this site's proxy.