Deploy AI-powered data solutions for your clients
Ekaya Engine is an Apache 2.0 open-source MCP Server that your clients deploy behind their own firewall. You bring the domain expertise, integrations, and support. Together you deliver a professional, contained data workspace — without your clients needing to hire a data engineering team.
all data stays inside the client's boundary
no licensing lock-in
full platform from day one
Ekaya is designed with a clean separation between the on-prem engine and optional cloud services. You and your clients control exactly where the boundaries are.
Everything stays on-prem
Full MCP Server with 40+ tools, ontology, schema management, and pre-approved queries. All core functionality.
Databases, query results, ontology metadata, audit logs — nothing leaves the client's network.
Admin controls which AI provider is used. Bring your own keys for OpenAI/Anthropic, use Ollama locally, or license Ekaya's on-prem models.
Optional · Replaceable
OAuth with HTTPS for non-localhost domains. Required for AI clients like ChatGPT and Claude Desktop. Replaceable with your own JWKS-compatible auth provider.
Invitations, roles, and seat management. Relies on email delivery and sign-in flows. Swap with your own identity management.
Stripe-powered billing and application activation. Partners can handle billing themselves or use Ekaya's billing with revenue sharing.
Gives localhost/on-prem servers public accessibility for AI clients. Requires a persistent connection to the Ekaya Service.
Design principle: All communication with the Ekaya Service is initiated by the Engine. The Service cannot call the Engine — it is designed to run on localhost or on-prem.
Your expertise, Ekaya's platform — a complete solution for your clients
Deploy and configure Ekaya Engine on-prem for your clients. Build custom data applications on top of the MCP platform. Provide the ongoing support, training, and domain expertise that turns a database tool into a business solution.
Integrate your tools, data sources, and workflows with Ekaya's MCP Server. Build adapters, connectors, and extensions that expand what Ekaya can do for mutual customers.
Bundle Ekaya with your own solutions and offer a complete package. Revenue sharing is available through Ekaya's billing service, or handle billing entirely on your own.
Ekaya's ontology requires LLM calls, but the admin controls exactly which provider and model is used. This is a critical selling point for clients with strict data governance requirements.
Client uses their own OpenAI or Anthropic API keys. Data is sent to the provider per their terms.
Client runs Ollama or compatible local models. LLM calls stay on-prem alongside the data.
License Ekaya's fine-tuned models for on-prem deployment. Zero external network calls for any operation.
Ekaya Engine is a single binary that accepts SIGINT for graceful shutdown. Bring up the new version, drain the old one — no orchestrator required for basic deployments. For larger installations, it fits naturally into Kubernetes or any container orchestration platform.
All core MCP functionality is in the open-source Ekaya Engine. The only external requirement is publicly-accessible authentication (OAuth requires HTTPS for non-localhost domains). Ekaya provides this via the Ekaya Service, but it is designed to be swapped out — the Engine uses JWTs that can authenticate with any JWKS-compatible provider, including one you or your client operates.
The Engine sends a provisioning request to the Ekaya Service when a project starts, so the Service can return configuration and update its state. When applications are installed, activated, or uninstalled, the Engine calls the Service so it can optionally intervene (e.g., start/stop billing). There is no telemetry collected today. All communication is initiated by the Engine — the Service cannot call the Engine.
The Ekaya Engine is Apache 2.0 open source — your clients keep running it. You would need to replace the authentication provider (swap to your own JWKS endpoint) and any optional Ekaya Service features you were using (user management, billing). The core MCP platform continues to work.
The Ekaya Service is currently offered on a best-effort basis. For partners with specific SLA requirements, reach out to discuss dedicated support arrangements.
Partners get direct access to the Ekaya team via partners@ekaya.ai. We are building out formal support tiers — early partners help shape what those look like.
Get hands-on with the Ekaya Engine today, or reach out to discuss how we can work together to deliver data solutions for your clients.