Form tools collect what the world sends you. Faldaro works it to a decision.
Faldaro is the intake platform. Claims, applications and requests arrive through a public link and become records — priced, routed, approved, signed and paid by your rules, your team and your AI agents. Nothing is computed in the browser, and nobody who submits is a seat.
Free forever — unlimited forms, ten thousand submissions a month, AI credits included. No card required.
Arrived 09:12 through the public link — nobody on your side typed a thing.
- Client
- Acme Logistics
- Incident
- 14 Jul 2026
- Vehicles
- 3
- Rate band
- B
- Submitted through the public link a stranger · no account · no seat
- Estimate computed: 3 × $4,000 + $400 towing on the server
- Moved to Risk review by rule
- Deadline armed: 48 hours escalates itself
- Agent note: “Band B, no injuries. Towing receipt missing — flagged for the reviewer.” acting on this record only
- Claims lead notified, tracking link mailed to the claimant by the form’s rules
Somewhere in your company, the outside world lands in a spreadsheet
A claim arrives through a form, someone exports it, and the real work starts by hand. The spreadsheet becomes the system — and everything wrong with it happens after submit.
-
The total checked by hand
The server computes it from the answers, on every save and every read. There is no number to double-check, because there is no number a browser can send.
-
The approval chased by email
A workflow state with an owner and a deadline that escalates itself. Forty-eight hours in Review and the record moves — nobody has to remember to chase it.
-
The paperwork assembled by copy-paste
Documents generate from the submission the moment its state changes — and anything sold is priced by the rules and delivered on settlement, from the same record.
That spreadsheet — and the inbox around it — is the product Faldaro replaces.
Folders group forms. Forms produce submissions. That's the whole model.
An insurer configures a Policies folder and a Claims folder. A support desk configures Tickets. Neither waits on a developer, because nothing in Faldaro is specific to a business domain — the platform takes the shape of whatever arrives.
What makes it an intake platform
Three laws no form builder keeps
Each is a property of the architecture, not a feature on a list — and each is checkable in behaviour before you commit anything.
-
The outside world is never a seat.
Submitters, brokers, approvers, signers and portal users cost nothing and are never metered. Submissions are never capped or billed by count on any plan — a fifty-person organization collects from fifty thousand. You pay for your team, never your audience.
-
The server owns the truth.
Every number is computed on the server on every save and every read — a browser cannot send a total, and a payment request has no field an amount could ride in. Published versions are immutable, every record keeps the version it was filled against, and the audit log is append-only because the database refuses to rewrite it.
Builder, logic & calculations Workflows Documents & payments Reports & datasets Security
-
AI works with a badge, not a master key.
The assistant, the standing agents and the MCP server act with exactly the permissions of the person or key behind them — bounded by the database, not by prompt engineering — with no delete tools and no credentials of their own. What a stranger typed arrives marked as data: the assistant cannot change anything in a turn that has read it, agents work inside fences of their own, and over MCP the marking reaches your client’s model intact.
An agent that works the queue, not a chatbox that describes it
Ask for a form and the assistant builds the draft, wires the logic and takes you there. Leave a standing agent on a form and it works what arrives — with exactly the permissions you granted, every step shown, and no delete tools, admin tools or credentials of its own. The agent proposes; you dispose.
-
Import a PDF as a fillable form
A working, editable draft — not a screenshot.
-
Prefill from a document
Matching fields fill themselves for your review.
-
Plain English to a filter
“Unpaid claims over $5,000” becomes the exact query.
-
Reports on demand
Describe the report; refine it in the builder it seeds.
Records that travel
A submission isn’t filed to be forgotten. It becomes a card someone drags, a status a submitter tracks, an approval decided from an inbox, a chart on someone’s site — each behind its own revocable link that carries the projection and never the data.
-
A board you can drag
The same records as a table, a board, a calendar or cards. The board’s columns are your workflow’s own states — dragging a card takes the exact move the record page offers, every server-side rule intact, and a drop the rules withhold says why.
-
“Track your request”, per record
Mint a status link and the submitter watches their own record move — stage, reference number, last update, and nothing else. Drop {{status_link}} into a confirmation email and every record ships with the package-tracking experience.
-
Charts that leave the building
Share a grouped report as a live read-only page, embed the chart in any site, or schedule it as a daily or weekly email digest to people who never log in. Aggregates travel; individual records never do.
-
A portal from just an email
Submitters see all their records in one place with nothing but their address: a secure link, mailed to the mailbox itself, listing each record’s live status. You choose the one field that identifies them — nothing else ever matches.
-
Publish a form as a template
One link makes your form’s design cloneable by anyone — fields, rules and workflow travel; your data, datasets and integrations never do. The clone lands in their workspace, not yours.
-
Approvals from an inbox
A workflow action mails each approver their own approve/decline link — no account, no login. You choose which move each verdict takes and exactly which fields they see; the decision lands on the record with a name, comment and timestamp.
Boards, tracking links, approvals, shared reports, the portal and templates — all of it on every plan, spelled out on the records page.
Built the other way round
Form builders are genuinely good at collecting answers. Work-management tools are genuinely good at work that stays inside the company. Faldaro is built for the work that arrives from outside it — the public form is the front door, and what walks through is worked, not exported.
| Form builders | Work-management tools | In Faldaro | |
|---|---|---|---|
| The person who submits | A metered response. | A seat, or a guest with a login someone had to create. | Never a seat and never metered — a tokenized link to fill, a tracking page to watch, an approval or signature taken from their own inbox. |
| The total | Computed in the browser; whatever arrives is stored. | A formula in a grid, editable by anyone with the sheet. | Recomputed by the server on every save and every read. A browser cannot fabricate a number. |
| The submission | A row you export. | A record, once someone with a seat has keyed it in. | A record from the first second — with a state machine, an owner, a deadline and an audit trail, minted by the stranger who submitted it. |
| The form itself | Edited in place, under responses already collected. | A view over the table. | Published as an immutable version. Every submission keeps the definition it was filled against. |
The first two columns describe how each category usually works, not any one product — check yours. Underneath Faldaro's: tenant isolation enforced by the database, immutable published versions, an append-only audit log. Each claim is checkable in behaviour, spelled out on the security page.
Built to be reviewed
Security you can verify in the design
Every control here is a property of the architecture, not a setting — and each is spelled out where a reviewer can check it.
- Tenant isolation enforced by PostgreSQL Row-level security; the service refuses to start without it.
- An append-only audit log Update and delete revoked from the application role.
- Immutable published versions Every record keeps the definition it was filled against.
- Single sign-on with your provider OIDC on Enterprise; passkeys on every plan.
- Retention you can prove Scheduled purges, each one recorded.
- Public links that are opt-in and revocable Tokenized, throttled, every refusal an identical not-found.
Your first five minutes
Leave with a door open, not a trial
No demo call, no sandbox tour, no imported sample data pretending to be yours. The first session ends with the outside world able to send you something — and the first thing it sends, worked.
-
1 Say what arrives
Sign up — no card — and tell the agent what the outside world sends you: “claims from policyholders, with an estimate and a review step.” Or upload the PDF you make people send you today. Either way, a working, editable draft appears in the builder. 18 templates, if you would rather start from one.
-
2 Make it yours
Adjust the fields on the canvas, watch the logic react in the preview, name the states work moves through. Publishing creates version one — immutable from that moment, like every version after it.
-
3 Open the door
Issue the public link and send it to anyone. No account on their side, never a seat on yours — and the first thing that arrives is not a row but a record: values the server computed, a state to move it through, a tracking link for whoever sent it, an audit trail already started.
Try it on your own document
Drop the form you make people send you
The intake sheet, the application, the claim form you still email as a PDF — drop it here and watch it come back as a working draft, no account required. Sign up and the agent builds the real thing from the whole document: computed totals, logic, workflow and a publishable link.
The converter also lives on its own page: PDF to online form. Or start from a free template with the workflow already built.
— the form you make people print, the intake sheet, the application —
and watch it come back as a working draft. PDF or photo, up to 5 MB.
Reading your document…
Bigger documents take longer — this can run for a minute or two.
A draft, from your own document — fields and choices included. Signing up (free) lets the agent build the real thing from the whole document: it also reads a fillable PDF's own field definitions, drafts computed totals, logic and workflow, and hands you a publishable link — all editable in the builder.
Or watch the whole run
Forty-five seconds, no signup: a PDF becomes a form, a stranger submits, the server computes the total, and the record routes itself to review. Every scene is the product as shipped — nothing mocked, nothing sped past.
A looping demo of Faldaro. An agent reads a claim-intake PDF and turns it into a real, editable form; wires the estimate calculation and its conditional rules, validated against the form's own fields before saving; adds a workflow that routes any claim over $10,000 to risk review; a submitted claim is priced at $12,400 by the server and stamped with the reference CLM-2026-0147; and the phrase “unpaid claims from July over $5,000” compiles into an exact submissions filter. Throughout, the agent acts with your permissions, has no delete tools, and saves nothing until you publish.
The next thing that walks in could be the first one you never export
Describe what arrives — or upload the PDF you use today — and open the door in the same sitting. Free forever: unlimited forms, ten thousand submissions a month, AI credits included.
No card required.