Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

Flanksource Mission Control

flanksource.com

  • Free trial
  • Web
  • API
  • Self-hosted
7.0 Club score Visit flanksource.com

What Flanksource Mission Control is

Flanksource Mission Control is an internal developer platform focused on developer productivity and operational resilience. Its catalog discovers, transforms, and tracks infrastructure, applications, and configuration across environments. Health checks can be synthetic, passive, infrastructure, or integration checks across services and infrastructure. Reusable playbooks can start from users, events, or webhooks to automate workflows and support developer self-service. Documented integrations include Kubernetes, AWS, Azure, GitHub, Azure DevOps, Prometheus, Datadog, Dynatrace, CloudWatch, and Elasticsearch. Mission Control supports self-hosted, SaaS, and hybrid deployment, and the maker describes it as self-hosted first. Self-hosting requires Kubernetes 1.26 or later, an ingress controller, TLS, and persistent storage or external PostgreSQL. The Starter plan costs $249 a month; Standard costs $799 a month, while Enterprise pricing is custom. SaaS-only deployment requires public network access and stores credentials and secrets in Mission Control Cloud, which the documentation does not recommend for production.

Who it suits

Mission Control suits development and operations teams needing infrastructure discovery, health checks, cataloging, and self-service workflows. Teams should be comfortable with Kubernetes-based self-hosting or evaluate the SaaS caveat carefully.

Good to know, and what to watch

  • Infrastructure and application catalog
  • Multiple health-check types
  • Webhook-triggered playbooks
  • Kubernetes and cloud integrations
  • Free trial available
  • No free plan
  • Self-hosting has Kubernetes requirements
  • SaaS-only deployment not recommended for production
  • Starter plan costs $249 a month

Enterprise

—

Starter

$249/mo

Standard

$799/mo

The verdict

Mission Control combines cataloging, health checks, integrations, and automated playbooks for internal platform work. Its deployment choices and documented requirements should be weighed against the team’s operating model.

What the maker publishes

Catalog
Its catalog automatically discovers, transforms, and tracks infrastructure, applications, and configuration across environments. source
Deployment
The product offers self-hosted, SaaS, and hybrid deployment models, and the maker describes it as self-hosted first. source
Health checks
Health checks include synthetic, passive, infrastructure, and integration checks across services, applications, and infrastructure. source
Integrations
Documented integrations include Kubernetes, AWS, Azure, GitHub, Azure DevOps, Prometheus, Datadog, Dynatrace, CloudWatch, and Elasticsearch. source
Limitations
The overview says Mission Control may not suit teams that prefer ClickOps, are mostly serverless, or already have dedicated full-stack platform engineers. source
Playbooks
Reusable playbooks can be triggered by users, events, or webhooks to automate workflows and support developer self-service. source
Pricing and trial
The pricing page lists a Start Free Trial option but does not state the trial duration. source
Purpose
Mission Control is an internal developer platform designed to improve developer productivity and operational resilience. source
SaaS deployment caveat
The documentation says SaaS-only deployment requires public network access to infrastructure and stores credentials and secrets in Mission Control Cloud, so it is not recommended for production. source
Secret handling
The security documentation says secrets are generated at install time where possible and saved to Kubernetes Secrets, and recommends role-based IAM identity where possible. source
Security
The security documentation lists CodeQL scanning, merge-blocking tests, branch protection, Dependabot, OpenSSF Scorecards, and a CI supply-chain runtime scanner in its secure SDLC. source
Self-hosting requirements
The self-hosted guide lists Kubernetes 1.26 or later, an ingress controller, TLS, and persistent storage or an external PostgreSQL database as requirements. source
Support
The docs offer help through CNCF community Slack, GitHub issues, YouTube, and email. source

Checked against the maker's pages on 8 Oct 2026.