// Example: Core's auto-wiring picks up connection intent and resolves it
type Connection struct { SourceService string `json:"source"` TargetService string `json:"target"` SourcePort int `json:"sourcePort"` TargetPort int `json:"targetPort"`
}
// Core resolves this into env vars, DNS entries, and NetworkPolicies automatically
// Example: Core's auto-wiring picks up connection intent and resolves it
type Connection struct { SourceService string `json:"source"` TargetService string `json:"target"` SourcePort int `json:"sourcePort"` TargetPort int `json:"targetPort"`
}
// Core resolves this into env vars, DNS entries, and NetworkPolicies automatically
// Example: Core's auto-wiring picks up connection intent and resolves it
type Connection struct { SourceService string `json:"source"` TargetService string `json:"target"` SourcePort int `json:"sourcePort"` TargetPort int `json:"targetPort"`
}
// Core resolves this into env vars, DNS entries, and NetworkPolicies automatically
# Initialize a KubeOrch project
orchcli init # Start all services (supports hot reload)
orchcli start # Fork and contribute to core or UI
orchcli init --fork-core
orchcli init --fork-ui
# Initialize a KubeOrch project
orchcli init # Start all services (supports hot reload)
orchcli start # Fork and contribute to core or UI
orchcli init --fork-core
orchcli init --fork-ui
# Initialize a KubeOrch project
orchcli init # Start all services (supports hot reload)
orchcli start # Fork and contribute to core or UI
orchcli init --fork-core
orchcli init --fork-ui
curl -sfL https://raw.githubusercontent.com/KubeOrch/cli/main/install.sh | sh
curl -sfL https://raw.githubusercontent.com/KubeOrch/cli/main/install.sh | sh
curl -sfL https://raw.githubusercontent.com/KubeOrch/cli/main/install.sh | sh
npm install -g @kubeorch/cli
npm install -g @kubeorch/cli
npm install -g @kubeorch/cli
{ "name": "postgresql", "ports": [ { "port": 5432, "type": "postgres", "envVarTemplate": "{{TARGET_NAME}}_DATABASE_URL", "valueTemplate": "postgresql://{{USER}}:{{PASSWORD}}@{{SERVICE_DNS}}:5432/{{DB_NAME}}" } ]
}
{ "name": "postgresql", "ports": [ { "port": 5432, "type": "postgres", "envVarTemplate": "{{TARGET_NAME}}_DATABASE_URL", "valueTemplate": "postgresql://{{USER}}:{{PASSWORD}}@{{SERVICE_DNS}}:5432/{{DB_NAME}}" } ]
}
{ "name": "postgresql", "ports": [ { "port": 5432, "type": "postgres", "envVarTemplate": "{{TARGET_NAME}}_DATABASE_URL", "valueTemplate": "postgresql://{{USER}}:{{PASSWORD}}@{{SERVICE_DNS}}:5432/{{DB_NAME}}" } ]
}
# Install the CLI
curl -sfL https://raw.githubusercontent.com/KubeOrch/cli/main/install.sh | sh # Initialize a new project
orchcli init # Start everything
orchcli start
# Install the CLI
curl -sfL https://raw.githubusercontent.com/KubeOrch/cli/main/install.sh | sh # Initialize a new project
orchcli init # Start everything
orchcli start
# Install the CLI
curl -sfL https://raw.githubusercontent.com/KubeOrch/cli/main/install.sh | sh # Initialize a new project
orchcli init # Start everything
orchcli start
git clone https://github.com/KubeOrch/core.git
cd core
go mod tidy
go run main.go
git clone https://github.com/KubeOrch/core.git
cd core
go mod tidy
go run main.go
git clone https://github.com/KubeOrch/core.git
cd core
go mod tidy
go run main.go - A Deployment manifest for your app
- A Service to expose it
- A Deployment + PersistentVolumeClaim for Postgres
- A Service for Postgres
- A Secret for credentials
- A Deployment for Redis
- A Service for Redis
- A ConfigMap for environment variables
- An Ingress with TLS config
- NetworkPolicies if you care about security - Drag services onto a canvas (Postgres, Redis, Kafka, your app — 150+ components)
- Connect them by drawing lines between ports
- Deploy — KubeOrch generates the manifests, resolves dependencies, and applies them to your cluster - JSON-to-YAML transformation — your visual design is stored as a JSON graph internally; Core converts it to production-ready Kubernetes manifests at deploy time
- Automatic connection resolution — when you draw a line from your app to Postgres, Core figures out the right DATABASE_URL env var, the right service DNS name, the right port — without you specifying any of it
- Nixpacks integration — point Core at a GitHub repo and it builds a container automatically, no Dockerfile needed
- Service mesh support — Istio, ingress controllers, and load balancers are first-class citizens
- Real-time streaming — WebSocket-based log and metrics streaming from all running containers - React Flow for the drag-and-drop workflow designer
- Next.js 15 with TypeScript
- shadcn/ui + Tailwind CSS v4 for the component library
- Zustand for state management
- WebSocket for real-time log streaming - What environment variable should carry the connection string?
- What DNS name should the dependent service use?
- What port should be exposed?
- Does this connection need a NetworkPolicy?
- Does it need a Secret, or is the connection string safe to put in a ConfigMap? - Contributor ladder (from contributor → member → maintainer)
- Governance policy
- API stability policy
- RFC/proposal process in the community repo - KubeOrch/core — Go backend, orchestration engine
- KubeOrch/ui — Next.js visual canvas
- KubeOrch/cli — OrchCLI developer tool
- KubeOrch/community — Governance, roadmap, RFCs
- KubeOrch/docs — Full documentation - GitOps integration — sync your visual design to a Git repo and trigger deploys on push
- Multi-cluster support — manage workloads across multiple clusters from one canvas
- Plugin SDK — let the community build and publish custom components to the marketplace
