How it works

From a roster to a route, in three moves.

kreator.network starts with the one thing nobody else can supply: your own account of who you know and what you would route through them. Everything after is derived from that, and nothing is derived from anything else.

1 · Twelve people

Name them, two taps each

Who, how the relationship stands, when it last demonstrably functioned. On the home page, in your browser, with nothing sent anywhere.

2 · The renewal queue

What has gone quiet

In the same minute: who you named, how long since each relationship last functioned, and which edges have decayed to estimated. It needs no network at all.

3 · A route

A path someone can consent to

When an ask arrives, a route runs only through people you said you would route that thing through, and every hop is consented by the person it crosses. Not yet live: routing needs the mesh connection described on the Developers page.

What is live today, and what is not

The roster and the renewal queue work now, in this browser. Routing, the Wallet and the sealed record wait on estate components that already exist elsewhere and are not yet wired here. Each says so where it appears.

Stepstate
Roster, two taps eachlive · this browser only
Renewal queuelive · this browser only
Routing through the meshNot yet
Consent-gated settlementNot yet
Sealed outcomes on the logNot yet