On this page
Deploy apps with PaaS
The platform-as-a-service option provisions a managed application platform on a virtual machine for you, so you can deploy apps and databases from Git and manage their environment without operating servers yourself.
When you create a PaaS instance, the platform provisions a virtual machine, installs a managed application platform on it, and hands you a ready-to-use dashboard. From there you connect a Git repository, define a build, set environment variables and deploy, all through the application platform's own interface.
The instance is yours: it gets a subdomain on the platform, can reach your private networks, be assigned a floating IP, and carry custom domains. Networking, storage volumes, snapshots and vault-backed secrets are managed from the instance's page in the Patrii Cloud console, while day-to-day app deployment happens in the platform dashboard.
Key concepts
PaaS instance — A managed application platform running on a dedicated virtual machine you own.
Dashboard URL — The web address of the application platform where you connect repositories and deploy.
Flavor — The CPU, memory and disk size of the underlying VM, chosen from your allocations.
Subdomain / FQDN — The auto-assigned hostname the instance answers on under the platform's PaaS domain.
Vault-backed secret — An environment secret stored securely and injected into your app at deploy time.
Custom domain — Your own domain pointed at the instance, with DNS handled automatically or set manually.
Before you start
- A compute flavor allocation to run the instance on.
- An admin email for the platform's initial administrator account.
- A Git repository for the app you want to deploy.
- Optionally, a private network and a custom domain.
Step by step
- Start a new instance
Go to PaaS and create a new instance. Choose a subdomain and provide the admin email; the full hostname is your subdomain plus the platform PaaS suffix.
Screenshot — The New PaaS form showing the subdomain field and its hostname previewThe New PaaS form showing the subdomain field and its hostname preview - Set networking
- Attach one or more private networks, choose whether to assign a floating IP for public reachability, and select security groups (the firewall).
- Public reachability comes from the floating IP toggle, not from attaching a public network directly.
Screenshot — The networking step with network, floating-IP and security-group controlsThe networking step with network, floating-IP and security-group controls - Choose storage
Keep ephemeral storage for a simple setup, or select a volume and set its size so data survives a rebuild of the instance.
- Pick a flavor and create
Select a flavor from your allocations and create the instance. Provisioning takes a few minutes.
Screenshot — The flavor cards with availability and the Create instance buttonThe flavor cards with availability and the Create instance button - Save the admin credentials
When provisioning finishes, the console shows the dashboard URL and a one-time admin username and password. Copy them now; the password is shown once.
Screenshot — The credentials dialog with the dashboard URL, admin username and passwordThe credentials dialog with the dashboard URL, admin username and password - Deploy from Git
- Open the dashboard URL and sign in with the admin account.
- Connect your Git repository, configure a build and deploy the application or database.
- Manage environment secrets
Back on the instance page in the console, add vault-backed secrets (for example DB_PASSWORD). Enter a value or have one generated, and it is injected into your app securely.
Screenshot — The Add secret dialog with the generate toggleThe Add secret dialog with the generate toggle - Add a custom domain
Add your own domain to the instance. If the domain is on Patrii Cloud DNS, records are created automatically; otherwise the console shows the IP to point your DNS at.
Screenshot — The custom domains table showing DNS mode and target IPThe custom domains table showing DNS mode and target IP
Examples
# Added as vault-backed secrets on the instance page, # then available to your app at deploy time: DATABASE_URL=postgres://app:...@db:5432/app SECRET_KEY_BASE=<generated> REDIS_URL=redis://cache:6379/0
# When the domain is not on Patrii Cloud DNS, create an # A record at your provider pointing to the shown IP: app.example.com. A 203.0.113.10
Limits & specifications
What you manage from the instance page:
| Area | What you can do |
|---|---|
Lifecycle | Start, stop, reboot and snapshot the instance. |
Networking | Attach or detach interfaces, security groups and floating IPs. |
Storage | Attach a new volume or mount an existing one. |
Secrets | Add, generate or remove vault-backed environment secrets. |
Domains | Add custom domains with automatic or manual DNS. |
Backups | Use object storage for backups when the quota is available. |
Best practices
- Save the one-time admin password the moment it is shown; it cannot be retrieved later.
- Put application data on a volume rather than ephemeral storage so it survives a rebuild.
- Manage app secrets as vault-backed secrets instead of hard-coding them in the repository.
- Open only the ports you need in the instance's security groups.
- Take a snapshot before a risky change so you can roll back.
- Enable object-storage backups so you can recover the platform state.
FAQ
How is PaaS different from a plain VPS?
I did not copy the admin password. What now?
My instance is not reachable from the internet.
Can I use my own domain instead of the assigned subdomain?
Learn more
Everything you can do here in the console is also available through the Patrii Cloud API for automation and scripting.