Kubling

Kubling is ranked #14 of 22 in data virtualization software on The Geeks Club. It runs on API, Linux, Self-hosted, Web.

Compared on data virtualization software

Deployment model: hybrid
Semantic layer: Yes
Access protocols: SQL, gRPC, native protocol, PostgreSQL wire protocol
REST API access: Yes
Query acceleration: Yes

Best Kubling alternatives

See all 12

9.4 Denodo Platform Free plan

9.2 Starburst Galaxy Free plan

9.1 Query Streams Free plan

8.4 Trino Free plan

8.4 Spice.ai OSS Free plan

8.2 Stardog Free plan

Kubling

Purpose: Kubling gives AI agents and automation a bounded model of live IT and OT state, federated directly from its sources.
Operational model: It makes shared entities, relationships, source ownership and valid actions explicit for agents.
Cross-source operations: Queries and mutations can cross databases, APIs and infrastructure, with providers translating operations into each source’s native protocol.
Source ownership: Providers retain their credentials, source logic and release cycle while Kubling handles federation, planning and policy.
OpenAPI integration: The OpenAPI provider exposes API operations as relational entities and maps mutations back to the API’s HTTP operations.
Deployment: Instances can use local providers, federate other Kubling instances, or do both; the site says no central instance is required.
Provider development: Providers are independent services behind a public gRPC contract, and teams can implement them in any language that supports gRPC.
Open source boundary: The provider protocol, Go SDK and official providers are open source; the engine is not.
Intended users: The site presents use cases for data center operations, IT and platform operations, and industrial operations.
Quickstart requirements: The documented quickstart requires Git, Docker Engine and Docker Compose v2.
Quickstart scope: The quickstart runs Kubling, Kubling Studio and the official In-memory provider as a disposable Docker Compose project.
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.
Authentication: The RBAC documentation says Kubling relies on external systems for authentication and authorization and has no internal IAM mechanism.
Purpose: Kubling provides AI agents and automation with a bounded model of live IT and OT state, federated directly from source systems.

Visit site Alternatives

Where it ranks on The Geeks Club

Best Data Virtualization Software in 2026#14 of 22

Is Kubling yours?

Claim it for free: prove the domain, then correct facts, plans and screenshots. An editor reviews every change.

Claim it free Promote Kubling

Sources

kubling.com· checked 2 Oct 2026
docs.kubling.com/quickstart· checked 2 Oct 2026
docs.kubling.com/agent/security· checked 2 Oct 2026
docs.kubling.com/Security/RBAC· checked 2 Oct 2026
docs.kubling.com/providers/catalog· checked 3 Oct 2026
docs.kubling.com/security/rbac· checked 3 Oct 2026
docs.kubling.com/security/http· checked 3 Oct 2026