Flat pricing, unlimited users, no per-seat licensing — and no sales call to find out whether it's any good. The button below opens a real, working database in your browser: Microsoft's own Northwind sample, rebuilt in Bionic Forms, with its customers, orders and line items all wired together. No signup, no email, nothing to install.
Both of these are the CRM template as it ships — one click from an empty account, no setup. They are screenshots of the running product, not mockups.

A grouped list view. Columns are renamed and retyped in place; there is no separate schema screen.

The same app's dashboard. The charts read live from the records above, not a separate reporting tool.
Flat, by what you build — never by how many people use it. Add the whole team, the contractor, the client who needs read access: the price doesn't move.
That's the question this is really built around, and it's the one I'd genuinely like to hear your answer to. A departmental Notes app usually outlives the person who wrote it, and what's left behind is often an NSF nobody can safely change.
Bionic Forms is, deliberately, an attempt at what Notes got right: a document database where the application is the data, forms and views are definitions rather than code, documents carry their own history, and the whole thing works offline and replicates when it can. If you have spent years in Notes, you already understand this product — that is not a coincidence, it is the design brief.
What it does not carry over is the part people actually complain about: no Domino server to run, no designer client, no LotusScript, and no per-seat licensing. Flat price, unlimited users.
You don't have to wait for anyone to move your data. A Notes view exports to CSV, and the app reads one directly: drop it in and it proposes a collection — a field per column, with the type it thinks each column is and the reason it thinks so, plus a few real values from your own file so you can check the guess instead of trusting it. Nothing is written until you say so.
Where it can't tell, it asks rather than guesses. A column of dates like 03/04/2026 could be
the 3rd of April or March 4th, and the rows it would get wrong look exactly like the rows it would get
right — so it stops and asks you which, and won't import until you answer. If one value anywhere in the
file can't be read, nothing is imported at all: a half-loaded collection is worse than an empty one,
because you can't tell which records made it and running it again duplicates the ones that did.
Import several files together and it looks for the links between them — an order that names a customer ID gets connected to its customer, so you can open one and see the other. It only links where both the column name and every value agree; where it isn't sure, it leaves the values alone rather than guessing.
Where it stops: it moves data. It does not convert forms, views, agents or LotusScript — there is no automatic conversion of a Notes design. Rebuilding the design is still a job somebody does by hand; what this gets you is your own records in front of you, in a couple of minutes, while you decide whether the rest is worth doing.
It isn't a Notes importer — there's no automatic conversion of an NSF, and I'm not going to pretend a rebuild is a click. It isn't a spreadsheet, it isn't a form builder, and it isn't finished software with a track record. It's an honest early product with a pricing model that doesn't punish you for adding people, and I'm looking for a handful of people willing to tell me where it falls short.
Nothing, and there is no call to book. Open the demo, click around a real database, and decide for yourself. If you want your own, the free tier is genuinely free and takes a minute.
When you are ready to bring your own data, a Notes view exports to CSV and the app reads one directly, working out how your documents relate to each other — that is the part described above, and it is self-serve. You do not need me for it.
Still comparing? I wrote up the Notes and Domino alternatives, including why the end-of-life story is wrong on the facts, what never migrates out of an NSF, and where my own access rules fall short of Notes reader fields.
Bionic Forms is built by Matt Bidwell (Bionics LLC). If something here reads as overclaiming, tell me and I'll fix the page — that's a promise I can actually keep at this stage. Either way you can reach me at matt@bidwellhq.com.