Your data already has relationships. Your spreadsheet doesn’t know about them.

What this replaces.

Nobody chose to run operations across five tools. It arrived one reasonable decision at a time, and now reconciling it is a standing item on somebody’s Friday.

The part your customers touch

Let the outside world in, without letting it in.

A base is only useful if the people who generate the data can reach it. Publish any view as a public form — conditional logic, file uploads, calculated fields, save-and-resume — and a submission writes a typed, correctly-linked row, with a parent and its children in one transaction. The person filling it in has no account and never sees the base.

When a form is not enough, build an app: a published surface over the same base with its own users, its own roles, and a canvas you lay out yourself. Contractors see their jobs, clients see their tickets, and nobody sees a spreadsheet.

Bring your formulas

241 functions, and they cross sheets.

Math, statistics, text, logic, date, financial and the lookup family — VLOOKUP, XLOOKUP, INDEX/MATCH, IFS, TEXTJOIN — with references that reach another sheet by name. Type into the cell. It runs the product’s own engine, so what comes back is what Relationsheet gives back, error codes included.

Paperwork, from the records

The document is the data, laid out.

Write a template once with tokens, conditionals and a repeat block over a relation, and every record can produce its own statement, quote, work order or contract — with the linked rows already in it. Documents export to Word or PDF, carry drawn signatures through an approval, and an automation can generate one the moment a row changes.

Edit the template on the left. The letter re-renders through the product’s own merge engine, the same one the document builder uses.

Dear J. Okafor,

Re: account Cordell Freight (Enterprise)

Our records show 3 open project(s) against your account and a
linked balance of $188,500.

Of that, $92,500 is still outstanding across the invoices below.


  INV-000104   Apr 2   $96,000   Paid

  INV-000122   Jun 12   $74,000   Sent

  INV-000129   Jul 9   $18,500   Sent

Yours,
Accounts, Relationsheet

Hiding a column is not what protects it.

Access is decided in Postgres, below the interface, by row-level security. Grants apply to a whole sheet, to specific rows, or to specific columns, for a person or a group — and a rule can depend on the value in a cell, so somebody gets exactly the rows for their own region and nothing else. Columns can be hidden outright or returned redacted, and every change is recorded with a per-cell diff in a tamper-evident log.

It is the same machinery that makes the forms and apps above safe to hand out: published surfaces are not trusted clients, they are constrained ones.

No layer here is a separate purchase.

Elsewhere the project module, the reporting module and the form builder are separate purchases stacked on top of the seat. Here they are one product. A plan buys collaboration, administrative control and scale — and paid plans are opening shortly, so today everything runs in the free workspace, within the limits printed on it.

These are real limits, in force today. Every plan still carries the whole product. See what a plan buys →