Documentation
Everything you need to give every git branch its own preview URL.
New to Nexos? Start here.
Nexos gives every branch of your repository a live preview URL. When you push code, Nexos builds your app, provisions a Postgres database and a Redis cache, and serves the whole stack at a shareable URL — usually in under a minute.
A preview environment is a full, running copy of your application tied to one branch. It is how reviewers click through a pull request, how QA reproduces a bug on realistic data, and how designers see working software instead of a Figma mock.
Nexos bills per second of actual use — no idle charges when an environment is paused, no bundled quotas you can't exceed. That is why full-stack previews on Nexos cost a fraction of what they cost on traditional clouds.
The mental model
Three things to keep straight as you read the rest of these docs.
Project
One GitHub repository. Where you configure builds, services, secrets, and resource limits.
Environment
One branch of a project. Has its own app container, database, cache, storage, and preview URL.
Deployment
One git push. Produces a build and updates (or creates) the environment for that branch.
Browse the docs
Getting Started
Sign in, connect a GitHub repo, push a commit, and share your first preview URL — in about five minutes.
Projects
A project connects a GitHub repo to Nexos. Learn how to configure builds, services, and lifecycle hooks.
Deployments
What happens between git push and a live URL — brand new vs incremental deploys, preview URLs, and environment actions.
Environment Variables
Configure encrypted secrets per project. Learn which variables Nexos injects automatically.
Nodes & Providers
Run your own compute node or contribute capacity to the network. Join tokens, agent config, and health monitoring.
Resource Limits
Set CPU and memory ceilings per project, configure build-time constraints, and manage account quotas.
API Reference
Automate Nexos programmatically. Authentication, endpoints, and example requests.