Data Services Blueprints
Every team needs data infrastructure. Almost nobody wants to operate it from scratch. The Data Services family gives you streaming, databases, caching, governance, and recovery as platform services — deployed through GitOps, secured by policy, and operated like the rest of your stack.
openCenter builds a narrow, operator-backed data services portfolio around services that fit its strengths: GitOps lifecycle management, opinionated blueprints, security hardening, air-gap packaging, multi-cloud portability, and managed day-2 operations. The first product is openCenter Managed Kafka, with PostgreSQL following next.
Strategy Principles
Individual data tools are easy to install and hard to operate. The Data Services family treats them as a cohesive layer of the platform with shared principles:
Blueprint repeatability
Versioned, supportable blueprints with limited topology choices.
Day-2 operability
Clear runbooks over feature breadth. Smaller service with clear operations.
Security by default
TLS, auth, secrets handling, image provenance, and policy controls built in.
Air-gap viability
Mirrorable, patchable, and operable without live internet dependencies.
Operator maturity
No fragile operators or unstable APIs. Production-ready only.
Shared responsibility
openCenter owns platform and operations; customers own app behavior and data.
Limited optionality
Standardized topologies, plans, access patterns, and maintenance models.
Commercial clarity
Attachable day-2 revenue and clear support boundaries.
Domain Blueprints
Event streaming as a platform service. Apache Kafka with Strimzi operator, secure-by-default deployment, GitOps lifecycle management, and integrated observability. First GA product: openCenter Managed Kafka.
Managed PostgreSQL coming Q2-Q3 2026. Operator-backed lifecycle management with backup, restore, failover, and upgrade workflows. High demand and strong second portfolio anchor.
Schema registry and governance capabilities as Kafka add-ons. Planned for Q4 2026 after Kafka operating model stabilizes. Not a standalone first product.
Narrow CDC add-ons for PostgreSQL-first patterns. Planned for Q1 2027 after Kafka and PostgreSQL are stable. Constrained scope to avoid open-ended support risk.
Need a data service we have not listed?
Tell us what you are running. If it belongs on the platform, we will build the blueprint.
Talk to Us