# maxpert/marmot

A distributed SQLite server with MySQL wire compatible interface

Repository: https://github.com/maxpert/marmot
Canonical: https://ross.abutalabs.com/products/marmot
Homepage: https://maxpert.github.io/marmot/
Language: Go
License: MIT
License Family: permissive
Topics: database, distributed, replication, sqlite3, mysql
Last push: 2026-08-11T17:03:15+00:00

## Health v2 (maintenance only)
Score: 87/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 97, release rhythm 67, longevity 100
- inputs: {"age_days": 1467, "days_push": 22, "days_rel": 220, "gap_med": 1, "n_releases_24m": 18}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 2819, forks 77 (observed 2026-08-28T04:07:23.939589+00:00)

## What it is
Marmot is a leaderless, distributed SQLite replication system built on a gossip-based protocol with distributed transactions and eventual consistency. It exposes a MySQL wire-compatible interface so existing MySQL clients, drivers, and applications like WordPress can connect without modification.

## Use cases
- run a distributed WordPress with a replicated database across regions
- deploy lightweight SQLite replicas as edge or Lambda sidecars with local reads
- use it as an edge vector database for RAG with built-in ANN search
- serve regional configuration data with fast local reads and replicated writes
- geo-distribute product catalog data with eventual sync
- connect existing MySQL clients and ORMs to a SQLite-backed cluster

## When to choose
- you need read-heavy, geo-distributed SQLite with no single point of failure
- you want MySQL client compatibility without running a full MySQL cluster
- you want automatic split-brain recovery and no leader election or failover coordination
- you need tunable consistency (ONE/QUORUM/ALL) balancing latency and durability
- you want local vector search for RAG workloads on replicated data

## When to avoid
- you require strong serializability or strict consistency guarantees
- you need heavy write throughput across regions rather than read-heavy workloads
- you rely on advanced MySQL features not supported by the MySQL-to-SQLite transpilation
- you need a mature battle-tested distributed SQL database like CockroachDB or Spanner

## Facets
- artifact type: service
- maturity: active
- function: database, vector-database, search-engine, http-server
- domain: databases, microservices, self-hosted, backend, web-development
- platform: windows, self-hosted, go, cli
- tags: sqlite, mysql-wire-protocol, leaderless-replication, gossip-protocol, eventual-consistency, edge, cdc, distributed-transactions, replication, linux, macos, docker

## Member repositories
- maxpert/marmot (main) score 87

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:07:23.939589+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-29T18:48:43.090267+00:00, confidence not recorded.
  - readme: https://github.com/maxpert/marmot (fetched 2026-08-28T04:07:23.939589+00:00, sha 0f3c75838c6d)
  - homepage: https://maxpert.github.io/marmot/ (fetched 2026-08-29T09:53:43.906717+00:00, sha 9eef06799f2d)
- Data as of 2026-08-30T08:39:29.467469+00:00.