Straight about this one: for most of what Softr does, we are not the alternative. Softr builds portals, with logins, rows filtered per user and actions written back to your data. Birta publishes static pages.
This page exists for the other half of Softr's audience. Look at what people actually build there and a good share is not a portal: a proposal for one client, a project status page, a monthly report, an onboarding page for a new customer. One reader, no login, no data to filter. Those are pages, and a portal tool is a heavy way to make a page.
One prompt: try the client-facing page without a portal
Paste this into Claude or ChatGPT.
Build a client-facing page as a single static bundle: index.html plus one
style.css, no build step, no framework, no client-side router.
Who it is for: [client name and role]. What it has to communicate:
[the offer, the status, the numbers]. The one action: [approve, reply, book].
Include only what this client needs. No login, no dashboard, no navigation to
other clients' material.
Style: [two words], and specifically generous whitespace, clear hierarchy,
system fonts, one accent colour. Use my real content, no placeholder text.Then send the address and see whether anybody asks for a login. If they do, the table at the bottom is your list. The prompts that publish the result and collect the client's remarks are in AI website prompts.
If clients need to log in, this is not us
Said early, because it decides whether the rest of this page is worth reading.
- Clients log in and each sees only their own records. Birta has no accounts and no permissions of that kind.
- The page reads from or writes to Airtable, Notion, a spreadsheet or a database. There is no data layer here at all.
- Different people need different views of the same source.
- Clients upload files, submit structured records, or work through a queue. Our lead form takes a submission; it is not a workflow.
- You need to take payments in the portal. Not something Birta does yet.
Softr is genuinely good at all of that, and nothing here argues otherwise.
What the page-shaped half gets instead
If what you send a client is one page, here is what changes when the agent writes it and Birta hosts it:
- A link, not an invitation. Nobody creates an account, resets a password or gets provisioned. You send an address.
- Remarks straight on the page. Send the version's own address and the client marks up the thing itself, pinned to the element they mean, with no account. Your agent reads those numbered threads and edits the same draft, then publishes again at the same address. It cannot reply in a thread or resolve one, so closing them stays with you.
- Versions and rollback, so last month's report stays exactly as it was sent.
- A declared lead form when the page needs a reply, with submissions in the panel plus an email digest roughly fifteen minutes after the first.
The free tier holds up to 50 projects at 25 MB each with 10 submissions per project per month, keeps the badge, and a custom domain needs Solo or Pro. For one client page per project, fifty goes further than it sounds.
A proposal, a report, a service page, an event page: the shapes people ask for most, which is why we keep them as live examples.
The honest alternatives
For the portal case, these are the real options, unranked: what your data lives in usually decides.
| Instead of Softr | What it is for | Worth knowing |
|---|---|---|
| Glide | Apps and portals over a spreadsheet or database | The closest like-for-like for data-backed portals |
| Noloco | Client portals and internal tools, Airtable-first | Aimed squarely at the same job |
| Stacker | Portals over your existing data with permissions | Strong on per-user filtering |
| Bubble | Full no-code applications with workflows | More power, more building; by its own docs no code export |
| Adalo | Mobile-first apps | Pick it when the client is on a phone all day |
| Retool, Knack, Tadabase | Internal tools and business apps | Where admin workflows and compliance matter |
| WeWeb | A front end you own over your own backend | For avoiding platform lock-in deliberately |
| Your agent plus Birta | Only when the deliverable is a page, not a portal | No logins, no data layer. That is the whole condition |
Send the client a page, not an account
A link anyone can open, remarks marked on the page itself, and every version kept.