Automate environments, infrastructure, and workflows through Git

Upsun uses Git as the control plane for application and environment lifecycle. Infrastructure configuration, environment creation, and operational workflows are defined and versioned alongside application code.

This approach is built for leaders, developers, platform engineers and DevOps teams who want repeatable automation, strong governance, and minimal manual intervention without introducing additional orchestration layers.

What this enables

Git-Driven Automation allows teams to define, automate, and audit platform behavior through Git:

Treat infrastructure and environments as versioned artifacts
Automate platform actions based on real development events
Standardize workflows across teams without slowing delivery

How it works

Git as the source of truth

Application configuration, services, and environment behavior are defined in Git. Every change goes through the same review and approval process as application code, ensuring consistency across environments and eliminating undocumented changes.

Event-driven workflows

Upsun reacts to Git events such as branch creation, commits, and merges. These events can automatically create or rebuild environments, trigger tests, and clean up resources on merge. Automation aligns with how teams already work, without requiring separate pipelines or tools.

Integrated platform actions

Git-driven changes trigger native platform actions such as builds and deployments, and apply resource changes defined in config. Backups are scheduled or triggered via API or CLI, and you can notify or orchestrate external systems with activity scripts or webhooks.

What this solves

Manual infrastructure changes

Manual changes are error-prone and difficult to track. Git-Driven Automation ensures every change is intentional, reviewed, and recorded.

Inconsistent workflows across teams

Different teams often develop their own processes for similar tasks. Defining automation in Git standardizes workflows while still allowing controlled flexibility.

Limited auditability

When automation lives outside version control, it is hard to prove what changed and why. Git provides a clear, immutable history of platform decisions.

Key capabilities

Git-based configuration for applications and environments
Automatic environment creation and cleanup tied to branches and pull requests
Event-triggered platform workflows
Versioned, auditable infrastructure changes
Native support via CLI, API, and integrations
Compatibility with existing Git providers

Enterprise considerations

Governance and control

Git workflows support approval gates, code reviews, and policy enforcement. Platform teams can define guardrails without blocking developers.

Security

Sensitive configuration changes are managed through controlled commits and role-based access. Use API tokens with the CLI for automation instead of shared credentials.

Reliability

Automated actions are executed consistently by the platform, reducing the risk of drift caused by ad hoc scripts or manual intervention.

How teams use this in practice

Preview environment automation

A pull request automatically creates a full-stack preview environment. When the request is merged, the environment is removed without manual cleanup.

Standardized platform operations

A platform team defines a shared configuration for services and resources. All teams inherit the same defaults through Git, ensuring consistency.

Controlled production changes

Infrastructure changes are proposed, reviewed, and merged through Git, creating a clear audit trail for compliance and internal reviews.

Get started

Use Git-Driven Automation to standardize platform operations while keeping development fast and controlled.

Start a free trial Request a demo