README
¶
Superplane
SuperPlane is an AI-native DevOps control plane. Our mission is to build the platform teams use to ship and manage software in the AI era.
Agents are helping us write an order of magnitude more code, while systems have become too complex for human-driven ops alone. We're rethinking DevOps from first principles for the AI era: a single control layer where engineers and agents safely collaborate.
Key Capabilities
- AI-Native Architecture - Built from the ground up for the AI era, enabling seamless collaboration between engineers and AI agents to manage increasingly complex DevOps systems
- Cross-Platform Workflow Orchestration - Connect and coordinate workflows across multiple DevOps tools, platforms, and services from a single interface
- Event-Driven Automation - Build workflows that automatically respond to code pushes, deployments, alerts, and custom triggers
- Visual Workflow Builder - Design and manage complex DevOps processes with an intuitive visual interface and real-time status updates
- Operational Knowledge Centralization - Create living documentation of your DevOps processes that's easy to understand and maintain
Quick Start
The fastest way to try SuperPlane is to run the latest version of the SuperPlane Docker container on your own machine. You'll have a working SuperPlane instance in less than a minute, without provisioning any cloud infrastructure.
docker run --rm -p 3000:3000 -v spdata:/app/data -ti ghcr.io/superplanehq/superplane-demo:stable
Production Installation
For a permanent, production-ready installation, SuperPlane can be deployed on a single host or on Kubernetes. The single-host installation is ideal for smaller deployments and provides automatic SSL certificate management. Kubernetes deployment offers better scalability and high availability for larger teams.
- Single Host Installation - Deploy on AWS EC2, GCP Compute Engine, or other cloud providers
- Kubernetes Installation - Deploy on GKE, EKS, or any Kubernetes cluster
Contributing
Found a bug or have a feature idea? Check our Contributing Guide to get started.
Get In Contact
Directories
¶
| Path | Synopsis |
|---|---|
|
cmd
|
|
|
cli
command
|
|
|
server
command
|
|
|
pkg
|
|
|
protos/applications
Package applications is a reverse proxy.
|
Package applications is a reverse proxy. |
|
protos/blueprints
Package blueprints is a reverse proxy.
|
Package blueprints is a reverse proxy. |
|
protos/components
Package components is a reverse proxy.
|
Package components is a reverse proxy. |
|
protos/groups
Package groups is a reverse proxy.
|
Package groups is a reverse proxy. |
|
protos/integrations
Package integrations is a reverse proxy.
|
Package integrations is a reverse proxy. |
|
protos/me
Package me is a reverse proxy.
|
Package me is a reverse proxy. |
|
protos/organizations
Package organizations is a reverse proxy.
|
Package organizations is a reverse proxy. |
|
protos/roles
Package roles is a reverse proxy.
|
Package roles is a reverse proxy. |
|
protos/secrets
Package secrets is a reverse proxy.
|
Package secrets is a reverse proxy. |
|
protos/triggers
Package triggers is a reverse proxy.
|
Package triggers is a reverse proxy. |
|
protos/users
Package users is a reverse proxy.
|
Package users is a reverse proxy. |
|
protos/widgets
Package widgets is a reverse proxy.
|
Package widgets is a reverse proxy. |
|
protos/workflows
Package workflows is a reverse proxy.
|
Package workflows is a reverse proxy. |
|
retry
Package retry holds a helper function for retrying a task.
|
Package retry holds a helper function for retrying a task. |
|
test
|
|