Integrations
Connect your cloud infrastructure and development tools to OpsCompanion.
Integrations allow OpsCompanion to observe and model your environment using read-only access.
Supported Integrations
Cloud Providers
- AWS - EC2, RDS, Lambda, S3, DynamoDB
- GCP - VMs, Cloud Run, Cloud SQL, Cloud Storage
- Azure - VMs, SQL databases, storage accounts
- DigitalOcean - Droplets
Source Control
- GitHub - Repositories, PRs, issues, commits
Deployment Platforms
- Vercel - Projects, deployments, domains
AI-Generated Applications
What Integrations Provide
Each integration contributes to the living map:
- Resource inventory
- Configuration and metadata
- Change history
- Relationship signals
How Integrations Work
- You install the integration with read-only access
- OpsCompanion calls provider APIs to discover resources
- Configuration and relationships are mapped
- Changes are tracked continuously
Authentication Methods
- AWS - IAM role assumption with external ID
- GCP - Workload Identity Federation
- Azure - Service principal with Reader role
- DigitalOcean - OAuth
- GitHub - OAuth with read-only scopes
- Vercel - OAuth with read-only scopes
- Lovable - URL-based connection
- Base44 - URL-based connection
Constraints
- Current integrations use read-only access
- No agents or sidecars are installed
- You can revoke access at any time
Adding Integrations
Integrations are additive. Start with one system and expand over time.
Each integration expands the model with additional structure and context.