Stop re-explaining your business to AI. Castles gives every model structured, permissioned access to your knowledge — at a fraction of the tokens.



You explain your brand voice. Your org structure. Your compliance rules. Then the session ends, and the next one starts from zero. This is context amnesia.
No six-figure enterprise search contract. No data engineering team to maintain a RAG pipeline.
| Pasting into prompts |
Enterprise search |
Castles | |
|---|---|---|---|
| Authored for AI | |||
| Native MCP for Claude, Cursor, ChatGPT | |||
| Permissioned access | |||
| No infra to set up | |||
| Stays current automatically | |||
| Fits teams of 20–200 | |||
| Priced for startups |
Every castle is a structured floor plan of a knowledge domain. Rooms hold the content. A sitemap gives any LLM a map of the entire layout.
Define a knowledge domain: "Product", "Legal", "Brand". The castle is the outer wall on the floor plan. Everything inside it belongs to one structured territory.
Each room holds a category of knowledge with its own access tier. "Brand Voice" is public. "Board Minutes" is confidential. Permissions are walls, not suggestions.
The documents, guidelines, and structured data that live inside each room. Add them manually or let AI import and organise them for you.
Castles auto-generates a compact index (~200 tokens) of the entire floor plan. Any LLM reads the map, navigates to the right room, and fetches only what it needs.
Castles connects to any LLM through the Model Context Protocol. Your teams keep using the AI tools they already have (Claude, GPT-4, Gemini) and every session silently arrives with the knowledge it needs.
50 people using 5 different AI tools all get the same structured knowledge. No more off-brand outputs because someone forgot to paste the style guide into the prompt.
Four access tiers enforced at the database level. Compliance docs stay behind the doors they belong behind. No model ever sees knowledge it shouldn't.
Every knowledge retrieval is logged with who, what, and when. Answer the audit question your board will ask: "What did our AI actually use to generate that?"
Standard MCP protocol means you connect once and it works with any model, today and tomorrow. Switch providers without touching your knowledge layer.
The dashboard is built for business users, not engineers. Your brand team updates brand voice. Your legal team manages compliance. No tickets required.
The sitemap is ~200 tokens regardless of how large your knowledge base gets. Add 10,000 artefacts and the per-session cost doesn't change.
Castles runs in the background. No new tools to learn, no workflow changes. Every AI conversation just starts smarter.
Castles works wherever your team works. Brand guidelines in Gemini. Sales intel in ChatGPT. Product specs in Claude Code. Onboarding processes in Copilot. Same structured knowledge, zero re-entry.
Marketing rewrites headlines in Gemini — Castles delivers the brand voice guide automatically.
Structure knowledge, set access tiers, and monitor usage from one dashboard. No code required. Your admin defines the rules, your team gets the context.
Every feature serves two audiences: the business leader who needs control and the developer who needs a clean API.
Every session that starts from scratch compounds the problem: wasted tokens, inconsistent outputs, and knowledge that never sticks. Castles is the cure.
Start small, scale when you need to. No surprises.