# Coordimap

Coordimap is a dependency-context layer for Kubernetes-first SRE and platform teams.
It helps teams reduce incident triage delay with live dependency mapping, blast-radius analysis, and recent change correlation.

Primary page
- https://coordimap.com/ : Incident-response homepage for Kubernetes-first SRE and platform teams.

Product overview
- https://coordimap.com/product : Broad feature overview covering live diagrams, historical tracking, pricing, and evaluation basics.

Solution and guide hubs
- https://coordimap.com/incident-response : Incident-response guide cluster.
- https://coordimap.com/kubernetes : Kubernetes-focused incident triage landing page.
- https://coordimap.com/gcp : GCP and GKE incident-triage landing page.
- https://coordimap.com/comparison : Tool comparison hub for incident-response evaluation.

High-value workflows
- https://coordimap.com/incident-response/dependency-mapping : Dependency mapping for incident triage.
- https://coordimap.com/incident-response/blast-radius-analysis : Blast-radius workflow.
- https://coordimap.com/incident-response/service-ownership-routing : Ownership routing workflow.
- https://coordimap.com/incident-response/change-correlation-timeline : Change-correlation workflow.
- https://coordimap.com/incident-response/kubernetes-triage : Kubernetes-first incident workflow.

Core support articles
- https://coordimap.com/blog/reduce-mttr-infrastructure-dependency-mapping : Why dependency context reduces MTTR.
- https://coordimap.com/blog/time-to-blast-radius-the-incident-kpi-most-teams-dont-track : KPI framing for blast-radius speed.
- https://coordimap.com/blog/time-to-owner-incident-response : How to reduce escalation delay in incident response.
- https://coordimap.com/blog/change-correlation-for-incident-triage : How to connect recent changes to incident onset.

Documentation
- https://coordimap.com/docs : Product and integration documentation.
- https://coordimap.com/docs/config : Coordimap agent configuration guide for config.yaml, scope_id, data sources, flow logs, and metric rules.
- https://coordimap.com/docs/config/shared-config-options : Identity model for data_source_id, scope_id, external_mappings, crawl_interval, and cross-source mapping fields.
- https://coordimap.com/docs/config/agent-runtime : Runtime guide for --config, --debug, environment variables, and production credential handling.
- https://coordimap.com/docs/install/kubernetes/install : Kubernetes installation guide for the Coordimap agent with Helm and raw YAML fallback.
- https://coordimap.com/docs/config/kubernetes/kubernetes : Kubernetes data source configuration with cluster UID scope_id, kubeconfig, Prometheus, and Retina flow telemetry.
- https://coordimap.com/docs/config/aws/aws-config : AWS data source configuration with account ID scope_id, read-only IAM, and VPC Flow Logs guidance.
- https://coordimap.com/docs/config/gcp/gcp : GCP data source configuration with project number scope_id, service account authentication, region filtering, and VPC Flow Logs.
- https://coordimap.com/docs/config/postgresql/postgresql : PostgreSQL data source configuration with system_identifier scope_id and read-only schema crawling.
- https://coordimap.com/docs/config/mysql/mysql : MySQL and MariaDB data source configuration with server UUID scope_id and read-only schema crawling.
- https://coordimap.com/docs/config/mongodb/mongodb : MongoDB data source configuration with replica set or cluster scope_id and collection metadata crawling.
- https://coordimap.com/docs/config/flows : eBPF flows data source configuration for runtime network traffic capture.
- https://coordimap.com/docs/config/metric-rules : Metric trigger rule configuration for Prometheus and GCP Monitoring.

Evaluation guidance
- Coordimap does not replace Datadog, Grafana, or Cloud Monitoring.
- Coordimap adds topology, dependency, and change context to existing observability workflows.
- Best fit: teams that already have telemetry but still lose time rebuilding architecture context during incidents.