Skip to main content
A quick tour of the words you’ll see across the dashboard and these docs.

​
Project

The top-level container for your app and everything around it: landing page, API, dashboard, database. One Project usually corresponds to one product or side project. Projects have shared variables and settings that flow down to everything inside.

​
Space

An environment inside a Project. Most people run dev, staging, and production Spaces. Each Space has its own deploy history and its own URLs. You can break things in dev without touching production.

​
Frame

A running app. Your landing page is a Frame. Your API is a Frame. Your Discord bot is a Frame. Each Frame:
  • Watches one branch of a GitHub repo
  • Has its own port and runtime settings
  • Gets its own *.nubo.onl URL (and any custom domains you attach)
  • Tracks its own deploy history
Other platforms call this a “service” or “app”. On Nubo it’s a Frame. Frames come in two kinds. An App Frame is source you build and run from a GitHub branch (the default, and what most of these docs describe). A Database Frame is managed storage Nubo runs for you (Postgres, MySQL, MongoDB, or Redis) that your apps connect to. See Databases.

​
Frame visibility

Every Frame is either Public or Private. Private is the default: only people with access to the Project can see it. Make a Frame Public and it shows up on your public profile. Set it per Frame in Frame Settings → Visibility.

​
Deployment

One build-and-release of a Frame. Pushed code? That’s a deployment. Hit “Deploy” in the dashboard? Also a deployment. Each one has a build log, a status (Queued, Building, Succeeded, Failed, Canceled), and a commit it was built from. See Deployments. Deployments come in two kinds. A Primary deployment serves the Frame’s main URL: it’s what visitors get. A Preview deployment is a temporary copy, typically built from a pull request, that gets its own URL and is torn down when the PR merges or closes. See Preview deployments.

​
Builder

The thing that turns your code into a container image. Two are available:
  • Raypacks (Beta) is the default. Fast, daemonless, four packs covering Go, Node, static, and Dockerfile.
  • Paketo is the classic option. Slower but covers more languages (Python, PHP, etc.) and exposes finer-grained config through BP_* env vars.
Pick per-Frame in Frame Settings → Builder.

​
Volume

A block of persistent storage you can attach to a single Frame. Files written to a volume’s mount path survive redeploys, rollbacks, and restarts. See Volumes.

​
Variable

A key-value pair fed into your app at runtime. Scoped to a Project (shared across Frames) or a Frame (just that one). See Environment variables.

​
Custom domain

Your own hostname (app.example.com) pointing at a Frame, with HTTPS handled automatically. See Custom domains.

​
Plan

Your account tier. Sets how much compute Frames can request, storage limits, and how long build logs are kept. See Plans and billing.

​
Team

A group of people you share Projects with. Members get a role (viewer, member, admin, or owner) and you grant the team access to specific Projects. See Teams.

​
Organization

A shared home for a group of people, with roles and a single owner. Every account gets a personal organization, and you can create shared ones for a company or a group of collaborators. See Organizations.

​
Public profile

Your builder page at withnubo.com/@handle. It shows your name, bio, and the Frames you’ve marked Public. Turn it on (and edit what it shows) in Settings → Public profile. See Profiles.

​
Self-hosted agent

A Nubo runtime you install on your own machine, instead of running on Nubo’s cloud. Same dashboard, same deploy flow, your hardware. See Self-hosted agents.