Open the console
Use the standalone console and sign in through the shared 0S/FS27 gate.
Open consolePost to SkyeNet
Publish a real app or landing page on the standalone SkyeNet edge.
SkyeNet gives a workspace, live route, deployment receipt, account-scoped source download, and explicit transfer lane for client-facing static sites, PWAs, and built frontend apps. The shared 0S/FS27 gate owns account access, so there is no second SkyeNet password to manage.
Normal posting flow
From folder to live route.
Choose a workspace
Create or resume a workspace, pick the plan, and keep the project slug simple.
Drop the build
Upload a built folder. SkyeNet promotes common roots like dist, build, out, and public.
Publish the route
SkyeNet checks for a root index.html, writes the deployment receipt, and returns the live URL.
What is ready now
Clean static publishing with account proof.
Landing pages and marketing sites
Built frontend apps and PWA shells
Public or shared-gate-protected routes
Deployment receipts and route records
Workspace dashboard and quota posture
Gated source download and stored transfers
Current boundary: Free99 is capped, custom domains are paid/approved, and unlimited arbitrary uploaded serverless functions are not sold until the isolated SkyeNet Sovereign Runtime lane has production proof. Full project downloads use the private source package lane, not public asset routes.
Source custody
Download is not the same thing as client ownership.
SkyeNet keeps deployed source recovery scoped to the authenticated account that owns the deployment record. Public assets and private full project source packages are separate lanes, so a client can have a live app hosted for them without receiving the source code.
When source handoff is approved, the owner can store the transfer in SkyeDrive, store it in SkyeVault, create an instant gated link, or generate a secure encrypted .skye source pack backed by the SkyeSecure v2 lane.
Environment variables
Project secrets belong in the account console.
The SkyeNet console includes project environment variables for production workspaces. Values are stored behind the shared gate and shown back only as redacted previews, so operators can verify a key exists without exposing the raw secret in the browser.
Use this lane for API keys, runtime toggles, and client-specific configuration that should travel with the SkyeNet deployment record without being copied into public assets.
Plan caps and pricing posture
Start free, upgrade when the surface needs more room.
$0
Capped demo or tiny public workspace.
- 25 MB bundle cap
- 3 deployments per month
- 1 public route
- No custom domains
- No serverless functions
- 30-day retention
$297 setup + $97/mo
Basic hosted app or public landing surface.
- 25 MB bundle cap
- 20 deployments per month
- 1 public route
- No custom domains
- No serverless functions
- 60-day retention
$997 setup + $297/mo
Multi-route workspace with one approved custom domain.
- 150 MB bundle cap
- 100 deployments per month
- 5 public routes
- 1 custom domain
- Managed functions review
- 120-day retention
$1,500 setup + $497/mo
Owner-approved managed function work and larger static releases.
- 250 MB bundle cap
- 150 deployments per month
- 8 public routes
- 2 custom domains
- Approved managed functions
- 180-day retention
$5,000 setup + $997/mo
Reserved lane for deeper runtime, domain, and managed infrastructure scope.
- 500 MB bundle cap
- 300 deployments per month
- 20 public routes
- 5 custom domains
- Isolated runtime reserved
- 365-day retention
These are current SkyeNet offer caps and owner-review prices. Final paid activation, custom domains, managed functions, and higher limits require owner approval before they are promised to a customer.
CLI lane
Operators can publish directly from a build folder.
npm run skyenet:deploy -- \ --dir dist \ --source-root . \ --project my-site \ --workspace default-workspace \ --host skyenet.my-site \ --mount / \ --url-mode subdomain \ --public \ --concurrency 4
Live examples