Get early info on our new product: Superhuman Databases.
You may have heard us talk about Superhuman Databases as part of the Superhuman Docs launch. While Databases are still in a closed beta, we wanted to share some early info on the new product, how it works alongside docs, and what you can expect next.
Basics of Superhuman Databases
Superhuman Databases is a standalone home for structured data — built to scale up to a million rows, with a table-first experience optimized for creating, editing, and managing large datasets.
Where a table in a doc works well for smaller, self-contained data living alongside other content, a database is designed for the data your team relies on everywhere: the kind you want to manage centrally and reuse across many docs at once, without sacrificing performance as it grows.
How Databases work with Docs
Superhuman Databases and Docs are built to work together:
- Standalone or connected: Create and manage a database on its own, or connect it to any doc. When you add a table to a doc, you can easily choose to connect it to an existing database.
- Real-time, two-way sync: Once a database is connected to a doc, everyone with access to that doc can see the data, and any changes stay in sync in both directions.
- One dataset, many docs: A single database can power multiple docs at once. For example, you can have a company-wide OKR database that flows into every team's individual hub, or a project tracker that's referenced across several planning docs.
- Permissions built for data: Sharing a database lets you separate who can edit values from who can change its structure (add or remove columns and tables), so the right people have the right level of control.
Tables in Docs aren't going anywhere. They're still the right fit for lighter-weight, self-contained work. Databases are for when you need to scale, reuse, or centralize.
Databases roadmap
Superhuman Databases is currently in a closed beta with a limited group of customers, running alongside the Superhuman Docs launch. We're using this period to gather real-world feedback before a wider release, so functionality is still evolving.
Available today
- Creating databases with multiple tables and views (grid, card, board, calendar, and timeline)
- Real-time syncing between databases and docs, in both directions
- Permissions for viewing, commenting, editing rows, and full structural access
- Core filtering, sorting, grouping, and formulas
- Copy data from existing doc tables into a new database
Coming soon
- Native AI support for building and querying databases
- API and MCP access
- Conditional formatting
- Database search
- More direct tools for converting existing doc tables into databases
- Restore deleted content
Further down the road
- Support for Pack sync tables and Pack columns within databases
- More granular sharing — such as giving a doc access to a single table or view, rather than the whole database
- Advanced formulas
- Buttons
- Canvas columns
- Automations
- Subitems
- Mobile and desktop app support
Interested in joining the waitlist for the beta? Please fill out this form.
FAQs
How is a database different from a table in a doc?
Tables in docs are great for smaller, self-contained data that lives alongside other content in a single document. Databases are purpose-built for larger, more complex datasets that you want to manage centrally and reuse across many docs, with a dedicated experience and permissions designed specifically for data.
Will Databases replace Cross-doc sync?
Over time, yes. Databases are designed to become the standard way to reuse data across docs, with real-time two-way syncing, support for far more rows, and permissions that live with the data itself rather than with any single doc. Existing Cross-doc syncs will keep working as-is, and we'll offer tools to help you migrate when you're ready.
Can I convert my existing tables into a database?
Yes — today, you can manually copy your table's data into a new database. But we're building more direct conversion tools, coming soon. If you're part of the beta, we'd love your feedback on what would make that process smoother.
Who can see and edit data in a database?
The person who creates a database owns it and can share it with others at different levels: view, comment, edit rows, or full access. When a database is connected to a doc, anyone with access to that doc can view the data — but editing it requires edit access to both the doc and the database.
Is there a limit to how much data a database can hold?
Databases are built to scale — up to a million rows on Enterprise plans — with data loaded on demand so performance stays fast regardless of size. Exact limits by plan are still being finalized.
Can I connect a database to a Pack sync table, or use Pack columns?
Not yet. Database tables can currently only reference other database tables. Pack integration is on our roadmap, which will make it easier to bring in data from external sources at scale.
When will Superhuman Databases be available to everyone?
Databases is currently in a closed beta with a limited group of customers. We don't have a firm date for wider availability yet, but we'll share updates here as that changes.
What will Databases cost?
We expect Databases to be included for existing Enterprise customers, as well as part of the Superhuman Business plan. Final pricing and packaging are still being finalized.
Will I be able to use AI, the API, or an MCP with Databases?
Not at launch, but all three are on our roadmap — including native AI for building and querying databases, API access, and integration with the Docs MCP.