@@ -20,32 +22,30 @@ import { CalloutCard, DocCard, DocCardGrid, FeatureCard, FeatureGrid } from '@si
icon="mdi:rocket-launch"
/>
-## Why Marmot?
+## Built for agents
-Unlike traditional catalogs that require extensive infrastructure and configuration, Marmot ships as a **single binary** with an intuitive UI, making it easy to deploy and start cataloging in minutes.
+AI agents are only as good as the context they can reach. Through a built-in MCP server and our SDKs, Marmot gives your agents a live, governed map of every asset in your stack: what exists, who owns it, what it means, and how it all connects.
-
-
+
+
+
+## Why Marmot?
+
+Most catalogs were built to help a data team document tables. Marmot is built to feed context to whoever needs it, human or agent, across every kind of asset: services, APIs, queues, topics, brokers, databases, tables and pipelines.
+
+That means agents are first class, not an afterthought. A native MCP server and our SDKs are part of the core, so your agents read the same governed context your team does. And Marmot stays light enough to actually adopt: a single binary backed only by PostgreSQL, with no platform team required.
## Architecture
@@ -55,62 +55,80 @@ Marmot is built entirely in Go with PostgreSQL being the only external dependenc
-## Features
-
-### Search Everything
-
-Find any data asset across your entire organisation in seconds. Combine full-text search with structured queries using metadata filters, boolean logic, and comparison operators.
-
-### Interactive Lineage Visualisation
+## What Marmot stores
-Trace data flows from source to destination with interactive dependency graphs. Understand upstream and downstream dependencies, identify bottlenecks, and analyse impact before making changes.
+Marmot is a context layer, so it stores **metadata about your assets**, not the data inside them. That means schemas, field names and types, ownership, descriptions, tags, lineage and statistics. The rows in your tables, the messages on your topics and the payloads behind your APIs never enter Marmot.
-### Metadata-First Architecture
+Plugins read a source's structure and metadata into PostgreSQL; the data itself never moves. The easiest path is to run it on our platform, isolated per customer and under strict access controls. Need everything to stay within your control? Run Marmot yourself, free or with an enterprise license, in your own cloud on AWS, Google Cloud, Azure, OVHcloud or anywhere else.
-Store rich metadata for any asset type. From tables and topics to APIs and dashboards - if it matters to your data stack, you can catalog it in Marmot.
-
-### Team Collaboration
-
-Assign ownership, document business context, and create glossaries. Keep your entire team aligned with centralised knowledge about your data assets.
-
-### Data Products
-
-Group related assets into logical collections. Use manual assignment for curated bundles or dynamic rules that use the query language to automatically include matching assets as your catalog grows.
+
+
+
+
+
+ + Stop hardcoding context +
++ Why you need a context layer +
++ This is how most agents get data today, and why it doesn't last. A + context layer replaces the hand wired map with one that stays + current. +
+
+ {/* Today */}
+
+
+
+
+
+ {/* With Marmot */}
+
+
+
+ Hardcoded today
+
+
+ -
+ {todayItems.map((item) => (
+
-
+
+
+ + + {item} + +
+ ))}
+
+
+
+
+
+
+
+
+ With Marmot
+
+
+ -
+ {marmotItems.map((item) => (
+
-
+
+
+ + + {item} + +
+ ))}
+
+ You don't move your databases to Marmot. You stop hardcoding the + context around them.{" "} + + See Marmot for agents + +
+
-
-
- Then let your AI do the same + the context they can reach.
-
-
-
+ const to = useDocHref(docId, href);
+ const linked = Boolean(docId || href);
+
+ const inner = (
+ - {title} -
-- {description} -
-
+
);
+
+ if (!linked) {
+ return (
+
+
+
+
+ {title}
+ {linked && (
+
+
+ {title}
+ {linked && (
+
+ + {description} +
+ {inner}
+
+ );
+ }
+
+ return (
+
+ {inner}
+
+ );
}
export function FeatureGrid({ children }: DocCardGridProps): JSX.Element {
diff --git a/web/docs/src/components/Hero.tsx b/web/docs/src/components/Hero.tsx
index 296953d8..d8b3bc0c 100644
--- a/web/docs/src/components/Hero.tsx
+++ b/web/docs/src/components/Hero.tsx
@@ -196,9 +196,9 @@ export default function Hero(): JSX.Element {
data-animate-delay="2"
className="text-4xl sm:text-5xl lg:text-6xl font-extrabold text-gray-900 dark:text-white mb-5 tracking-tight leading-[1.1]"
>
- Discover any data asset in seconds.
+ AI agents are only as good as
- Then let your AI do the same + the context they can reach.
- The open-source context layer for your AI. Catalog your tables, - topics, queues and APIs then expose real metadata to your AI agents. + Marmot is the open source context layer for agents and + humans. Catalog every service, API, queue, topic, database and + pipeline then expose real, governed context to your AI agents and your + team.
+
+
+
+ );
+}
diff --git a/web/docs/src/pages/index.tsx b/web/docs/src/pages/index.tsx
index 48fc6f8c..4e4d1f11 100644
--- a/web/docs/src/pages/index.tsx
+++ b/web/docs/src/pages/index.tsx
@@ -1,12 +1,14 @@
import React, { useEffect } from "react";
import Layout from "@theme/Layout";
import Hero from "../components/Hero";
+import ContextProblem from "../components/ContextProblem";
import BenefitsShowcase from "../components/BenefitsShowcase";
import QuickDeploy from "../components/QuickDeploy";
import ArchitectureComparison from "../components/ArchitectureComparison";
import DataSources from "../components/DataSources";
import PerformanceProof from "../components/PerformanceProof";
import MCPShowcase from "../components/MCPShowcase";
+import SecurityTrust from "../components/SecurityTrust";
import CTA from "../components/CTA";
export default function Home(): JSX.Element {
@@ -33,17 +35,19 @@ export default function Home(): JSX.Element {
return (
+
+
+
+
+ + Only metadata. Your data stays put. +
++ A context layer needs to know about your assets, not to hold their + contents. Marmot is built so the data itself never leaves your + systems. +
+
+ {pillars.map((p, index) => (
+
+
+
+
+ ))}
+
+
+ + {p.title} +
++ {p.description} +
++ + Talk to us + +
+