Welcome to Kubling
Kubling is an open-source, SQL-based federation engine for reasoning over and safely operating live state across heterogeneous systems, platforms and environments.
It runs close to the systems that own the data and exposes them through one strongly typed, schema-first model. Kubling does not require a central ingestion pipeline or copy operational state into a warehouse before it can be queried.
The answer is never in one system
“Can we deploy this change safely?”
The running state may be in Kubernetes, ownership in a service catalog, open work in a task system and customer impact in a database. None of those systems has the complete answer, and their state keeps changing while the decision is being made.
Modern operations are no longer limited by lack of visibility. They are limited by the difficulty of evaluating and coordinating decisions across systems that were never designed to work as one.
Teams usually bridge that gap with scripts that call several APIs, normalize identifiers, join responses in memory and then attempt a sequence of writes. Those scripts quickly become critical infrastructure: difficult to test, audit, reuse or compensate when the fourth system fails after the first three have already changed.
One operational model over live systems
Kubling makes operational state explicit and queryable as a whole, so a decision can be evaluated in context instead of inferred from disconnected signals.
SQL acts as the unifying operational language. Providers and data sources translate that model into the operations each remote system can preserve, while Virtual Databases combine their physical schemas into reusable operational views.
Applications can query and join current state across system boundaries, expose controlled operations and coordinate changes with explicit security and transaction semantics. The source systems remain the owners of their data; Kubling does not require moving it into a centralized repository first.
This model is designed for on-premises, cloud, hybrid and edge environments, where locality, responsibility boundaries and system heterogeneity matter.
Built for operational decisions
- deployment and change-safety checks that depend on several systems.
- internal platforms that need one contract over heterogeneous infrastructure.
- investigation and remediation workflows that combine live state.
- hybrid and edge operations where central ingestion is impractical.
- AI agents that need typed, permission-aware reads and actions.
Start here
- Run the Quickstart to understand the local Kubling, provider and Studio workflow.
- Connect an application through gRPC using the public protobuf contract or the official Go SDK.
- Explore Providers to learn how source integrations advertise schemas and capabilities.
- Understand the architecture before designing a production Virtual Database.
- Plan a production deployment when moving beyond a local environment.
What Kubling is not
Kubling is not a data warehouse or a general-purpose analytics platform. It is designed to operate on current system state, with an emphasis on correctness, coordination and explicit operational semantics.