Nubo
Start building

the platform

One model, from your repo to a running app.

Everything on Nubo hangs off the same three ideas, whether you deploy from a git push, the CLI, or a coding agent talking to Nubo over MCP.

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 deployable thing inside a Space. Arrange them on a grid so you see everything at once.

a Frame can be

  • web app

    App or API

    An HTTP service that gets a URL and routes traffic.

  • static site

    Static site

    Built from your repo and served as static files. No server to keep alive.

  • worker

    Worker

    A bot or job with no public URL. We keep it running.

  • database

    Database

    Managed Postgres, MySQL, Mongo, or Redis.

click a Space · statuses update live

AC
acme Project
watching for events…
WE
web
main
:3000/tcp
online 1
AP
api
main
:4000/tcp
online 1
RE
redirect
main
:8080/tcp
online 1
MA
marketing
main
:3000/tcp
online 1

inside one Frame

What we actually run.

A web app Frame moves through four layers. You don't have to think about them, but when something surprises you, the dashboard tells you which one is misbehaving.

WE
acme / web · Frame
online

01 source

Your repo, your branch.

GitHub, the branch you pick, the commit you push.

02 build

Code becomes an image.

Nubo detects your stack and builds an image. Dependencies cached between builds.

03 runtime

A container that stays healthy.

Restarts on crash and scales to the replicas you set. Real env vars and secrets, injected at runtime.

04 network

URL, routing, and TLS.

A default subdomain or your own domain. SSL renewed automatically.

us-east-01 · 1 replica 200 OK

Explore by surface.