Integrations
Connect your cloud infrastructure and development tools to OpsCompanion.
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, App Platform apps
Source Control
- GitHub - Repositories, PRs, issues, commits
Deployment Platforms
- Vercel - Projects, deployments, domains
AI-Generated Applications
Plugins
- Slack - Bring OpsCompanion context into team conversations
- Claude Code - Connect coding agents to live OpsCompanion context
- Codex - Investigate systems and act with real-time context
What Integrations Provide
Each integration or plugin expands the living map and makes that context more useful:
- Resource inventory
- Configuration and metadata
- Change history
- Relationship signals
- Shared operational context inside the tools where you already work
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
Plugins extend that same context into your workflows so tools like Slack, Claude Code, and Codex can operate with better awareness of your systems.
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
- Slack - Workspace app connection
- Claude Code - Local plugin connection
- Codex - Local plugin 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.