Give clients a login, not another spreadsheet.
Build a password-protected portal on top of the tables you already keep. Your customers sign in and see their rows — only theirs — on your domain, with your branding, and they can update them without you touching anything.
- 18 block types
- Your own domain
- Per-customer row scoping
- Versioned publishes with rollback
- 9 starting layouts
Eighteen blocks. One data source. No export step.
Every block reads live from a TinyTables view, so the portal is never a stale copy of the truth — it is the truth, filtered to the person looking at it.
Show the data
Tables, lists, detail views, stats, charts, calendars, kanban boards, maps and pivots — all bound to a view you choose.
Only their rows
Point a block at an owner column and each signed-in customer sees their records and nobody else's, enforced on the server.
Let them edit
Inline cell editing, add a record, remove a record, and a per-user 'mark complete' state that writes straight back to the table.
Collect input
Embed a published TinyForm in card, classic or chat mode, right inside a portal page.
Your brand, not ours
Six colour tokens, three font roles, button shape, elevation, density, radius, light or dark, your logo, your sign-in screen.
Your domain
Add a hostname, get the DNS records, verify, and the portal serves over SSL on your own domain.
Three ways in
Native email and password, credentials held as rows in a Users table you control, or your own Keycloak SSO.
Publish safely
Drafts autosave; publishing takes an immutable snapshot after a completeness and safety review, and you can roll back to any version.
Describe it and it builds
Say what the portal is for and the assembler lays out the first version — then edit it by asking, or by hand.
From table to client login.
- 01
Pick the data
Choose a TinyTables base, table and view. That view is what the portal can ever show — nothing outside it is reachable.
- 02
Lay out the pages
Drag blocks onto a 12-column grid. Set each page to public, signed-in, or a specific role. Set the owner column so people only see their own rows.
- 03
Publish it to your domain
Publishing snapshots the whole spec and strips every data binding from what the browser receives. Add your hostname, verify DNS, and it goes live over SSL.
It uses the rest of your TinyCommand.
Same login, same data, same bill. No export step between the thing that finds the answer and the thing that acts on it.
What TinyPortal is not.
Every tool’s marketing page tells you what it does. This is the part that usually isn’t on one, so you can find out now instead of after you’ve built on it.
- The nine templates are layouts, not working apps. They give you the structure; you point the blocks at your own tables. There is no one-click provisioned demo portal.
- Charts are bar, line and pie. There is no area chart, and a date grouping does not roll up by day on its own yet.
- Search inside a portal filters the rows already on the page. It is not a server-side search across the whole table.
- Customer SSO works but is not yet switchable from the builder UI — the panel offers email/password and the Users table, and SSO has to be set through the API.
- Inviting a teammate to help build shares the whole workspace, not just that one portal. The invite dialog says so.
- Embeds are sandboxed and HTTPS-only, so a site that refuses to be framed will not render inside a portal.
- Pages fetch 50 rows at a time, up to 200. Aggregations scan up to 20,000 rows and then tell you the number is approximate rather than quietly rounding.
Questions people actually ask.
Do my customers need a TinyCommand account?
No. Portal end-users sign in to your portal with their own credentials — email and password, a Users table you control, or your own SSO. They never see TinyCommand.
Can two customers see each other's data?
Not if you set an owner column. Row scoping is applied on the server before anything is sent, and every data binding is stripped from the published payload.
Can it run on my domain?
Yes. Add the hostname in the builder, add the DNS records it gives you, verify, and it serves over SSL. Until it's verified, it doesn't resolve.
What happens if I break something?
Publishing is versioned and immutable. Roll back to any earlier version, and your draft is untouched when you do.
Can a button in the portal kick off a workflow?
Portal actions cover navigation and writing back to your tables today. Workflow-triggering buttons exist in the builder — check with us on whether they're switched on for your workspace before you design around them.
Your clients already have a login for everything else.
Give them one for their data with you — on your domain, from the table you already maintain.