Mainsail Industries · Starlight
Starlight, in your browser.
try.starlight.build opens a session to your Starlight servers wherever they run: on-prem, in a cloud account you own, or at the far edge. Stargate bridges the hop over a p2p zero-trust mesh, so one dashboard covers every site.
Works with the Google, GitHub, or Microsoft identity you already have. Starlight stays on your hardware.
Your browser
try.starlight.build
Stargate
web access gateway
On-prem
host · datacenter
Cloud
AWS · GCP · Azure
Far edge
single node · 2-node HA
solid = TLS to the site · dashed = p2p zero-trust mesh, brokered by Stargate
What Starlight is
One platform. Every workload.
Starlight is software you install on your own hardware to run virtual machines, containers, and AI workloads at the edge, with security and autonomy built into the system itself.
Unified
VMs, containers, and AI under one control plane. Same identity, same policy, same lifecycle for every workload type.
Edge-first
Every node runs on its own. Sites keep working when the link drops and reconverge state when it returns.
Autonomous
Security and resilience are part of the system: verified boot, signed builds, runtime policy, and two-node HA.
Stargate
Reach every server through Stargate.
Stargate is the web access gateway. Your browser talks to it over TLS; it bridges to each Starlight server over a p2p zero-trust mesh. Nothing runs in Stargate but the session.
On-prem site
- Local Starlight node (host)
- Enterprise datacenter racks
- Private AI node on NVIDIA Spark or DGX
- Starlight Desktop, side by side
Cloud regions you own
- Starlight nodes in AWS
- Starlight nodes in GCP
- Starlight nodes in Azure
- Your account, your bill, your keys
Far edge
- Single-node sites
- Two-node HA without a third box
- DDIL and satellite links
- Relay path when direct fails
Capabilities
What you can run, and how it stays up.
Virtual machines
Windows and Linux VMs run as-is. Live migration, HA, snapshots, and networking are native.
Containers
OCI images run unchanged. Helm charts and Kubernetes workloads replatform incrementally.
AI inference
Models ship as containers. GPU drivers and runtimes come version-matched on first boot.
Peer mesh orchestration
No etcd, no scheduler to babysit. Nodes share state by protocol and stay consistent.
Zero-trust policy
Identity-driven filesystem, network, and syscall controls enforced at runtime, not observed.
Live migration
Move running workloads between nodes with no forklift and no maintenance window.
Two-node HA
High availability at edge scale. Two boxes, not three, and the same operating model at any size.
Disconnected operation
Sites keep serving when the WAN drops. State reconverges on its own when the link returns.
API and MCP
One API for desktop, CLI, and automation. A built-in MCP server lets agents operate the platform.
How this site works
Four hops from sign-in to your servers.
Everything between your browser and your hardware is a session. The hardware, the capacity, and the data stay yours.
- 01
Sign in
Use the Google, GitHub, or Microsoft account you already have. No new password.
- 02
The site opens a session to Stargate
A short-lived, per-user session. Stargate never holds your workloads, only the connection.
- 03
Stargate bridges to your servers
Over the p2p zero-trust mesh, to on-prem hosts, cloud nodes in your account, and edge sites.
- 04
You get one dashboard
Workspaces, servers, and dashboards across every site, in the browser, next to Starlight Desktop.
Bring your servers. We bring the session.
Sign in to open a workspace, register your first Stargate endpoint, and see every site on one dashboard.