Explore Palace

Understand it.
Evaluate it. Put it to work.

A clear path from the first question to your first shared memory.

GUIDE

Start with a pilot

Deploy a server, connect your agents, and evaluate a single project.

Read the guide
FOR ENGINEERING LEADS

Make the technical case

Review identity, isolation, network boundaries, and operational requirements.

Open evaluation
INTEGRATIONS

Keep your favorite tools

Connect Cursor, Claude Code, Codex, and other MCP clients.

Explore connections
OPEN SOURCE

Inspect the engine

Learn about palace-rs and the context behind its retrieval benchmark.

Explore the engine
A PRACTICAL COMPARISON

Choose the memory layer

Understand when built-in memory, a vector database, or a shared service fits.

Compare approaches
HELP

Find your next step

Setup, permissions, backups, and answers to common deployment issues.

Find a guide
HOW IT WORKS

From one laptop to the team

Start locally with palace-rs, then point every developer at one server.

See the steps
THE CASE

Why shared memory

What changes when every agent on the team can reach the same context.

Read the case
ANSWERS

Common questions

Licensing, offline use, supported tools, and what happens if you cancel.

Open the FAQ
Put your knowledge to work

Give your next session
a head start.

Start your team trial

60 days · 10 seats · No credit card