Free for you.
Flat-priced for the team.

Start free and solo with the open-source core — forever. When your team needs shared memory, pick a flat tier: seats included, no per-seat billing, no cloud dependency.

Free trialWant to evaluate Palace Server with your team first? Get a no-commitment trial license for any paid plan — set up within one business day.
Start a free trial →
Start here
Free / Open Core
For every solo developer. Local memory for your own agents.
€0
1 developer · unlimited projects

  • MIT open core — free forever
  • Persistent local memory across sessions
  • Works with Cursor, Claude Code & Codex over MCP
  • Runs fully on your machine — no cloud, no telemetry
Start free on GitHub
Growth
For growing teams.
€3,490 / year
€349 / month · up to 30 users

  • Up to 30 developer seats (enforced by license)
  • Everything in Team
  • Flat price — seats included, no per-seat billing
  • Self-serve checkout and billing portal
Enterprise
For larger companies, regulated environments, and custom rollouts.
Custom
from €8,000+/year · custom monthly

  • Custom seat counts beyond 30
  • Everything in Growth
  • SLA and priority support
  • Custom contract terms
  • Custom quotes
Contact sales

Common questions

Can I use Palace for free, as a solo developer?+
Yes. palace-rs — the open-source core — is MIT-licensed and free forever. Install it, point Cursor, Claude Code, or Codex at it over MCP, and your agent gets persistent local memory across sessions. No account, no cloud, no payment. Palace Server (paid) is only needed when you want to share that memory across a team.
Do I need a whole team to benefit?+
No. Solo, the win is immediate: your agent stops forgetting your decisions, conventions, and fixes every session. Teams add a second win — shared recall, so one developer's solved problem becomes every developer's answer.
How is Palace Server different from palace-rs?+
palace-rs is a local-first crate for individual developers — memory lives on your machine. Palace Server adds a shared layer: one deployment your whole team connects to, so memory and context flow between teammates. It's built on palace-rs internally.
Does any data leave our network?+
No. Palace Server runs entirely on your infrastructure. Embeddings are computed locally with ONNX Runtime. The license is verified cryptographically on your server — fully offline by default, with an optional online revalidation you can enable to roll the expiry forward automatically. There is no telemetry, no logging to external services, and no outbound traffic required.
Which AI coding tools does it support?+
Any tool that supports MCP (Model Context Protocol). That includes Cursor, Claude Code, Codex, and Claude Desktop. The server exposes all palace_* MCP tools over the network — developers point their local MCP config at the server and nothing else needs to change.
How does licensing work offline / air-gapped?+
Licenses are Ed25519-signed key strings verified locally — no network connection required after you set PALACE_LICENSE_KEY. The signed payload contains your seat count and expiry date and is verified cryptographically on every server start.
Can I run multiple Palace Server instances?+
Licensing is based on developer seats, not process counts. You can design your self-hosted deployment around your infrastructure needs; for separate environments, high availability, or larger rollouts, contact us so the subscription and support scope match the setup.
What happens if I cancel my subscription?+
The server continues running until the license expiry date embedded in the key. You can export all drawers and knowledge graph entries as standard JSON at any time. No lock-in.