Get started · Alpha

Get Nebula early access

Join the waitlist for the public source release and managed-install pilot.

Nebula-COS is Apache-2.0, but the public source release is still gated on clean install evidence. The target installer brings up the backend, waits for it to be healthy, and walks you through a setup wizard — honest about which OSes are supported and exactly what's live on first run.

Pick a path → What happens on first run →

Targeted in v1: Linux, and Windows via WSL2 / Docker Desktop. macOS is not a v1 target.

Install

Install in one script

Nebula-COS is Apache-2.0. Clone it, run the installer, and you're on a backend you own.

Honest OS support. Supported in v1: Linux, and Windows via WSL2 / Docker Desktop. macOS is not a v1 target.

The installer bootstraps the stack, then waits until the backend reports healthy before handing back. Day-to-day, the same lifecycle commands start it, check its health, tail logs, upgrade, stop, and cleanly uninstall.

evidence: scripts/install.sh, scripts/install.ps1 

# Linux — bootstrap + wait until healthy
$ ./scripts/install.sh

# Windows (PowerShell, in WSL2 / Docker Desktop)
> ./scripts/install.ps1

# Day-to-day lifecycle
$ ./scripts/install.sh doctor     # health-check the install
$ ./scripts/install.sh logs       # tail the logs
$ ./scripts/install.sh upgrade    # pull + migrate to the latest
$ ./scripts/install.sh stop       # bring the stack down
$ ./scripts/install.sh uninstall  # clean removal
First run

What happens on first run

No surprises. Here's the exact sequence after the installer hands you a healthy backend — and what's live versus off until you opt in.

  1. The setup wizard creates your local admin user and bearer session.

  2. You configure your chat provider — DeepSeek v4 is pre-filled, but any OpenAI-compatible endpoint works; the egress allowlist will only permit hosts you allow.

  3. You start chatting through /v1/turn.

  4. Memory ledger, action receipts, external-content firewall, and backups are live from the start; voice, local models, pairing, and artifacts stay off until you opt in.

Setup wizard — admin user, bearer session, and provider configuration
Setup wizard — admin user, bearer session, and provider configuration
Live Optional · off by default Engine · roadmap Built · gated
Choose

Two ways in

Self-host the Apache-2.0 Community Edition yourself, or let us set it up and maintain it for you.

Self-host (DIY)

Free
Apache-2.0 Community Edition

Public source release is pending. The target install path lets you run the backend, the trust kernel, and the web UI on your own hardware.

Soon Public source release is on the way — join the waitlist to hear the moment it lands.

Get early access

Waitlist
Self-host or managed

Leave your email for the open-source release and for managed-install availability. No spam — one note when there's something real to try. Nebula™ is a reserved trademark.

Nebula-COS is an alpha foundation, not a finished assistant.

What's live — self-hosted backend, hosted-provider chat, the trust kernel (memory ledger, receipts, firewall, backups, egress allowlist), installers, and a capabilities contract — is real and tested. What's roadmap — voice, memory recall, and proactivity — is labeled roadmap, never sold as shipped. Own the foundation now; grow into the rest.

See the full live-vs-roadmap matrix →