Kubling

Input—per 1M tokens

Output—per 1M tokens

Context—tokens

WeightsClosed

About

Kubling is ranked #13 of 23 in data virtualization software on Inferse. It runs on API, Linux, Self-hosted, Web.

Compared on data virtualization software

Deployment model: hybridkubling.com
Semantic layer: Yeskubling.com
Access protocols: SQL, gRPC, native protocol, PostgreSQL wire protocolkubling.com
REST API access: Yeskubling.com
Query acceleration: Yeskubling.com

Facts

Purpose: Kubling gives AI agents and automation a bounded model of live IT and OT state, federated directly from its sources.kubling.com · 2 Oct 2026
Operational model: It makes shared entities, relationships, source ownership and valid actions explicit for agents.kubling.com · 2 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 · 2 Oct 2026
Source ownership: Providers retain their credentials, source logic and release cycle while Kubling handles federation, planning and policy.kubling.com · 2 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 · 2 Oct 2026
Deployment: Instances can use local providers, federate other Kubling instances, or do both; the site says no central instance is required.kubling.com · 2 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 · 2 Oct 2026
Open source boundary: The provider protocol, Go SDK and official providers are open source; the engine is not.kubling.com · 2 Oct 2026
Intended users: The site presents use cases for data center operations, IT and platform operations, and industrial operations.kubling.com · 2 Oct 2026
Quickstart requirements: The documented quickstart requires Git, Docker Engine and Docker Compose v2.docs.kubling.com · 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 · 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 · 2 Oct 2026
Authentication: The RBAC documentation says Kubling relies on external systems for authentication and authorization and has no internal IAM mechanism.docs.kubling.com · 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 · 3 Oct 2026
Operational model: The model makes entities, relationships, source ownership, policies, capabilities, and valid actions explicit.kubling.com · 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 · 3 Oct 2026
Deployment: Instances can use local providers, federate other Kubling instances, or both; the site says no central instance is required.kubling.com · 3 Oct 2026
Provider architecture: Providers are independent services behind a public gRPC contract and can use any language that supports gRPC.kubling.com · 3 Oct 2026
Open source boundary: The provider protocol, Go SDK, and official providers are open source, while the engine is not.kubling.com · 3 Oct 2026
Integrations: The provider catalog lists Cassandra, Kubernetes, OpenAPI, and Redis integrations, plus an in-memory reference provider.docs.kubling.com · 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 · 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 · 3 Oct 2026
Production versioning: The quickstart recommends pinning exact Kubling and provider versions in production deployments.docs.kubling.com · 3 Oct 2026
Authentication: Kubling does not have an internal IAM mechanism and relies on external systems for authentication, authorization, and role reading.docs.kubling.com · 3 Oct 2026
Transport security: Kubling's HTTP endpoints can be secured with TLS by configuring a certificate at the application level.docs.kubling.com · 3 Oct 2026
Intended users: The site describes use for data center, IT and platform, and industrial operations teams.kubling.com · 3 Oct 2026