Skip to main content
Version: 0.9

Introduction

Marmot is the open source context layer for your whole stack: a single catalog for every asset your systems and teams depend on, from services, APIs, queues, topics and brokers to databases, tables and pipelines. It exists to solve context starvation, the moment an engineer or an AI agent has to act without knowing what exists, who owns it, what it means, or what it connects to.

Marmot is built so both humans and agents can ask that question and get a real answer. Catalog your assets once, enrich them with ownership and business context, and expose them through the UI, a REST API, and a built-in MCP server that lets AI agents read your catalog, then write back the lineage they generate.

See Marmot in Action

Explore the interface and features with the interactive demo - no installation required.

Try Live Demo

Built for agents

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

Marmot is built entirely in Go with PostgreSQL being the only external dependency, handling search, job scheduling and metadata storage. Unlike traditional catalogs that have opinionated ingestion methods, Marmot lets you populate your catalog however you like.

Marmot architecture diagram

What Marmot stores

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.

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.

Building for a regulated environment?

Run it yourself so nothing leaves your VPC, and read the source to verify exactly what is collected.

Talk to us

Features

Everything you need to turn scattered assets into a context layer that humans and agents can both query.

Get started

Pick a starting point. The Quick Start walks you from an empty deployment to a populated catalog, step by step.

Join the Community

Get help, share feedback, and connect with other Marmot users on Discord.

Join Discord