Features

When notes grow up,
they become databases.

Tables, boards, calendars, timelines, and galleries over the same rows, with relations, rollups, and formulas keeping the numbers honest. On the NoteX web workspace.

Web surface

Six views of
one truth.

On NoteX web, any list can grow into a database: pages with typed properties instead of loose text. Then every team looks at it their own way: a table for the operators, a board for the sprint, a calendar for deadlines, a timeline for the quarter, a gallery for design work, a list for the minimalists.

Views remember their own filters, sorts, hidden properties, and grouping, so "my view" and "your view" stop being an argument.

Backlog2
Query analytics dashboard
EngQ3
Onboarding email revamp
Marketing
In progress2
Search v2 ranking spec
ProductP0
Deploy runbook
Ops
Done1
Beta cohort selection
Product

Board view. The same rows are a table, a calendar, a timeline, a gallery, and a list.

Properties

Sixteen property types,
including the serious three.

Text, number, checkbox, select, multi-select, date, URL, email, phone, rating, progress, and attachments cover the everyday. The serious three do the heavy lifting: relations link rows across databases (tasks to projects, invoices to clients), rollups aggregate across those links (count of open tasks, sum of hours, latest date), and formulas compute what you would otherwise maintain by hand.

Views per database
6
table · board · calendar · timeline · gallery · list
Property types
16
incl. relation, rollup, formula
Rollup functions
10+
count, sum, average, min, max, median…
Saved formats
Per view
filters, sorts, grouping, hidden props

Working the data

Built for the way
teams actually filter.

🔍 Filter groups

Stack conditions with and/or logic across any property: status is Active AND (owner is Maya OR priority is P0). Twenty-plus operators cover text, numbers, and dates.

👁️ Row peek

Click a row and it opens as a side panel: the full page with all its blocks, without losing your place in the table.

📄 Databases inside pages

Embed a database as a block in any note, so the sprint board lives inside the sprint notes and the SOP index inside the team wiki.

Which surface?

CapabilityWhere
Create and edit databases, all six viewsNoteX webWeb
Relations, rollups, formulasNoteX webWeb
Pages containing databases, syncedBoth surfacesSync
Database rows over the APIAny clientAPI

Databases are a web-surface feature today. Desktop users open the same workspace in the browser when they need the boards, and keep the desktop app for writing.

Frequently asked questions

Are databases available on the desktop app?

Databases are a web-surface feature today. Pages sync across both surfaces, and desktop users open the web workspace when they need boards and tables.

What views can a database have?

Table, board (kanban), calendar (month and week), timeline, gallery, and list. Each view saves its own filters, sorts, grouping, and hidden properties.

What do relations and rollups do?

Relations link rows across databases, like tasks to a project. Rollups then aggregate over the linked rows: count the open tasks, sum the hours, find the latest date. Formulas compute values from other properties.

Can I filter and sort like in Notion?

Yes: filter groups with and/or logic, more than twenty operators, multi-level sorts, and grouping. If you know Notion databases, you already know how this works.

Can databases live inside regular pages?

Yes. A database can be a block inside any note, so boards and indexes sit right where the surrounding context is.

Your notes deserve a better engine.

A Notion-style block editor on the engine behind the world's most popular code editor. Notes stay files you own, extensions add what you need, and AI plugs in natively. Free to start, on web and desktop.

Free to start · Your files, your disk · Windows desktop & web