SkyeNet Deploy
SkyeNet
A standalone sovereign deploy network for public apps, client landing experiences, PWA shells, route receipts, and owner-controlled source custody. The 0S can publish here, while FS27/SkyGate still owns the shared operator gate.
Public host patternskyenet.<company-slug>
Control originskyenet.graylondonskyes.workers.dev
RuntimeFS27 SkyeNet route registry
StorageSkyeNet R2 deployment vault
AuthShared 0S / FS27 gate
CustodyAccount-scoped download + .skye transfer
Source custody
Hosted for the client. Owned by the account that deployed it.
SkyeNet separates the public app from the source handoff. A client can receive a live hosted surface without receiving the source code. The authenticated account that deployed the bundle can download it, store it in SkyeDrive or SkyeVault, create an instant gated handoff, or generate an encrypted secure .skye source pack.
Cross-account client source handoff is a deliberate transfer event, not an accidental console leak.
Live examples
Published surfaces
Publishing guide
Post to SkyeNet
Normal browser and CLI flow, plan caps, pricing posture, and what is ready to sell today.
Client app
Bob's Smoke Shop
Retail landing app, workspace handoff, PWA shell, and cinematic hero media.
Host-native route model
skyenet.<company-slug>
Customer-facing company surfaces publish on platform-native hostnames after route proof.
Operator lane
Standalone console
Shared-gate control for status, route receipts, account workspace state, and source downloads.
How it connects
Separate project, shared command layer.
0S publishes
FS27 verifies
SkyeNet routes
CitadelDB records