The Pipefy alternative for intake that starts outside
Pipefy is genuinely good at what it is for: orchestrating internal processes — finance, HR, procurement, IT — through no-code pipes, automations, portals and AI agents, across a whole company. If the process is the product and the form is how work enters it, it may well be the right choice. Teams come here when the front door is the hard part: the people sending work are strangers, the form carries a price, and partner firms need to work through it without becoming users of your account.
The usual triggers
Three reasons people search for this page
Not adjectives — each one is a difference in mechanism, and each is checkable in behaviour before you commit anything.
-
The front door
A process platform starts from the pipe and treats the form as the way a card gets created. Faldaro starts from the other end: the public form is the most designed part of the product — tokenized, revocable links; every refusal an identical not-found; throttles and an optional captcha; translations served one locale at a time; a tracking link per record.
-
The price inside the form
When intake carries a quote, a fee or an eligibility score, the figure has to be one nobody can type. Faldaro evaluates every formula on the server on every save, stores it apart from what was submitted, and never sends the formula text to the public page — so the form is not an oracle for the pricing behind it.
-
Partners as organizations
Brokers, agencies and franchisees are not users of your account in Faldaro — they are organizations of their own. Share a form or folder with one and its people submit through it on their own seats, their records isolated from yours and from each other by PostgreSQL row-level security.
The public surface is described in full in the public forms guide, partner organizations in partner sharing, and the category-level comparison on why Faldaro.
Behind the door
Still a process, just not a separate one
The record that arrives is the record that moves. States, deadlines, approvals, documents and signatures all hang off the one submission.
-
Transitions are default-deny
A move that names no privilege still requires one, so the easiest thing an author can do is also the safe thing. Deadlines fire only the one transition their author named.
-
Effects run after the move commits
Notifications, documents and webhooks run once the state change is saved, so an unreachable mail server cannot un-move a record, and nothing announces a move that did not happen.
See it end to end on the approvals page, or start from the project request template, which ships with its workflow.
Switching
Moving is an afternoon, not a project
The start form rebuilds itself, the phases become states, and the history arrives as records.
-
1 Rebuild the start form
Describe the request to the AI assistant, or hand it the PDF people fill in today, and it builds an editable draft — fields, conditions and calculations together.
-
2 Draw the phases as states
Each phase of the pipe becomes a workflow state, and each move a named transition with its own privilege, conditions and actions — notify, generate a document, request a signature or approval, call a webhook.
-
3 Bring the cards
Export the history as CSV and import it: columns map to fields by header, states and reference numbers come across, and every imported record is marked as imported in the audit log. Nothing replays.
Fair questions
Does Faldaro have a kanban view like a pipe?
Yes. A form’s submissions can be viewed as a table, a board with one column per workflow state, a calendar or cards. Dragging a card on the board takes the ordinary transition, so the same privileges, conditions and actions apply as from the record page — the board cannot skip a rule.
Do requesters need an account to follow their request?
No. Each record can have a status link showing its state, its reference number and its timestamps — never its field values. Submitters can also open a portal of all their own records through a magic link mailed to the address they gave, so possession of the mailbox is the credential.
We need approvals from people outside the team.
An approval request mails each approver a link; they decide from their inbox with no account. The verdict fires the transition the workflow named when the request was created, and an expired request can never read as consent.
What does the free plan include?
Unlimited forms, ten thousand submissions a month, the same logic and calculation engine and workflows as every paid plan, public links, PDF documents, email notifications, and payment collection with a three percent platform fee. The pricing page lists exactly what each tier adds.
Build the front door first
The free plan includes unlimited forms, ten thousand submissions a month and the same engine and workflows as every paid plan — and nobody who submits or approves is ever a seat.
No card required.