Platform
Everything you need to run customer environments
Patrol covers the full lifecycle — from defining a reusable service template to deploying, scanning and auditing what's actually running.
Service catalogue
Build a library of reusable service templates
The Catalogue is where you define the 'shapes' of infrastructure you deploy for customers — things like 'Core API', 'Payments Worker', or 'Reporting DB'. Each template has a typed parameter schema, a QA checklist, and deployment config describing exactly how Patrol triggers a deploy.
- Typed parameter schemas (instance sizes, versions, secret references) become per-environment form fields
- Templates are versioned conceptually — environments snapshot the template's config at creation time
- Keep templates in draft until they're ready; only active templates appear when registering environments
Environment management
Track every environment across every customer
Environments belong to a customer and move through a clear lifecycle — Development, Staging, QA, Pre-production, Production. Each one carries its provider, region, cloud account ID and deployment status, all in one list.
- Register environments against active service templates with auto-filled provider and region
- See deployment status, run history and QA progress for every environment at a glance
- Notes and target dates keep delivery context attached to the environment record
Deployment orchestration
Trigger deployments through any pipeline
Deploying an environment creates a deployment run, resolves any secret references, and dispatches to the configured adapter. Synchronous adapters report success immediately; asynchronous ones complete later via a callback — and the run status updates automatically either way.
- Webhook, GitHub Actions, GitLab, Terraform Cloud, Ansible AWX, Azure DevOps and Vagrant adapters
- Run history, status and logs/links visible from the environment's Deployments panel
- Adjust deployment trigger settings or parameter values without editing the underlying template
Secrets management
Credentials stay out of your templates and config
Patrol never stores raw secret values in template or environment configuration — only a reference to where the value actually lives. Secrets are resolved at deploy and scan time, scoped to your tenant.
- Store encrypted credentials once in Settings → Secrets, then reference them by name
- Supports environment variables, Vault paths, and AWS/GCP secret manager references
- Resolved just-in-time by the deployment and scanning workers — never persisted in plain text
Multi-tenancy
Built for teams running many customers at once
Every environment, template and cloud account is scoped to your organisation — with people, teams and QA workflows to match.
Organisations
Create your organisation during onboarding, or join an existing one with a join code and wait for admin approval.
Customers
Track status (Active, Suspended, Offboarding), support tier and default cloud provider/region per customer.
Teams
Group people into teams so QA tasks can be assigned to a team rather than chasing individuals.
QA Kanban boards
Every environment gets a QA board with configurable columns, so reviewers can work through checklist items visually.
See drift detection in action
Patrol's continuous scanning model turns 'what changed?' into a reviewable, auditable workflow.