Build an internal tool

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.

The spreadsheet, or a real app · 54

Feature by feature

Swipe to compare all columns →

The spreadsheet, or a real app54
Who can see itWhoever has the link, or an auth system you buildA login with a code to their mail, Google or a password
The dataRows anyone with access can overwriteRecords written through the server, with the owner checked
A new fieldEveryone updates their copySay it; the tool changes
Running it somewhereA server, a certificate, updatesPublished, with your own domain included
Getting the data outCopy and pasteDownloadable from the admin

Written from each product's public documentation. Products change: check theirs before you decide. No prices here for the same reason.

FAQ · Build an internal tool

The 10 questions people ask about Build an internal tool

Can I restrict it to my team?

Yes. Require a login and keep the records private.

How do people log in?

A code to their mail, with Google, or with a password they set.

Can two people edit at once?

The records are written on the server, so the last write wins rather than two copies drifting apart.

Can I see who did what?

The records carry who wrote them.

Can it send an email when something is submitted?

Yes, from a mailbox on your own domain.

Can it hold a file?

Yes — uploads attached to a record.

Is there an admin I do not have to build?

Yes, with the records, the users and the payments if the tool charges for anything.

Can I give someone access to only one part?

For the mailbox, yes. For records, the split today is public, logged-in, or owner.

What if it outgrows this?

Download the files and the data. Nothing is locked in a proprietary runtime.

Does an internal tool need a paid plan?

No. The free plan includes the domain and ten builds a day.

+

Keep comparing

Build an internal tool

Describe your site — free