Welcome to Nubo

Documentation Index

Fetch the complete documentation index at: https://docs.withnubo.com/llms.txt

Use this file to discover all available pages before exploring further.

Nubo runs your code in the cloud without making you babysit servers. You connect a GitHub repo, pick a branch, and we figure out the rest: language detection, build, container image, HTTPS-ready URL. Push to your tracked branch and the next deploy goes out automatically. No Dockerfile. No YAML manifests. No ImagePullBackOff errors at 2am.

​

Who Nubo is for

Whether you’re a:

• Solo dev spinning up a side project before lunch
• Indie hacker running ten micro-apps without ten different control panels
• Student trying to deploy your first real backend
• Startup that wants production infra without a platform team

If you’ve got code and a port number, you’ve got a Nubo deploy.

​

What ships out of the box

• Auto-detected builds. Go, Node, PHP, Python, and static sites are recognized from your repo. No config required for the common case.
• Push-to-deploy. Every push to your tracked branch triggers a build. Preview deploys for every PR.
• HTTPS + a free domain. Every Frame gets a *.nubo.onl URL with HTTPS. Bring your own domain when you’re ready.
• Environments. A Project holds multiple Spaces (dev, staging, production), each with their own variables, history, and URL.
• Rollback in one click. Bad deploy? Roll back to a known-good version from the dashboard.

​

A note on builders

Two builders ship with Nubo today:

• Raypacks (Beta) is our new daemonless builder. Fast, opinionated, the default for new Frames. Covers Go, Node, and static sites.
• Paketo is the classic Cloud Native Buildpacks path. Slower but more configurable. Still the right call for Python, PHP, and anything Raypacks doesn’t cover yet.

You can switch between them per-Frame in Frame Settings → Builder.

---