Public or private, as a setting
A public app is open to anyone holding the URL. A private app demands an identity
on every request: agent tool calls carry the app's edge token automatically, and a
person is sent to sign in with Nexus. A client with neither gets a 401 — never a
silent 404.
Your app becomes a tool your agents can call
Hand a healthy deployment its OpenAPI spec and it registers as a callable tool in
the same org. The platform owns the endpoint — it is the app's own public URL, so
a tool can never be pointed somewhere else by accident.
Versions, and a rollback that does not rebuild
Every deploy is a numbered version. Restore the previous one, or name an older
one, and the platform re-activates the image it already has — atomic, no build, no
new version spent, and the live version keeps serving until the restored one is
healthy.
A human gate, when you want one
Turn on approvals and a successful build waits for a person between build and
deploy. Never the person who triggered it.
A gate on the repository itself
The ship gate reads the commit for the verification artifacts you declared and
refuses the deploy if they are missing or red — before a single build minute is
spent. Off, warn, or enforce. Warn is the on-ramp: it reads, records and ships
anyway, so you can see what enforce would have stopped.
Env vars and org credentials
Per-app environment variables, plus the access cards imported from your org — so a
secret lives in one place rather than in two dashboards.
Logs you can actually read
Runtime output, oldest-first. Follow it live, filter it to one deployment slot, or
keep only the lines containing a literal string.
An audit feed, append-only
Every transition is a row: deployments, approvals, rollbacks, cost-safety state
changes.
A spend ceiling that acts
Cost safety refuses new deploys for an org over its ceiling, and rolls live ones
back. The platform enforces it — it is not a dashboard warning.
Your own cluster
An org can provision a dedicated Vibe cluster. EU regions only — that one is
deliberate.
A starter that runs on arrival
nexus apps starter my-app downloads the org app skeleton with the
component library already vendored. No npm token, no registry setup, no blank
page.
One CLI for all of it
Create, deploy, watch, roll back, read logs, attach a domain, set visibility,
approve a gated release — one tool, authenticated as your org.