The licence, updates and support
From$6,000a year, per install
The same price every year. Every new release, installed for you, and email support with a reply within one working day.
Enterprise
Context Engine on your own server.
One memory for your AI agents and your team, on your own server, for your organisation alone. Relote installs it and runs it for you.
If you stop paying
Yours to keep
The installed version keeps running, with everything in it. Only new releases and support stop.
What you get
Your data, on your own server
One install serves one organisation: yours. No shared database, no index shared with other customers, nowhere your content mixes with anyone else’s.
Keeps running if you stop paying
If you stop paying, the version you have keeps running, with everything in it; only new releases and support stop.
Installed and run by Relote
We install it on your server, then keep it running, monitored, backed up and upgraded, through Relote Cloud. The account we use cannot read your content: file permissions keep it out.
Works with the AI tools you use
Claude on the web and in the desktop app connects by signing in (OAuth 2.1). Claude Code, Cursor and the agents you build connect over MCP with a key. What a signed-in tool may do follows the person’s role.
Roles and an audit log
Viewer, Author and Admin, by invitation only. Every request a key makes to the API is recorded: which key, what it was allowed to do and where it went. Admins read the log.
Markdown you own, versioned in git
What the engine knows is plain Markdown on your disk, and every change is a commit, so you can see any earlier version. Push it to a git remote you choose.
Backups, health and metrics
Encrypted backups that cannot be read without their recovery key, so storing them never exposes your content. A health check, Prometheus metrics and a version probe for your monitoring.
Connected apps
Connect the apps your team uses through Composio, one at a time, each authorised by you. When someone asks the engine, a viewer gets read-only tools; authors and admins get the rest.
Single sign-on for your own apps
The engine is an OpenID Connect identity provider. Register an app, and your team signs in to it with their engine accounts.
What you bring
- A server. A virtual server or a container for the install, with Postgres 16 and pgvector. Relote sets it up.
- A Claude subscription. The engine’s thinking runs on Claude Code, signed in to your own subscription.
- An OpenAI API key. Used for search embeddings only.
Questions about Enterprise
What does the yearly price cover?
The licence, every new release, installed for you, and email support, with a reply within one working day. It starts from $6,000 a year per install and stays the same every year.
What happens if we stop paying?
The version you have keeps running, on your server, with everything in it. New releases and support stop.
Can Relote read our data?
Not in the course of running it. The account Relote operates with can start and stop the engine, read logs scrubbed of secrets, run health checks, back it up, restore and upgrade it, but cannot read your content, its history, its search index or its secrets. If a problem can only be fixed by looking at content, you authorise a window in writing; it expires on its own, the session is recorded and the recording is yours.
What leaves our server?
The model calls: to Anthropic on your Claude subscription, and to OpenAI for search embeddings. Beyond those, only what your install is set up to use, such as a git remote you push a copy of your content to, or connected apps. There is no product telemetry. Relote Cloud, which runs the install for you, sees health checks and encrypted backups, never readable content.
Can people sign in with Okta or Entra ID?
No. People sign in to the engine with an email and password it manages, by invitation. Single sign-on works the other way: the engine is the OpenID Connect identity provider your own apps sign people in with.
Is it the same as the hosted app?
It is the same idea, one memory for your AI agents and your team, as its own product: one engine per install, on your server, with its own screens. The hosted plans and their agent limits do not apply to it.
Put it on your own server.
Tell us about your team and where it should run, and we will come back with what the install needs.