Docs menu
Glossary
Short definitions of the Primcloud terms used across the docs and dashboard, each linking to the page that covers it.
On this page
Short definitions of the Primcloud terms used across the docs and dashboard. Each links to the page that covers it.
Terms#
Application: a project on Primcloud. Backed by a git repo, owns one or more environments, and lives in a single region. See Applications.
CNAME target: the DNS record you add at your registrar to point a custom domain at Primcloud. Custom domains CNAME to <region>.primcloudns.com. See Domains.
Compute: the CPU and memory a formation runs on, set by its Formation Size and metered by the minute. Standard sizes have shared CPU; Performance sizes have dedicated CPU. See Compute.
Credit: an amount Primcloud adds to your account, applied to your next invoice before your card is charged. See Plans.
Deployment: one commit built and released to an environment. Pushes, manual deploys, secret saves, compute changes, rollbacks, and redeploys each create one. See Deployments.
Domain: a hostname pointed at an environment. Every environment gets a *.primcloud.app URL, and you can add custom domains. See Domains.
Environment: one running copy of an application, with its own tracked branch, configuration, formations, and URL. Every application starts with a production environment. See Environments.
Formation: one process type your app runs (web, worker, or any other name from your Procfile), with a Formation Size and an Instances count. See Formations.
Past-due: the account state when an invoice's automatic charges haven't succeeded. Your apps keep running, but anything that would grow your bill is blocked until you pay it. See Past-due & Suspension.
Placeholder: the page visitors see when an environment is in maintenance or suspended, or at an address with nothing deployed. See Environments.
Primcloud Runtime: what builds and runs your app. It detects your language from files like package.json, composer.json, and Gemfile, then installs your dependencies and builds your app. See Language Support.
Procfile: a file at the root of your repo declaring one process type per line (name: command). Each becomes a formation. See Formations.
Provider: a connected git host whose repos Primcloud builds and deploys. See Source Control.
Region: where an application runs. Chosen when you create the application, and it can't be changed. See Regions.
Release process: the release command in your Procfile, run once per deploy before traffic moves to the new version. See Deployments.
Secret: a configuration value set on an environment, which your app reads as an environment variable during the build and at runtime. Encrypted at rest. See Secrets.
Standard: the $0 plan every account starts on, with compute billed from the first minute. Pro is $29/mo and Team is $49/mo. See Plans.
Suspended: the account state when an invoice is still unpaid 14 days after the account went past-due. Every environment stops and visitors see a suspended page. Nothing is deleted, and everything comes back once you pay. See Past-due & Suspension.
Task: a one-off command run against a fresh copy of your app's current build. It runs, exits, and keeps its output. See Tasks.
Usage alert: a threshold you set on build minutes, spend, bandwidth, failed deployments, or build duration that notifies you when it's crossed. See Plans.