Structured data that your team can query, view, and sync in real time

Design your team's database without writing code, then let each colleague open the same records as a grid, a kanban board, a calendar, or a gallery. Every edit appears for the rest of your team as soon as someone makes it.

Get early accessView all products

Databases that your team can see, edit, and share

Tables stores the records that your team tracks, such as orders, work requests, or grant proposals, in a database that you lay out one field at a time. Each colleague can open those records as a spreadsheet grid, a kanban board, a calendar, or a gallery, while Tables combines the edits that several colleagues make at the same time and records each one in the change history. Beryl Lens fills in AI fields that categorize, summarize, and score each record by comparing it with the rest of the table.

Build a database that each team can open in its own layout

The steps below take one table from its first fields to a shared database that several teams edit at the same time, each in the view that suits its work.

How Tables stores, shows, and links your records

A managed database engine under every table illustration

A managed database engine under every table

As a sheet grows, its filters and lookups can slow down until the spreadsheet tool reaches its row limit. Once your table reaches that point, you will have to move the records into a database and rebuild the screens that your team already knows how to use.

Tables stores every database on a managed Postgres or SQLite engine, which indexes the columns, enforces the constraints, and plans each query. Your team works in the same interface at 500 rows and at 500,000, because only the storage beneath that interface grows with the table.

A view for each way that your team works

A sales lead may plan from a pipeline board, while a project manager plans from a timeline and the operations team works in a spreadsheet. If each of them keeps the data in a separate tool, the copies will disagree from the first edit that one person makes to their own.

Your team can open one table as a grid for detailed edits, a kanban board for work that moves through stages, a calendar for dated records, a gallery for records with images, a timeline for date ranges, or a form that collects new entries from people who see only that form. Every view shows the same records, so when someone drags a card to Done on the kanban board, Tables marks the record complete in the grid and takes it off the calendar.

Standard, linked, computed, and AI fields

Text, number, and date fields can hold the simple facts about a record. A team that tracks orders or tickets will also need formulas that use values from another table, totals across linked records, and a score that someone has to judge from the content of each entry. An AI field that works on one row at a time can score each entry, but it cannot compare that entry with the rest of the table.

Tables includes standard types such as text, number, date, select, currency, and attachment, together with relations, formulas, lookups, and rollups that connect and calculate across tables. Beryl Lens fills in AI fields that categorize records, summarize text, detect sentiment, and score entries, using the whole table to work out each value. On a table of support tickets, for example, Beryl Lens sets the priority of each ticket after comparing it with every other ticket in the table.

Editing together without losing a value illustration

Editing together without losing a value

A shared spreadsheet can keep whichever of two simultaneous edits saves last and discard the other without a warning. On a team spread across time zones, the person whose edit disappears may be asleep at the time, so the team can go days before anyone notices the missing value.

Tables sends each edit within milliseconds to everyone who has the table open. When two people type into the same text field at once, Tables keeps both insertions, while for a number field it keeps the later value and records the earlier one in the change history. That history lists the user, the time, and the previous value of every edit, so you can trace any value back to the colleague who entered it. To help colleagues stay out of each other's way, each person's live cursor marks the cell that they are editing, beside a presence list of everyone who has the table open.

Records linked across tables

In a set of separate sheets, you will have to type a customer's name into the orders sheet, the invoices sheet, and the support sheet. When the customer changes their name, someone will have to correct all three sheets before every report shows the new one.

A relation field links a row in one table to rows in other tables, so a customer record can link to the customer's orders in one table and to their support tickets in another. A lookup field shows a value from the linked row, which means that the customer's name appears on each order without anyone typing it twice. A rollup field totals the linked records, so the customer row shows the total order value, the number of open tickets, and the date of the last contact, all of which Tables recalculates whenever a linked record changes.

One table

Behind every view

0

Values lost when two people edit at once

0

Artificial row caps

What changes when your team works in one table

Room for hundreds of thousands of rows

Because a database engine indexes your data, Tables keeps filters and lookups fast at hundreds of thousands of rows, a size at which some spreadsheet tools slow down or stop accepting new rows.

Each team plans in its own layout

Your sales team can work from a kanban board of the same records that finance checks in a grid and marketing schedules on a calendar, so an edit in one view appears in the others.

AI fields that weigh every record

When Beryl Lens categorizes, scores, or summarizes a record, it first checks that record against every other record in the table, so it can rate the sentiment of one piece of feedback against all the other feedback that your customers send.

Every change kept when colleagues work at once

When colleagues in different time zones edit the same table, Tables keeps each person's changes and logs who made them, so the colleague who signs in next can see every change since their last visit.

How organizations use Tables

Three squads share one feature roadmap

Three engineering squads track their features in the same Tables database. Each squad filters its own kanban view by team tag, while the product lead follows every feature across the squads on a timeline view. A relation field links each feature to the customer requests in a separate feedback table, so the product lead can see how many customers ask for each feature.

Result

Tables shows the product lead every squad's features on one timeline, so the lead stops compiling the squads' plans into a separate spreadsheet. Since each feature links to the customer requests behind it, the lead can rank the roadmap by how many customers ask for each feature.

