Integrations
Connect cloud providers, version control, observability, and alerting systems to ops0. Integrations let brew.ops0.ai discover resources, run deployments, sync code, and send operational signals into the tools your teams already use.
Accessing Integrations
Go to Settings
Navigate to Settings from the main sidebar.
Open Integrations
Select Integrations to view connected providers, statuses, and available setup flows.
Integration Categories
Cloud
AWS, GCP, Azure, and Oracle Cloud for deployments and discovery.
Git
GitHub and GitLab for repository sync, pull requests, and version-control workflows.
Observability
Route logs, plans, and policy output into your observability stack.
Alerts
Send delivery, approval, and incident alerts into collaboration channels.
Shared Fields
Most integrations expose a common management surface in ops0:
| Field | Description |
|---|---|
| Name | Human-readable label for the integration |
| Type | Provider or category, such as AWS, GitHub, or Slack |
| Status | Connection health, such as Connected or Error |
| Created | When the integration was added |
| Last Used | The most recent time ops0 used the integration |
Cloud Integrations
Cloud integrations provide provider-specific credentials and trust relationships so ops0 can discover resources, run deployments, and scope access correctly.
Each cloud provider has its own setup page because authentication models, required fields, and permission boundaries differ significantly.
Git Integrations
Git integrations connect ops0 projects to source-control providers for syncing IaC code, opening pull or merge requests, and managing repository access.
Observability
Observability integrations send execution output and policy context into logging and monitoring systems.
Observability Guide
Overview, supported provider details, data types, and troubleshooting.
OpenObserve
Legacy alias path retained for compatibility.
Alerts
Alerts integrations deliver deployment notifications, approval requests, policy findings, and incident signals into collaboration tools.
Alerts Guide
Configure channels, alert types, and workspace authorization.
Slack
Current supported alerts provider.
Lifecycle Actions
After an integration is added, the operational lifecycle is broadly the same regardless of provider:
Test Connection
Run a connectivity check to verify that credentials, scope, and network access are valid.
Edit Configuration
Update names, endpoints, regions, channels, or provider-specific settings as requirements change.
Rotate Credentials
Replace keys, secrets, tokens, or app access when your rotation policy requires it.
Review Usage
Confirm which projects, workflows, or scans rely on the integration before changing or deleting it.
Delete Safely
Remove the integration only after checking for affected projects, workflows, or automation.
Naming Guidance
Use explicit names so teams can distinguish integrations quickly:
| Good Example | Why It Works |
|---|---|
aws-production-us-east-1 | Captures provider, environment, and region |
gcp-analytics-prod | Makes project purpose obvious |
github-platform-org | Identifies account or org scope |
slack-deploy-alerts | Indicates the alerting use case |