We use cookies to understand how you use our site and improve your experience. Cookie policy
Last updated:
Common questions about Palette, answered directly.
Palette is the shared context layer for organizations using AI. It connects to your tools, talks to your people, and maintains a living context map of your organization, so your team stays aligned and your AI tools have the context they need.
Teams actively implementing AI tools like Claude and ChatGPT that are hitting the context wall. Typically 30 to 250 people, moving fast, using tools like Slack, Jira, Linear, GitHub, and Notion. If every AI session starts with re-explaining your company, Palette is for you.
Your AI tools are only as good as the context they start with. Without Palette, every session begins from zero. With Palette, your AI tools know your org, your team knows what's happening, and nobody had to write a status report to make it work.
Connect your tools. Palette's signal engine interprets events into meaningful context and builds a living map of your org. Your team reads it as plain English. Your AI tools read it via MCP. See How Palette Works for the full picture.
Palette only ingests the channels, projects, and tools you explicitly connect. Nothing is scraped or accessed without your permission. You control what's in, what's out, and you can disconnect anything at any time. Data processing is transparent.
Every claim in your context is confidence-scored and traced back to its source. Palette tells you when it's not sure. Your team validates context through lightweight check-ins, and you can correct anything instantly. Your wiki says what you wish were true. Palette reflects what's actually happening, and tells you when it's uncertain.
Dashboards show you charts and wait for you to look. They go stale between refreshes. Palette is a living context layer that updates itself, serves both humans and AI tools, and flags when something is uncertain or outdated. It works for you even when you're not looking at it.
Wikis capture intent. Palette captures reality. A wiki goes stale because someone has to manually maintain it. Palette stays current because it reads from your tools and confirms with your team. Both are useful, they just solve different problems.
Slack, Jira, Linear, GitHub, Notion, and Google Calendar today. More coming based on what design partners need.
Connecting your tools takes a few minutes. Building your initial context map can take up to 30 minutes depending on data volume. You'll see value the same day.
Early access with a direct line to the team. Your input shapes the product. We ask you to connect a few tools, use Palette with a small team, and share honest feedback. You get early access and close support. We get real-world signal.
You can — but then your AI only sees what you see. Your Slack channels, your repos, your docs. When every team connects their tools to Palette, your AI gets context from across the whole org — teams, channels, and projects you're not in, because those teams opted in. It's the difference between giving your AI your silo and giving it the company. See MCP for more.
Palette doesn't replace good processes. It makes the context from those processes available everywhere, to every team member and every AI tool you use. Good processes generate valuable context. Palette makes sure that context doesn't stay locked in one tool or one person's head.
Ready to get started? See the Quick Start guide, learn how Palette works, or read about MCP.