On 54 an internal tool is a site whose records are private: only people who log in can see them, the admin lists them, and you change the tool by describing the change instead of running a deploy.
Most internal tools are the same three pieces — **a form, a list, and who is allowed to see it** — and they get built as a spreadsheet because the real version needs a server, a login and someone to keep both alive. The spreadsheet then becomes the thing nobody can change and everybody depends on.
Swipe to compare all columns →
| The spreadsheet, or a real app | 54 | |
|---|---|---|
| Who can see it | Whoever has the link, or an auth system you build | A login with a code to their mail, Google or a password |
| The data | Rows anyone with access can overwrite | Records written through the server, with the owner checked |
| A new field | Everyone updates their copy | Say it; the tool changes |
| Running it somewhere | A server, a certificate, updates | Published, with your own domain included |
| Getting the data out | Copy and paste | Downloadable from the admin |
Written from each product's public documentation. Products change: check theirs before you decide. No prices here for the same reason.
Yes. Require a login and keep the records private.
A code to their mail, with Google, or with a password they set.
The records are written on the server, so the last write wins rather than two copies drifting apart.
The records carry who wrote them.
Yes, from a mailbox on your own domain.
Yes — uploads attached to a record.
Yes, with the records, the users and the payments if the tool charges for anything.
For the mailbox, yes. For records, the split today is public, logged-in, or owner.
Download the files and the data. Nothing is locked in a proprietary runtime.
No. The free plan includes the domain and ten builds a day.