Introduction

Primcloud is a platform-as-a-service: hand it your git repo and it builds your app, deploys it, and keeps it running. These docs are the reference for every piece of the platform: the mental model, the deploy flow, the runtime, billing, and everything you can configure.

The model#

Five concepts show up on almost every page. Learn them once here and the rest of the docs read straight through.

• Application: a project on Primcloud. Backed by a git repo, owns its environments (one, production, on Standard; more per application on Pro and Team).
• Environment: a deployment target inside an application. Every application starts with a production environment, which owns its own branch, configuration, domains, and running processes.
• Deployment: a specific build of your application released to an environment. Every deploy is addressable and rollback-able.
• Pod formation: a process type your app runs (web for HTTP, worker for background work), with a replica count and compute size.
• Domain: a hostname pointed at an environment. Includes the free *.primcloud.app subdomain and any custom domains you attach.

Configuration (secrets, compute sizing, formations) is scoped to environments.

Where to go next#

• New here? Start with the Quickstart and deploy something in a few minutes.
• Working through the concepts in order? Read the Basics section top to bottom, starting with Source Control.
• Deploying a specific stack? Jump into Language Support for your language.
• Sorting out billing? Head to Billing.