push to deploy
GitHub to live URL.
Our cloud, yours, or both.
Web apps, static sites, and workers, all from one dashboard. We run the servers, or you bring your own.
no card for the trial · sign in with github
Deploys today
14-day trend
Frames online
5/7
all healthy
In flight
1
deploys in progress
Projects
1
across 1 region
| Project | Description | Building | Updated |
|---|---|---|---|
| checkout | Stripe checkout flow | 1 now | 5d ago |
- 15:47
Build started on checkout
checkout
- 15:47
Frame created in checkout
checkout
- 15:45
Deploy succeeded on checkout
checkout
-
-
-
what people ship on nubo
Whatever you're building, we'll host it.
Side projects live next to revenue-generating apps in the same dashboard, with the same deploy flow for both.
-
web apps & APIs
Web apps
MVPs, prototypes, or production traffic. Whether it's day one or after you launch.
-
side projects
Side projects
Have an idea Friday night? It can be live by Sunday morning, with logs and a real URL.
-
internal tools
Internal tools
Admin dashboards, ops panels, or prototypes. Shipped in an afternoon.
-
bots & workers
Bots & workers
Discord bots, Slack apps, or scheduled jobs. We keep them running.
-
static sites
Static sites
Marketing pages, blogs, docs, or portfolios. Deployed from your repo.
-
your weird thing
Whatever you're cooking
If it runs in a container, it runs on Nubo. We've seen weirder.
from idea to internet
Four steps. No DevOps engineer required.
Most platforms make you learn a whole new vocabulary before your first deploy. Nubo doesn't.
- 01 connect
Point at a repo.
Sign in with GitHub, install the Nubo app, pick the project. The whole setup takes under a minute.
- 02 choose where
Our cloud or your server.
Default to Nubo Cloud. Or, if you have a server already, connect it with a single command.
- 03 push
git push, like always.
When you push, Nubo builds and ships. You don't write any CI config, Kubernetes manifests, or YAML.
- 04 live
Share the link.
You get a URL with TLS already set up. Want yourdomain.com? Add it in the dashboard and we handle the rest.
push on the left. nubo reacts on the right.
- webhook accepted
- image build started
- image pushed
- rolled out · 200 OK
Projects, Spaces, Frames
The same three-layer model as the dashboard.
01 Project
The thing you're building. Holds your landing page, API, workers, and database in one place.
02 Space
An environment inside a Project. Most have a dev, staging, and production.
03 Frame
One running app inside a Space. Arrange them on a grid so you see everything at once.
click a Space · statuses update live
inside one Frame
What we actually run.
Each Frame has four layers. You don't have to think about them, but when something surprises you, the dashboard tells you which one is misbehaving.
01 source
Your repo, your branch.
GitHub, the branch you pick, the commit you push.
02 build
We turn code into an image.
Buildpacks or your Dockerfile. We cache dependencies between builds.
03 runtime
A container. Healthy by default.
Restarts on crash. Scales replicas as you ask. Real env vars and secrets.
04 network
URL, routing, and TLS.
A default subdomain, or hook up your own. SSL renewed automatically.
in the dashboard
Built-in for the boring parts.
Logs, rollbacks, domains, metrics. The whole set lives in one console, next to the deploys that produced them.
live logs
See what your app is doing.
Requests, console.logs, and errors stream into the same dashboard you deploy from, in real time. You can search, filter, and tail them. Logs persist across deploys, so yesterday's bug is still readable today.
- v1.4.2 commit c0ffeebee · mainfailed
- v1.4.1 commit 4b2a91e · main
- v1.4.0 commit ae31fa2 · main
- v1.3.9 commit 9f8de31 · main
one-click rollback
Shipped a bug?
Undo it.
Every deploy is saved. When a release goes sideways, click "Roll back" on the last good one. Traffic returns to it in seconds. No git surgery required.
custom domains
Your domain. HTTPS handled.
Connect your domain in the dashboard, paste the hostname, hit save. We issue the TLS cert, keep it renewed, and route traffic. The whole thing takes a minute.
Hostname
- Domain connected
- TLS certificate issued
- Routing live traffic
Deploys today
11
Frames online
12/ 14
Build p95
42s
metrics
The numbers worth tracking.
Deploys per day, Frames online, build performance. The same fleet-wide view we use ourselves, available the moment your first Frame ships.
self-host with agents
Bring your own server.
Keep the dashboard.
Run Nubo on hardware you already own. Same dashboard, same workflow. No vendor lock-in.
- 01 Connect a new agent in your Nubo settings. You'll get a token.
- 02
Install the agent on your server.
$ curl -fsSL https://dl.withnubo.com/nubo-agent/install.sh | bash - 03 Pick it as a deploy target on any Frame.
- 04 Logs and status stream back live.
agent live link · websocket
*.frames.example.com → your server
- · agent connected
- · task dispatched
- · logs streaming back
- · rolled out
deploy task
logs · state
nubo-agent
- · docker + caddy ready
- · pulling git repo
- · building image
- · serving traffic
and the rest
-
Push to deploy
Wire up GitHub once. Every push lands as a deploy.
-
Encrypted secrets
Env vars and API keys live in one place. Encrypted at rest.
-
TLS by default
Every URL is HTTPS. Certificates renew themselves.
-
Cheap to run
$5 of monthly usage credits cover most side projects. No card to start the 7-day trial.
pricing
Seven days free.
Then $4.99 a month.
Every month includes $5 of usage credits, enough to cover most side projects and prototypes end-to-end. Above that, you only pay metered rates for the vCPU, memory, and egress your Frames actually use.
nubo basic
Free for 7 days. No card to start.
- 7-day free trial, no card to start
- $5 of usage credits every month
- Push-to-deploy from GitHub
- Custom domains + TLS, real-time logs
- Rollback, metrics, auto-scaling replicas
- First self-host agent free
stop reading
Got an idea?
Ship it tonight.
Sign up with GitHub, pick a repo, and we'll take it from there. Seven days on the house, no card and no sales call required.