Step 1 / Start
The homepage opens with a guided route-request flow. Not ready yet? Skip and review the platform first.
Step 2 / Node Install
Start with the desktop client. Generate keys, attach to a node route, and verify lifecycle events before treating TNTS like ordinary email.
Use the desktop bootstrap first, then move into developer setup when you want custom nodes or envelope tooling.
Account creation is really route identity provisioning. You are asking for a transport slot, not just a profile page.
Step 3 / Frontend Architecture
The client centers transport state, node attachment, event visibility, and envelope proof. It exposes routing truth instead of hiding it behind feed logic.
Composer, route status, receipts, and stream events are primary UI layers because message movement is observable infrastructure.
Users can see exactly what happened to an envelope, which node touched it, and which lifecycle state it reached.
Step 4 / Platform Difference
Most platforms insert ranking, trust scores, moderation heuristics, or AI interpretation into delivery. TNTS stays deterministic: valid identity, valid route, valid proof.
Signed envelopes and auditable states replace invisible moderation queues, shadow filters, and content-based deliverability decisions.
The platform is opinionated about transport integrity, not about judging message tone or shaping attention.
Step 5 / Expectations
jetes.cloud is not an algorithmic judge. The no-ban model means the normal route path does not silently suppress, rank down, or tone-score valid messages.
No shadow bans, no sentiment gates, no AI verdict layer deciding whether a valid envelope should move.
Bring a real use case, expect early-access rough edges, and treat node access as infrastructure participation rather than a casual social signup.
Step 6 / Signup
Reserve a route identity and receive a confirmation code immediately. This keeps signup aligned with the onboarding you just read.
Signup / Complete
Your route request is now in the system. Use the confirmation code below for follow-up while you explore the rest of the homepage.
TNTS / True Nanomessage Transport System
Deterministic routing with signed envelopes and auditable lifecycle events. No sentiment scoring. No hidden moderation layer. No AI judge in your transport path.
Lifecycle
SENT -> ROUTED -> DELIVERED -> OPENED
Guarantee
Delivery is route-driven, not content-scored.
Proof
ed25519 envelope and receipt signatures
Messages move when identity, route, and proof are valid. TNTS does not inspect tone or rank users by behavior scores.
Senders and recipients can query exact state transitions and timing events without platform snooping into payload body.
`POST /tnts/envelopes/send`, `GET /tnts/envelopes/{id}`, and websocket event streams map cleanly to transport lifecycle.
Live Flow Preview
The homepage follows the latest message as it moves through the TNTS lifecycle. New messages and updates stream in over SSE.
Waiting for the latest envelope event.
What Developers Get
Onboarding
The guided gate explains node install expectations, frontend architecture, and the no-ban operating model before signup submission.
