Login and account linking
Email, Google, and GitHub access flow into one user account.
Sandbox Ecosystem
Isolated cloud AI sandboxes with AI CMS included
Nostate is the control plane for creating user sandboxes, tracking limits, attaching domains, and operating lightweight cloud environments through one account. Start free, open a sandbox in minutes, and keep the operational surface simple.
- One free sandbox and one free custom domain per user by default
- Queued provisioning instead of manual infrastructure steps
- Custom-domain flow with DNS verification and SSL activation
Control planeAccount, queue, sandbox, domainEach environment is managed through one operational surface instead of scattered setup scripts.
Queued builds
Sandbox creation is persisted first and executed asynchronously.
Verification before activation
Custom domains stay gated by entitlement, DNS proof, and certificate readiness.
Lifecycle controls
Open, inspect, stop, restart, and delete environments from the same panel.
Overview
A clean user path from account creation to a running environment.
The current product flow is deliberately narrow: sign in, view limits, create a sandbox, and manage it from the control plane without touching raw infrastructure.
Create one account
Register with email or sign in with Google or GitHub. Existing users are matched by email so provider access stays attached to one account.
Check limits in the dashboard
See how many sandboxes and custom domains your account can use before you attempt provisioning.
Create and open a sandbox
Submit the sandbox name, wait for the queued build, then open both the live runtime and the sandbox admin surface.
Provisioning
Provisioning is persisted first, then executed by workers.
Nostate does not hide that sandbox creation is an infrastructure operation. Instead it makes the workflow explicit and safe: records are written first, workers execute the provisioning steps, and the user sees the status through the platform.
- New sandboxes start in a building state until provisioning finishes
- Operations are designed to be idempotent instead of assuming a perfect first run
- The control plane remains responsive while background work continues
Control-plane preparation
- Sandbox record is created
- Entitlement limits are checked
- Provisioning operation is queued
Environment activation
- Worker executes provisioning steps
- Runtime URLs become available
- Status changes from building to active when ready
Custom Domains
Custom domains are supported, but only after entitlement and verification checks.
Domain attachment is not just a text field. Nostate gates the flow through custom-domain entitlement, DNS verification, and SSL issuance before the domain becomes active on a sandbox.
Entitlement-aware
Accounts without domain entitlement stay blocked from activating custom domains.
DNS verification
Ownership must be proven before the platform treats the domain as eligible.
SSL before activation
Certificates must be issued successfully before the custom domain is activated.
Operations
Lifecycle controls stay in one management surface.
The user panel is not only for creation. It also centralizes the day-two actions that matter once a sandbox already exists.
Reach the live runtime and admin quickly
The platform exposes the runtime URL and the admin surface once the sandbox is ready.
Start, stop, and inspect state
Lifecycle actions are intended to be visible and repeatable rather than hidden behind one-off scripts.
Remove sandboxes intentionally
Deletion is a real user action and the documentation makes clear that removed environments and data may not be recoverable.
Free Start
The current cloud offer starts with a strict free baseline.
Nostate currently defaults to one free sandbox and one custom domain unless billing or admin-issued entitlements extend that baseline.
The initial cloud service is free and best-effort. It does not create an obligation for uninterrupted availability, guaranteed retention, recovery, or compensation.
One sandbox by default
Free users can start with a single sandbox without needing a paid entitlement.
Domains are additive, not assumed
The default baseline already includes one custom domain, and higher tiers or admin bonuses can extend that capacity.
Admin overrides remain possible
Operational or support-driven entitlement bonuses can extend account limits without changing the core rule set.
Control Plane
This repository is the orchestrator, not the sandbox app itself.
Nostate separates the control plane from the workloads it provisions. Authentication, dashboard summaries, domains, provisioning logs, admin tools, and billing logic live in one modular monolith, while each sandbox runtime stays isolated from that management layer.
What that separation gives you
- A single place to manage user identity and limits
- Queued infrastructure operations instead of long-running controller requests
- Admin visibility into support actions without coupling to sandbox content logic
- Cleaner isolation between platform concerns and runtime concerns
Start carefully
Use the sandbox ecosystem for fast iteration, not for blind assumptions.
Nostate is designed to reduce setup friction and keep the platform understandable. It still expects users to make responsible decisions about data, uptime expectations, and whether a free best-effort cloud service fits their workload.