One license.
One contract.
The complete Karate Labs stack.

The Karate framework is MIT-licensed and free forever — that doesn't change. Karate Enterprise is the commercial edition that adds the async protocol pack (Kafka, gRPC, WebSocket runtime), the IDE Enterprise tier, Karate Agent for AI verification, API Coverage across OpenAPI, gRPC, GraphQL and Kafka, and engineering-grade support, all under a single contract. Open source remains the foundation; Enterprise adds the components that procurement, security, and operations teams require.

Pricing is custom based on which components you need, team size, environment count, and support tier. IDE plugins are priced per user, the async runtime is priced per environment, and Karate Agent is priced by execution volume. We consolidate all components into a single annual agreement so you have one renewal, one PO, and one support relationship. See the pricing page for IDE seat costs.

Yes. Every component is self-hosted. Karate Agent runs in Docker on your infrastructure; pair it with a local LLM via Ollama and the entire pipeline — browser, agent, model — runs inside your network with zero outbound calls. Used in production by financial services, insurance, and healthcare customers with strict data-residency requirements.

A dedicated Slack channel with Karate Labs engineers, response SLAs tied to your support tier, an escalation path for production incidents, and access to the Karate Labs roadmap. Enterprise customers also get architecture review, deployment support, and hands-on assistance during PoC and rollout.

IDE Enterprise licenses cover individual developers writing and debugging tests locally. Runtime licenses cover execution of async (Kafka, gRPC, WebSocket) tests in shared environments such as CI/CD pipelines. Most enterprise customers buy both: IDE seats for the team plus runtime licenses for their pipelines. We model the bundle for you during scoping.

Yes. Many teams start with the IDE Enterprise tier or the async pack, then add Karate Agent once they're ready to introduce AI verification. Components can be added at any time — pricing is prorated to your contract term, and the support relationship carries across the whole stack.

Via SAML 2.0 or OIDC against any major identity provider — Azure AD / Entra ID, Okta, Ping, Auth0, Google Workspace. Role-based access control determines who can run tests, view reports, and manage configurations. No per-seat installs; teams share a single deployment governed by your IdP.

Three steps. First, evaluate using the public Enterprise Evaluation guide — 95 answers to the questions technical and procurement teams typically ask. Second, run a scoped 30-day PoC with engineering support and weekly check-ins. Third, sign an annual agreement covering the components and seats you've validated. Most evaluations close in 4 to 8 weeks.