Three squads share one feature roadmap

Grants office tracks proposals against deadlines

A university grants office tracks its funding proposals in one Tables database. Program officers draft their applications in the grid view, while the director moves each proposal through the Drafting, Internal Review, Submitted, and Awarded stages on a kanban board. The calendar view shows each funder's deadline beside the proposal that it applies to. Before internal review, Beryl Lens checks each proposal through an AI field and flags any proposal that lacks the required budget narrative.

Result

Every program officer plans against the funder deadlines on the shared calendar, so the director can drop the separate list of due dates. Because Beryl Lens flags a missing budget narrative before internal review, the director also stops sending proposals back from review for that reason.

Grants office tracks proposals against deadlines

Facilities passes work orders between teams

A campus facilities group routes maintenance work orders between its trades in one Tables database. A relation field links each work order to the People profile of the staff member who reports the fault. Each technician works from a grid of their own assignments, while each trade desk sorts its incoming requests by status on a kanban board. A rollup field on each desk's row counts its open jobs and averages its time from report to close.

Result

Tables recalculates the rollups as each work order opens or closes, so a desk lead can watch a backlog form without waiting for a weekly report. When the electrical desk's count shows 14 requests open for more than 7 days, its lead can call in a contractor before tenants report the same fault again.

Facilities passes work orders between teams

Camera rental house books gear by status

A film equipment rental house keeps its inventory in Tables, with fields for daily rate, category, condition, status, and assigned crew. The gallery view shows each lens and camera body with its product photo, while the calendar view lays out every booking by pickup date. When a booker sets a unit to Reserved, Tables updates the linked table of productions that are waiting for that unit and sends the account manager a notification through Channels.

Result

Bookers choose gear for a shoot from the photos in the gallery and confirm on the calendar that it is free, so they can retire the separate availability spreadsheet. Since a booker can change a unit's status from their phone on set, the rest of the team can see which crew holds each unit without asking by email.

Camera rental house books gear by status

Restaurant group approves supplier purchase orders

A restaurant group with several locations tracks its purchase orders in Tables, with relation fields that link each order to its supplier and to the location that places it. A rollup field on each supplier's row totals the outstanding balance across every location. Alongside that rollup, an AI field from Beryl Lens flags any order in which a line item exceeds the contracted price by more than 10%. After a buyer enters an order in the grid view, the purchasing manager moves it through the Submitted, Verified, Approved, and Received stages on a kanban board.

Result

Beryl Lens flags an overcharge when the buyer enters the order, so the purchasing manager catches each off-contract price before the monthly reconciliation. Each supplier's row shows what the group owes that supplier across every location, which means that the manager can check the balance before approving the next order.

Restaurant group approves supplier purchase orders

What Beryl adds to each table

Beryl can fill in AI columns, answer questions about your records, and flag the records that break from the pattern of a table.

AI-computed columns

Beryl Lens fills in a column on every row from a plain-language description that you write, judging each row against the rest of the table.

Learn more

Questions in plain language

Beryl answers a plain-language question about your records from the records themselves, citing the row that supports each part of the answer.

Learn more

Anomaly detection

Beryl flags a record that departs from the pattern of the rest of the table, such as an outlying amount or a malformed entry, so your team can correct it before anyone builds a report on it.

Learn more
Explore Beryl for Tables

All supported integrations

Connect Delalify People with the tools your team relies on. Sync data automatically and keep everything current across your entire workflow.

Salesforce

Sync accounts, deals, and customer journeys.

HubSpot

Connect marketing campaigns and sales pipelines.

Google Workspace

Integrate Gmail, Drive, and Calendar.

Microsoft 365

Connect Outlook, Teams, and Exchange.

Slack

Push contact updates to team channels.

Zoom

Log meetings and surface call history.

WhatsApp

Send messages and engage contacts directly.

LinkedIn

Connect professional networks and contacts.

Facebook

Reach audiences through social campaigns.

X

Sync your followers and track engagement.

Blackbaud

Sync donor records and fundraising campaigns.

Canvas

Connect student data and course information.

Zendesk

Unify support tickets and customer context.

DocuSign

Manage agreements and consent forms securely.

Zapier

Connect 6,000+ apps without code.

Shopify

Sync customers, orders, and store data.

Stripe

Connect payment data and customer profiles.

Mailchimp

Sync audiences and automate email campaigns.

Intercom

Unify conversations and customer messaging.

API

Build custom integrations securely.

Explore Tables in more detail

Each page below explains one part of Tables and shows how teams use it.

Databases

Design your tables in a visual editor while a managed Postgres or SQLite engine stores every row.

Explore

Views

Open the same table as a grid, a kanban board, a calendar, a gallery, a timeline, or a form.

Explore

Fields

Give each column the type that its values need, from relations and formulas to AI columns.

Explore

Sync

Several colleagues can edit the same table at once, with a live cursor for each person.

Explore

Questions about Tables

Give each team the same records in its own layout

Tables stores the records behind your Builder apps and links them to People contacts and OneCloud files, while your colleagues edit them together in real time.

Get early accessView all products