Skip to content

Database

Database turns your objects into structured, queryable tables — tasks, contacts, a reading list, a CRM, an inventory.

Database: A query-backed listDatabase: A query-backed list
A query-backed list — The studio's tasks as a live collection — status and priority pills in typed cells, counts in the sidebar.
Database: Same objects, board viewDatabase: Same objects, board view
Same objects, board view — Flip the view and the list becomes a kanban grouped by status — no export, no copy.
Database: Row inspectorDatabase: Row inspector
Row inspector — Open any row in the right panel and edit its properties without leaving the view.
  • Six view kinds per List: grid, list, gallery, kanban board, calendar, and timeline with drag and dependency lines.
  • Filters with AND/OR groups and live relative-date ranges like “last 7 days”.
  • Formula and rollup columns compute across properties and relations; footers aggregate sum, average, median, and more.
  • Edit cells in place with the same typed cells the rest of the platform uses.
  • CSV import with type inference; export a List to CSV, JSON, or Markdown.
  • Save any object as a template and start new rows from it.
  • Embed a live List inside a note with the /database command.

Each row is an object, and each column is a typed property — text, number, date, checkbox, select, link, and more. Properties are defined at the vault level, so a “Status” or “Due date” means the same thing wherever that object appears. Cells are edited inline through Brainstorm’s shared property system.

The same set of objects can be viewed several ways without duplicating data:

  • Table — the classic rows-and-columns grid.
  • Board — a kanban grouped by a property.
  • List, Gallery, and other layouts for different shapes of data.

A view defines how objects are filtered, sorted, and grouped; switching views never changes the underlying objects.

Rows are ordinary objects, so a task you create in a Database can appear on the Calendar, as a node in the Graph, and linked from a Note. The database is one lens over your data, not a silo.

  • Objects — the rows and properties model
  • Calendar — a time view over the same objects