Deploy anything on a server you own. A new version only goes live if it answers.
Noust deploys web applications on Linux servers you own. It writes the nginx or Apache site, the certificate and the systemd unit, builds every deploy as a release that only goes live if it answers, and can put the previous one back in seconds.
Install, checking the script first
curl -fsSLO https://github.com/Perkybeet/noust/releases/latest/download/install.sh
curl -fsSLO https://github.com/Perkybeet/noust/releases/latest/download/SHA256SUMS
sha256sum -c --ignore-missing SHA256SUMS && sh install.shIt downloads the installer and its checksums, and runs it only if they match. What it installs, and the other ways.
Where to start
Pick the line that sounds like you.
- New to Noust What it is, how to install it, and a first application from start to finish. What Noust is, and when it is not for you
- Running servers for a team Several servers from one console, single sign-on, roles, audit and compliance. Run a central
- Coming from another platform Bring an application across with its settings and its data, and move its domain. Move an application from Coolify or Dokploy
What people come here to do
Each one opens the page that does it, from the first command to the check that it worked.
- A domain with HTTPS Point a name at the server, check it, add it to the application, send www to it, and get a certificate that renews itself.
- A database A PostgreSQL database with an account of its own, linked as DATABASE_URL, and migrations that run before each version serves.
- Backups, and getting them back A nightly backup with the databases, an encrypted copy off the server, and a rehearsal that shows it restores.
- Roll back a bad deploy Deploy a new version behind the health check, put the previous one back in seconds, and deploy on every push.
- Deploy from CI Deploying from a pipeline with a token, the deploy endpoint and the GitHub Action.
- A preview for each pull request Previews built from a pull request, a branch or a tag, for any application including a Compose stack.
- Teammates and single sign-on Teams, projects and environments, and what each role sees.
- Several servers Manage a second server from the console of the first, over an SSH tunnel that gives it no shell.
Something is wrong?
noust diagnose names the most likely cause first. The frequent failures are here, with their messages.
- Symptom:The site answers 502, or does not answer
- Symptom:A build or a deploy failed
- Symptom:A certificate was not issued, or is about to expire
- Symptom:The name does not point at the server
- Symptom:I cannot sign in to the console
- Symptom:The console does not open
- Symptom:The installation did not work
- Symptom:An update says it is on the way, or the package index is behind
Look something up
Every command, endpoint and setting, and what changed in each release.
The whole documentation
6 parts, one question each. The search (Ctrl K) reaches every page.
- Start What Noust is, how to install it, and a first application from start to finish. 17 pages
- Guides How to do one thing, one task per page. 91 pages
- Concepts Why Noust works the way it does. Explanation, no steps. 6 pages
- Reference The exact command, endpoint or setting. Generated from the code wherever it can be. 156 pages
- Releases What each release changed, how to upgrade, and how to go back. 12 pages
- Project Getting help, contributing, and the security policy. 9 pages