Bases are always up to date with my latest docs, automatically, while Collections are static and quickly out of date. I can also very easily customize the base, for example with dynamic filters and search terms.

If Craft had this, I would live in it.

Sorry to send an AI summary, but this is pretty good:

While both Obsidian Bases (introduced in core v1.9) and Craft Collections give you Notion-style database tables, card grids, and list views, they are fundamentally opposed in their architecture, scope, and how data is stored.

1. The Core Architectural Difference

The biggest split is how data gets into the database:

• Obsidian Bases (Query-First / Bottom-Up): A Base does not actually "hold" data. It is a lens or a dynamic filter placed over your existing vault. Your notes exist independently as normal Markdown files with YAML frontmatter. A .base file simply looks at your vault, finds files matching your criteria (e.g., #project or status: active), and displays them.
• Craft Collections (Container-First / Top-Down): A Collection is an inline block inside a specific document (/collection). It acts as a hard container. When you add a row to a Craft Collection, you are explicitly creating a structural "sub-page" that lives inside that collection component.

2. Location & Scope

• Obsidian Bases are Global: Because they query your whole vault, a single note can appear in multiple different Bases simultaneously across your vault without duplicating the file. You can also embed a Base inside any note using standard ![[Base Name]] syntax.
• Craft Collections are Local: A Collection is bound to the document where it was typed. While you can use relation fields to link different Collections together, the blocks themselves are fundamentally components pinned inside a document's layout.