Skip to main content

How OPSd works

Build the foundation, then connect the pieces your application needs.

OPSd generates configuration for a separate cloud environment and Kubernetes platform. Your team reviews and applies the cloud changes, connects its Git repository, and provides the application's deployment files. Cloud resources vary by provider.

A guided path

From a separate cloud environment to an application your team can run

Select a stage to highlight the parts of the platform involved. DigitalOcean is available today; AWS and Azure paths are planned.

Cloud environment Kubernetes GitOps Your application

Your workstation

OPSd CLI
Review and apply

Your cloud account

Separate environment
Network
Kubernetes cluster

Application platform

GitOps controller
Application entry point
DNS name
TLS certificate
Secret sync
Your application
Monitoring and telemetry Planned
Application CI integration Planned

Your Git repository

Platform configuration
Application manifests or charts

Cloud foundation

OPSd Review and apply Separate environment Network Kubernetes

GitOps delivery

Git repository GitOps controller Application

Application access

Application Entry point DNS name TLS certificate

Secrets and future platform work

Secret sync Application Monitoring CI integration
OPSd prepares Your team configures Planned

Who does what

OPSd prepares the setup. Your team decides when to create cloud resources, controls access, and supplies the application configuration.

OPSd generates the setup

OPSd generates reviewable configuration and groups its cloud resources in a dedicated environment, so they are easy to identify and manage alongside resources your team created separately. It prepares the platform, not your application code.

Your team applies cloud changes

Review the Terraform or OpenTofu plan, then apply it in your cloud account when you are ready. OPSd generates the plan; your team decides when to create the resources.

Argo CD follows your Git repository

Your team connects a Git repository and adds the application deployment files. Argo CD then reads that repository and keeps supported resources in Kubernetes in sync with its configuration.