How OpsCompanion Works

OpsCompanion builds a living map by connecting to your infrastructure, automatically discovering resources and relationships, and letting you add the business context that machines can't figure out.

The Living Map

A living map is not a diagram someone drew. It is the actual state of your infrastructure, continuously synchronized from the systems themselves.

The map includes:

• Every resource across your connected cloud providers
• The relationships between those resources, derived from real configuration
• Business context you add: ownership, purpose, dependencies that only humans know
• A timeline of changes across the entire environment (coming soon)

When something changes in production, the map changes with it. No manual updates required.

How the Map is Built

1. Connect

You install integrations with your cloud providers and tools:

• Cloud providers - AWS, GCP, Azure, DigitalOcean
• Code - GitHub repositories and deployments
• Deployment platforms - Vercel projects and domains
• AI-generated apps - Lovable, Base44

Each integration uses read-only access. OpsCompanion observes your systems without modifying them.

2. Discover

Once connected, OpsCompanion begins automatic discovery:

• Resources - Every EC2 instance, Lambda function, storage bucket, database, and service
• Configuration - How each resource is configured, what permissions it has, what it connects to
• Relationships - Security groups, IAM policies, network flows, DNS records
• Changes - What changed, when, and by whom (from audit logs)

This happens continuously. New resources appear in the map as soon as they exist.

3. Enrich

Machines can discover what exists. They cannot discover why it exists.

You add the human knowledge:

• Manual links - Connect resources that are related for business reasons
• Notes - Explain why something exists, what it does, who to contact
• Ownership - Document which team owns what
• Tribal knowledge - The context that would otherwise live only in someone's head

This is what turns a resource inventory into actual understanding.

4. Explore

With the map built, your team can:

• Search - Find any resource across all connected systems
• Trace - Follow connections to see what depends on what
• Investigate - Understand blast radius before making changes
• Ask - Use AI that knows your specific infrastructure to answer questions

What Gets Discovered

Technical Connections

Relationships are derived from actual configuration, not guesswork:

• Security group rules link compute to networking
• IAM policies link roles to resources
• Network flow diagrams show how traffic actually flows (AWS and GCP only)
• DNS records link domains to services

These connections update automatically as your infrastructure changes.

Resource Metadata

For each resource, OpsCompanion captures:

• Configuration and settings
• Tags and labels
• Region and availability zone
• Creation time and last modified
• Associated resources

Change History

From audit logs and provider APIs:

• What changed
• When it changed
• Who made the change
• What the previous state was

Business Context

The most valuable context is what machines cannot discover:

• This database is the source of truth for billing
• This Lambda function is part of the payment processing pipeline
• This S3 bucket contains customer uploads for the onboarding flow
• When this service fails, page the platform team

OpsCompanion lets you capture this knowledge and attach it directly to the resources it describes. When someone new joins the team, they can explore the map and understand the system without asking dozens of questions.

Context-Aware AI

OpsCompanion includes AI that has learned your infrastructure:

• It knows what resources you have
• It knows how they connect
• It knows the business context you've added
• It can answer questions about your specific systems

Ask it:

• "What depends on this database?"
• "What changed in the last 24 hours?"
• "Who owns this service?"
• "What's the blast radius if I take down this EC2 instance?"

The AI grounds its answers in actual data from your environment. It does not hallucinate resources that don't exist or relationships that aren't real.

Data Sources

The living map is built from:

• Provider APIs - AWS, GCP, Azure, DigitalOcean
• OAuth connections - GitHub, Vercel, DigitalOcean
• URL-based connections - Lovable, Base44
• Audit logs - CloudTrail, Cloud Audit Logs, Activity Logs
• Manual context - Links, notes, and ownership you add

All data flows one direction: from your systems into OpsCompanion. Current integrations use read-only access and cannot modify your infrastructure.