Glossary

Quick definitions for the Primcloud-specific terms you'll see across the docs and dashboard. Each entry links to the page that covers the concept in full.

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 vCPU and memory each pod runs on, sized per formation and metered by the minute at rates quoted per hour. Two tiers: Standard (shared) and Performance (dedicated). See Compute.

Credit: a balance Primcloud applies to your account (a goodwill adjustment, a correction, or a promotional grant). It shows on your invoice as a line item and is applied against your balance automatically before your card is charged. See Plans.

Deployment: one full build-and-release cycle. Every push to a mapped branch, manual deploy, secret save, compute change, rollback, and redeploy creates a deployment. See Deployments.

Domain: a hostname pointed at an environment. Every environment gets a free *.primcloud.app URL; you can attach any number of custom domains on top. See Domains.

Environment: one running slice of an application. Has its own tracked branch, configuration, formations, and URL. Every application starts with a production environment. See Environments.

Formation: see Pod Formation.

Past-due: the account state after an invoice's automatic retry schedule finishes without succeeding. Your apps keep running; anything that would grow your bill is blocked until you settle the outstanding invoice. See Past-due & Suspension.

Placeholder: the page visitors see when an environment is in maintenance mode or suspended, or the "Deployment not found" page at an address with nothing serving it. See Environments.

Pod formation: one process type your app runs (web, worker, or any custom name from your Procfile), with a replica count and compute size. See Pod Formations.

Primcloud Runtime: the language-detection and build pipeline that turns your repo into a running app. It detects your language from files like package.json, composer.json, and Gemfile, then installs and compiles your app during the build phase. See Deployments.

Procfile: a Procfile at the root of your repo declaring one process type per line (name: command). Each entry becomes a pod formation after the build. See Pod Formations.

Provider: a connected git host (currently GitHub) that Primcloud can read from to build your apps and receive push webhooks. See Source Control.

Region: the geographic location where an application's compute runs. Chosen at application creation and fixed for the life of the application. See Regions.

Release phase: the second half of a deployment. Runs the release process from your Procfile if it's declared, then rolls each long-running formation to the newly built image with a rolling update. See Deployments.

Rolling update: the update pattern Primcloud uses to swap a formation's pods to a new image or size without dropping traffic. New pods start and pass readiness, then old pods terminate. See Deployments.

Secret: a configuration key/value scoped to an environment, injected into your pods as an environment variable. Available at build time and at runtime; encrypted at rest. See Secrets.

Standard: the $0 plan every Primcloud account starts on, with compute billed from minute one. Upgrade to Pro ($29/mo), or create a Team ($49/mo), from Account → Billing. See Plans.

Suspended: the account state after the 14-day past-due grace period lapses without payment. Every environment is stopped and visitors see a suspended placeholder page; nothing is deleted, and the account returns to Active the moment the outstanding invoice clears. See Past-due & Suspension.

Task: a one-off command run against a fresh copy of your app's current build. Distinct from long-running pod formations: a task spins up, runs, and exits. See Tasks.

Usage alert: a threshold you set on a billing signal (build minutes, total spend, compute spend, bandwidth, deployment failures, or build timeout) that emails you when it's crossed. See Plans.