- Home
- Data Virtualization Software
- Kubling
Kubling
What it is
Kubling gives AI agents and automation a bounded model of live IT and OT state, drawing information directly from its source systems. It defines shared entities, relationships, ownership, and permitted actions so queries and mutations can span databases, APIs, and infrastructure. Providers translate each operation into the source’s native protocol while retaining their own credentials, source logic, and release cycle; Kubling handles federation, planning, and policy. The OpenAPI provider exposes API operations as relational entities and maps changes back to HTTP operations. Instances may use local providers, federate other Kubling instances, or combine both, and no central instance is required. Providers are independent services behind a public gRPC contract and can be written in any language supporting gRPC. The catalog lists Cassandra, Kubernetes, OpenAPI, Redis, and an in-memory reference provider. The provider protocol, Go SDK, and official providers are open source, but the engine is not. Kubling presents use cases in data center, IT and platform, and industrial operations. Its quickstart uses Docker Compose with Kubling Studio and requires Git, Docker Engine, and Docker Compose v2.
For and against
For
- Federates databases, APIs, and infrastructure
- No central instance is required
- Providers use a public gRPC contract
- OpenAPI operations become relational entities
- Supports SQL, gRPC, and native protocols
Against
- The engine itself is not open source
- Provider APIs and releases are pre-1.0
- Quickstart requires Git and Docker tools
- Production deployments should pin exact versions
The verdict
Kubling provides a federated operational layer for agents, with provider-owned source connections and explicit policies. Its open provider ecosystem and hybrid deployment model come with pre-1.0 integration maturity and a non-open engine.
Who it suits
Kubling suits teams building agent-driven operations across IT, platform, data center, or industrial systems. It is intended for deployments that need federated providers and explicit operational boundaries.
On the record
- Authentication
- Kubling does not have an internal IAM mechanism and relies on external systems for authentication, authorization, and role reading.docs.kubling.com · read 3 Oct 2026
- Cross-source operations
- Queries and mutations can cross databases, APIs and infrastructure, with providers translating operations into each source’s native protocol.kubling.com · read 2 Oct 2026
- Deployment
- Instances can use local providers, federate other Kubling instances, or both; the site says no central instance is required.kubling.com · read 3 Oct 2026
- Federated queries
- Queries and mutations can cross databases, APIs, and infrastructure, with providers translating operations to each source's native protocol.kubling.com · read 3 Oct 2026
- Integration maturity
- The provider catalog says provider APIs and releases are pre-1.0 and recommends pinning exact image versions and reviewing compatibility notes before upgrades.docs.kubling.com · read 3 Oct 2026
- Integrations
- The provider catalog lists Cassandra, Kubernetes, OpenAPI, and Redis integrations, plus an in-memory reference provider.docs.kubling.com · read 3 Oct 2026
- Intended users
- The site describes use for data center, IT and platform, and industrial operations teams.kubling.com · read 3 Oct 2026
- OpenAPI integration
- The OpenAPI provider exposes API operations as relational entities and maps mutations back to the API’s HTTP operations.kubling.com · read 2 Oct 2026
- Open source boundary
- The provider protocol, Go SDK, and official providers are open source, while the engine is not.kubling.com · read 3 Oct 2026
- Operational model
- The model makes entities, relationships, source ownership, policies, capabilities, and valid actions explicit.kubling.com · read 3 Oct 2026
- Production versioning
- The quickstart recommends pinning exact Kubling and provider versions in production deployments.docs.kubling.com · read 3 Oct 2026
- Provider architecture
- Providers are independent services behind a public gRPC contract and can use any language that supports gRPC.kubling.com · read 3 Oct 2026
- Provider development
- Providers are independent services behind a public gRPC contract, and teams can implement them in any language that supports gRPC.kubling.com · read 2 Oct 2026
- Purpose
- Kubling provides AI agents and automation with a bounded model of live IT and OT state, federated directly from source systems.kubling.com · read 3 Oct 2026
- Quickstart
- The documented quickstart runs Kubling, Kubling Studio, and an in-memory provider in Docker Compose and requires Git, Docker Engine, and Docker Compose v2.docs.kubling.com · read 3 Oct 2026
- Quickstart requirements
- The documented quickstart requires Git, Docker Engine and Docker Compose v2.docs.kubling.com · read 2 Oct 2026
- Quickstart scope
- The quickstart runs Kubling, Kubling Studio and the official In-memory provider as a disposable Docker Compose project.docs.kubling.com · read 2 Oct 2026
- Security boundary
- Kubling’s agent security documentation says runtime connection credentials authenticate the Kubling-to-runtime channel and do not grant VDB or source access.docs.kubling.com · read 2 Oct 2026
