Applications

Run a service from Git, an image, or a one-click preset.

Create one from Applications → Newafter you have a project. Pick a regionand a source.

Source

• Git repository: connect a provider under Git integrations, pick the repo and branch. Nodion scans the tree. Build with a Dockerfile or Buildpacks. If the repo has a compose file you can import the stack. That path is experimental; see Docker Compose.
• Prebuilt image: deploy an existing image, including one you pushed to a Nodion registry.
• Preset: a one-click appwith its own defaults.

Git apps can turn on Auto-deploy so a push to the branch starts a release.

After it exists

The app page has these tabs:

• Overview: status, attachments, first deploy.
• Deployments: history. The header Deploy button starts one.
• Processes: each process is its own containers. Set replicas, package (Discovery or General Purpose), command, ports, and volume mounts.
• Shell: a terminal on a running process.
• Logs and Metrics.
• Environment: your variables (secrets are write-only after save), plus attach databases and buckets. The database must be in the same region. Injected values apply on the next deploy.
• Domains: the default hostname and custom names.
• Previews: Git apps only, not prebuilt images.
• Settings: including preview enablement.

Preview environments

Enable previews in settings. Each preview is an ephemeral app for a pull request or branch: its own URL, and a fresh database. Create one by hand, or auto-create on pull requests. Previews expire. Redeploy or close them from the Previews tab.

Plans

Discovery shares CPU. General Purpose is dedicated vCPU. Live prices are on Pricing.