Skip to main content
Docs for Doers

The Secret Sauce,there is no secret sauce. Just Open Source.

openCenter gives engineering teams a repeatable path to stand up Kubernetes and OpenStack with GitOps, security controls, observability, and day-2 operations already in the design. This documentation is built for the people who have to make that real.

GitOps-nativeShip from pull requests

Bootstrap clusters, services, and app delivery from versioned config.

Security-firstPolicies wired in early

Start with hardening, secrets, and observability before the first outage.

Multi-environmentOpenStack, AWS, air-gap

Keep one operational model across the places your workloads actually run.

bootstrap session
$ opencenter init platform
✓ generated cluster configuration
✓ enabled GitOps reconciliation
✓ installed policy + observability stack
→ next: docs/welcome/quickstart
cpu usage
RedpandaRedpanda Icon
GrafanaGrafana Icon
memory usage
GrafanaGrafana Icon
GrafanaGrafana Icon
network - total rx/tx

The goal is not another dashboard screenshot. The goal is faster platform delivery with fewer bespoke scripts, fewer snowflake clusters, and a lot less day-2 drag.

Why This Docs Site Exists

Built for operators, platform teams, and skeptical engineers.

The main site makes the case for openCenter. This landing page should help technical readers get to the part that matters: how the platform is assembled, how it is operated, and how to avoid creating another brittle internal platform.

Bootstrap without guesswork

Move from prerequisites to cluster configuration with opinionated docs that assume you need working infrastructure, not a glossy overview.

Operate through Git, not tribal knowledge

Follow documented workflows for GitOps bootstrap, upgrades, drift control, and application delivery so the platform can survive handoffs.

Treat day-2 as part of day-0

Backups, scaling, lifecycle operations, and troubleshooting are first-class docs sections because production platforms fail there, not in demos.

Bake in security from the start

Use the security, secrets, and air-gap guidance to enforce hardening, access control, policy, and evidence requirements early.

Design for real topology constraints

Reference architectures, provider comparisons, and deployment models help teams make concrete decisions across VMware, OpenStack, AWS, and regulated environments.

Standardize your internal platform

Blueprints, service catalogs, and golden paths give platform teams a way to ship paved roads instead of rebuilding the same stack for every team.

Get Started

Build the first working path

Start with the quickstart, core concepts, and installation flow to get openCenter running with the least ambiguity.

Open docs path
Architect

Plan the platform before you buy pain

Review planning, reference architectures, and provider tradeoffs before the first cluster turns into permanent platform debt.

Open docs path
Ship

Give developers a cleaner golden path

Jump into application deployment, GitOps workflows, and blueprints when the job is enabling teams to ship safely at speed.

Open docs path