> partner.build()

Deploy AI-powered data solutions for your clients

Build with Ekaya

on-prem, open-source, yours to extend

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.

100%

On-Prem

all data stays inside the client's boundary

Apache 2.0

Open Source

no licensing lock-in

40+

MCP Tools

full platform from day one


Clear Architecture Boundaries

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.

Client's Infrastructure

Everything stays on-prem

  • Ekaya Engine

    Full MCP Server with 40+ tools, ontology, schema management, and pre-approved queries. All core functionality.

  • All Data

    Databases, query results, ontology metadata, audit logs — nothing leaves the client's network.

  • LLM Calls

    Admin controls which AI provider is used. Bring your own keys for OpenAI/Anthropic, use Ollama locally, or license Ekaya's on-prem models.

Ekaya Service

Optional · Replaceable

  • Authentication & SSO

    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.

  • User Management

    Replaceable

    Invitations, roles, and seat management. Relies on email delivery and sign-in flows. Swap with your own identity management.

  • Billing & Activation

    Replaceable

    Stripe-powered billing and application activation. Partners can handle billing themselves or use Ekaya's billing with revenue sharing.

  • MCP Tunnel

    Under Development

    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.

How Partners Work with Ekaya

Your expertise, Ekaya's platform — a complete solution for your clients

Systems Integrators

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.

  • Full on-prem deployment — no cloud dependency required
  • Swap authentication to your own IdP or your client's SSO
  • Build and deploy custom MCP applications for specific industries

Technology Partners

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.

  • 40+ MCP tools provide a rich integration surface
  • Ontology and schema APIs for metadata-driven integrations
  • Joint solution positioning with shared customers

Resellers

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.

  • Flexible pricing — use Ekaya billing with rev-share or bring your own
  • White-label deployments with your own auth and branding
  • Self-service product — no enterprise sales cycle required
AI Models

Your client's AI, their rules

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.

  • Bring your own keys — Use OpenAI, Anthropic, or any compatible API with the client's own credentials
  • Run locally with Ollama — Zero data leaving the infrastructure, ideal for air-gapped environments
  • License Ekaya's fine-tuned models — Vetted and optimized for Ekaya Engine, available for on-prem deployment so no data crosses any boundary

Data Boundary Options

Standard

Client uses their own OpenAI or Anthropic API keys. Data is sent to the provider per their terms.

Enhanced

Client runs Ollama or compatible local models. LLM calls stay on-prem alongside the data.

Air-Gapped

License Ekaya's fine-tuned models for on-prem deployment. Zero external network calls for any operation.

rolling-upgrade
# Zero-downtime upgrade process
$ ekaya-engine start --port 8081
✓ New instance ready on :8081
# Switch traffic to new instance
$ kill -SIGINT $OLD_PID
Draining active connections...
3 requests remaining...
0 requests remaining...
✓ Old instance shut down gracefully
# Upgrade complete, zero dropped requests
Operations

Simple upgrades, graceful operations

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.

  • Rolling upgrades with graceful connection draining
  • Single binary — minimal operational surface area
  • Works standalone or in containerized environments

Pricing & Revenue Sharing

Ekaya is a self-service product. Your clients can get started on standard pricing, or you can handle billing entirely on your own and layer your own services on top. Revenue sharing is available for partners who use Ekaya's billing service.

Frequently Asked Questions

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.

Ready to build with Ekaya?

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.