// the find
superplanehq/superplane
The open source control plane for platform engineering.
SuperPlane is an event-driven workflow orchestration platform for platform engineering teams — think 'Zapier for DevOps' but self-hosted, with a visual canvas UI and Go backend. It lets you wire together CI/CD pipelines, incident tools, cloud services, and approval gates into DAG-based workflows triggered by webhooks or schedules. Aimed at platform teams tired of stitching together bash scripts and GitHub Actions hacks.
- Genuinely wide integration surface — GitHub, GitLab, PagerDuty, Datadog, AWS, GCP, Azure, LaunchDarkly, etc. — all with both trigger (inbound event) and action (outbound call) sides, which is the hard part most orchestrators skip.
- Migration history is substantial and well-structured (100+ timestamped up/down SQL migrations), suggesting the schema is evolving deliberately rather than being duct-taped together.
- Single-container demo image makes local evaluation realistic in under 5 minutes, which is rare for tools in this category.
- Canvas versioning with change management / approval gates for canvas edits is a thoughtful production concern — workflow drift is a real operational problem this directly addresses.
- Still in alpha with explicitly warned breaking changes, and the migration list shows significant churn (multiple renames, cascade fixes, foreign key corrections) — adopting this in production today means accepting schema migrations as a recurring cost.
- The Cursor AI rules/skills checked into the repo (.cursor/ directory) suggest the codebase is being actively co-written with LLM assistance, which isn't inherently bad but raises questions about consistency and test coverage in newer integrations.
- No clear story for custom/generic integrations — if your internal tool isn't in the supported list, it's unclear how easy it is to add one without forking. The docs link is external and the integration code isn't obviously pluggable from the repo structure.
- RBAC via Casbin with several migration fixups (alter schema, fix index names, rename prefixes) suggests the permission model wasn't fully designed upfront, which can create subtle authorization bugs during upgrades.