← Back to home
Comparison · DevOps

Barman vs Sanity

A side-by-side editorial comparison of Barman and Sanity — release velocity, themes, recent moves, and the top alternatives to consider.

Barman vs Sanity: at a glance

FeatureBarmanSanity
SectorDevOpsDevOps
Velocity score2.55.0
Sparks · 30d00
Top themespostgresql, backup, object-storage, encryptionheadless cms, mcp, ai agents, content validation
Last editorial update2mo ago1d ago
WebsiteVisit →Visit →

What is Barman?

Barman's cloud lifecycle is closed; 3.20.0 starts hardening it for regulated storage.

The arc that ran through 3.18.0 (block-level incremental backups written straight to object storage) and 3.19.0 (restoring from that storage with the standard restore command) is complete. 3.20.0 works the edges of it: SSE-C server-side encryption with customer-supplied keys across every barman-cloud command, parallel uploads to Google Cloud Storage, S3 access point ARNs including S3 on Outposts, and EBS snapshots kept on the Outpost rather than the parent region. A new check-archived-wal-range command reports gaps in the WAL archive, and the minimum Python is now 3.12.

Read the full Barman trajectory →

What is Sanity?

Sanity's MCP server now advertises itself to agents through a server card and llms.txt.

Sanity shipped three MCP server releases in two days. 2.44.0 makes the server discoverable through a /.well-known server card, an HTML or markdown landing page, robots.txt and llms.txt, and cuts CPU per request. 2.43.0 adds an undeploy_schema tool and deprecates workspaceName for schema selection. 2.42.2 fixes validation against deployed schemas and refuses patches that would change a document's _type.

Read the full Sanity trajectory →

Barman vs Sanity: editorial side-by-side

B
Barman
DEVOPS
2.5

Barman's cloud lifecycle is closed; 3.20.0 starts hardening it for regulated storage.

◆ Current state

The arc that ran through 3.18.0 (block-level incremental backups written straight to object storage) and 3.19.0 (restoring from that storage with the standard restore command) is complete. 3.20.0 works the edges of it: SSE-C server-side encryption with customer-supplied keys across every barman-cloud command, parallel uploads to Google Cloud Storage, S3 access point ARNs including S3 on Outposts, and EBS snapshots kept on the Outpost rather than the parent region. A new check-archived-wal-range command reports gaps in the WAL archive, and the minimum Python is now 3.12.

◆ Where it's heading

With backup and restore both working against object storage, the work has moved to the requirements that decide whether a regulated shop can adopt it — who holds the encryption keys, whether data stays in a given location, and whether the archive can be proven complete. The inactive-server handling that began in 3.17.0 also continues: barman cron now stops WAL receivers left streaming on servers switched to active = false, and command behaviour on those servers has been made consistent, with commands that ingest new data still rejected.

◆ Prediction

The Outposts and SSE-C work points toward more storage-backend and residency coverage rather than new backup mechanics. A 3.20.x patch settling the Python 3.12 floor or the new access-point handling is the more likely near-term release.

S
Sanity
DEVOPS
5.0

Sanity's MCP server now advertises itself to agents through a server card and llms.txt.

◆ Current state

Sanity shipped three MCP server releases in two days. 2.44.0 makes the server discoverable through a /.well-known server card, an HTML or markdown landing page, robots.txt and llms.txt, and cuts CPU per request. 2.43.0 adds an undeploy_schema tool and deprecates workspaceName for schema selection. 2.42.2 fixes validation against deployed schemas and refuses patches that would change a document's _type.

◆ Where it's heading

The MCP server is becoming the main way agents read and write Sanity content, and the work has shifted from adding tools to making it safe and findable: guarded patches, accurate safety annotations, full schema lifecycle and discovery metadata. Studio and Manage continue alongside it with speed work and admin features for larger organizations.

◆ Prediction

Expect workspaceName to be removed after the migration period, and more guardrails on write tools such as patch_documents.

Alternatives to Barman and Sanity

Other DevOps products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Barman or Sanity.

See all Barman alternatives → · See all Sanity alternatives →

Recent activity from Barman and Sanity

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1d agoSanityMCP server v2.44.0: Discover the MCP server and improve request reliability
  2. 2d agoSanityMCP server v2.43.0: Remove deployed schemas and prepare for workspaceName deprecation
  3. 3d agoSanityMCP server v2.42.2: More reliable document validation and safer patches
  4. 7d agoSanityMCP server v2.42.1: Clearer document validation results
  5. 8d agoSanityMCP server v2.42.0: Validate documents against deployed schemas
  6. 10d agoSanitySanity Studio v6.20.0: Faster workspace navigation and several bug fixes and improvements
  7. 2mo agoBarmanPython 3.12 floor, SSE-C keys and AWS Outposts support
  8. 5mo agoBarmanFix cloud-wal-restore missing prefix-colliding WAL files
  9. 5mo agoBarmanCloud restore closes Barman's object-storage lifecycle ⚡
  10. 7mo agoBarmanBlock-level incremental backups land in cloud storage ⚡
  11. 9mo agoBarmanQuery and restore now work on inactive servers
  12. 11mo agoBarmanDetect MissingContentMD5 errors by message on S3-compatible stores

Frequently asked questions

What is the difference between Barman and Sanity?

They serve adjacent needs but don't currently overlap on shipped themes. Sanity is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is Barman better than Sanity?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Sanity is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other DevOps products to evaluate alongside.

What are the best alternatives to Barman?

Top Barman alternatives in DevOps are ranked by recent ship velocity. Browse the "Barman alternatives" section above for the current picks, or visit /alternatives/barman for the full list with editorial commentary on each.

What are the best alternatives to Sanity?

Top Sanity alternatives in DevOps are ranked by recent ship velocity. Browse the "Sanity alternatives" section above for the current picks, or visit /alternatives/sanity for the full list with editorial commentary on each.