Enterprise Enabler vs Kubling

Enterprise Enabler 10 is data integration middleware for connecting IT and business users to data held across different sources. Its transformation engine can federate live data from multiple systems and transform it without staging it in a physical or virtual database. A data catalog provides another way to search within the product, and lineage traces a dataset’s origin, destination, formulas, business rules, and intervening steps. Fast Virtualization uses drag and drop to create virtual models for BI reports, web services, and applications. Data masking and obfuscation control partial or full user views; the product page says these features support GDPR compliance, row-level security, and column-level security. Listed relational integrations include Oracle RDBMS, Microsoft SQL Server, IBM DB2, MySQL, and PostgreSQL. Deployment options include on-premise, cloud, hybrid, and a cloud edition designed to run without extra installation and setup. Stone Bond Technologies offers a no-cost trial, with setup instructions sent by email. AWS Marketplace bundles are billed per hour: EE 10 Bundle A is $2.17 a month for 3 data sources, and Bundle B is $8.50 a month for 12.

Kubling gives AI agents and automation a bounded model of live IT and OT state, federated directly from source systems. It defines shared entities, relationships, source ownership, and valid actions so queries and mutations can cross databases, APIs, and infrastructure. Providers translate operations into each source’s native protocol while retaining credentials, source logic, and release cycles; Kubling handles federation, planning, and policy. The OpenAPI provider exposes API operations as relational entities and maps mutations to HTTP operations. Instances can use local providers, federate other Kubling instances, or do both, with no central instance required. Providers are independent services behind a public gRPC contract and can be written in any gRPC-supported language. The catalog lists Cassandra, Kubernetes, OpenAPI, Redis, and an in-memory provider. The provider protocol, Go SDK, and official providers are open source, but the engine is not. Quickstart requires Git, Docker Engine, and Docker Compose v2. Provider APIs are pre-1.0; exact versions are recommended.