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 rundev, staging, and production Spaces.
Each Space has its own variables, 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.onlURL (and any custom domains you attach) - Tracks its own deploy history
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, Online, Failed), and a commit it was built from. See 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.
Volume
A block of persistent storage you can attach to one or more Frames. 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 build and 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.
