Glossary
Gain a basic understanding of what Nuon is and how it works.
Nuon is a platform you can use to build, deploy, and manage BYOC apps. This page provides an overview of basic concepts essential to understanding how Nuon works.
Organizations
In Nuon, organizations are the top-level workspace under which all operations are performed. All your apps and VCS connections are created under your organization, and you grant team members access by adding them to your organization.
Org Server and Runner
When you create an organization, we provision a single-tenant server and build runner for you. The server manages the execution of builds and deploys. It is the only part of our system that has access to your source code and your customer installs.
VCS Connections
In order to use source code from private repositories for your components, you need to connect your Nuon organization to your Version Control System (VCS). Refer to our Connect GitHub guide for more details.
Apps
Nuon apps are versions of your application code and infrastructure that can be deployed into a customer cloud account. Refer to our Apps configuration guide for more details.
Components
Nuon app components define what your app consists of. We currently support:
Sandboxes
A Sandbox defines the base infrastructure you want to use for an app’s installs. It provides the base infrastructure components will run on top of, as well as a runner that manages deploys. Refer to our Sandboxes configuration guide for more details.
Installs
An install is an instance of your app running in a customer’s cloud. Refer to our Create Installs guide for more details.
Installers
An installer provides a convenient way for your customers to install your app in their cloud. Configure an installer with your branding, custom content, and metadata, along with the apps you want the installer to support. You can then use it to power a customer-friendly installation UI flow. Refer to our Installers guide for more information.
Builds, Deploys, and Releases
A build packages your component’s source code into an artifact that can be deployed to customer installs. A deploy syncs a component build to a customer install and then provisions the resources that component defines.
Releases orchestrate creating deploys, saving you the overhead of managing thousands of installs yourself. Refer to our Creating a Release guide for more details.