Skip to content

Migrating from Kissflow to DueReason

Kissflow is a low-code BPM platform with a dedicated enterprise approval product. See what one approval step gains from a signed, verifiable grant.

Updated · 8 min read

In short

  • Kissflow is a low-code BPM platform with a dedicated "Approval Workflow Software for Enterprise IT" product page; Kissflow does not publish a single public price list, and third-party figures for it disagree widely, so treat any number you see as [UNVERIFIED] until quoted directly.
  • Its approval step sits inside a configurable process definition with its own form builder and routing, but approving a step there still means a step marked approved inside Kissflow's own process instance - not a signed, independently verifiable object another system can check.
  • DueReason does not replace Kissflow's process builder, its routing rules or its form designer - it answers the one approval question a process step asks, with a signed grant, a hash-chained ledger and an agent-native surface behind the answer.
  • Moving one approval step over does not mean moving the whole process: keep Kissflow for the BPM process you built around it, and add DueReason for the one step that needs a record someone else can verify.

If your team runs approvals inside a Kissflow process - a BPM workflow with a form, configurable routing and an approval step that blocks progress until the right person acts - this walks through what that approval step does today, and what changes if you move just that one step to DueReason.

What Kissflow does today

Kissflow is a low-code BPM (business process management) platform: you design a process as a sequence of steps with a form builder, configure routing rules for who acts on each step, and add conditional logic so later steps branch on earlier answers - including an approval step that blocks the process instance until an assigned person approves or rejects it. Kissflow also maintains a dedicated "Approval Workflow Software for Enterprise IT" product page, distinct from its general BPM product, aimed squarely at approvals as a use case. Kissflow does not publish a single public price list - third-party figures range from roughly $50/workflow/month to $1,500/month for 50 users to $2,500/month for a Basic enterprise plan, depending on the source - so any specific number should be marked [UNVERIFIED] until quoted directly from Kissflow for your plan. Because a Kissflow process is fully configurable, teams run far more than approvals through it - procurement, onboarding, service requests, almost any process with forms and routing.

That breadth is also why an approval step inside it is a feature of the process engine rather than a dedicated object: it is one step type among many a process can have, built to fit whatever workflow you modeled, not a decision with its own identity, signature or lifecycle independent of the process instance that contains it.

What happens after a process step is approved

An approval step in Kissflow blocks the process instance until an assigned person approves or rejects it, then routes the instance to the next step, where later steps, an integration or a person pick up from there. What is not part of that mechanism is a signed, independently verifiable object the next system checks before it acts - the trust sits in the step having been marked approved inside Kissflow's own process instance, the same gap the Pipefy migration guide describes for a card that moves past a stage with no record a downstream system can check on its own. A Kissflow process is also built around routing rules that move an instance between steps inside the platform; nothing in that mechanism is a published, agent-native way to file and wait on a request from outside the process entirely.

The same shape in DueReason

Kissflow's processes are general-purpose, so no single DueReason template is a 1:1 replacement for a whole process - DueReason answers the approval question one step asks, not the rest of the routing around it. Map the step, not the process: if the step you want to move gates spend, Payments and refunds or Vendor onboarding from Settings → Templates cover that shape directly; for a step with no close template match, a custom DueReason action models the same approve/reject question with its own approver group and its own evidence field in place of the step's form attachment.

Whichever action models the step, once a request is decided DueReason issues a signed, single-use grant bound to the exact payload - the amount, the recipient, the change being requested - which whatever acts next verifies, rather than trusting that the step is marked approved in the right process instance.

What changes, not just what moves

  • A grant the acting system checks, not a step status trusted at the source. DueReason's signed grant is bound to a hash of the exact payload and verified by whatever executes the decision, so a changed amount or target after approval is refused rather than carried out because a step happened to be marked approved.
  • A hash-chained ledger, not a process instance's own activity log. Every step of a request - filed, each answer, what happened after - is a ledger event from the start, checkable on its own without opening the process that hosted the approval step.
  • Evidence built into the action, not a generic form attachment. Kissflow's form builder can attach anything to a process step; DueReason's evidence setting (none, text or document) is narrower by design - built into the action definition itself rather than a generic form builder, so the "must attach the invoice" cases are faster to set up and the decision record always carries exactly what the approver was shown.
  • An agent-native surface, not a step that only advances when routing rules move it. The same actions are reachable from @duereason/sdk, the MCP server, the GitHub Action or the REST API, so a pipeline or an agent can requestApproval() and waitForApproval() without a process instance involved at all.

Moving one approval step over

  1. Pick the one approval step you want to move - not the whole process - and find the closest DueReason template (Payments and refunds, Vendor onboarding) or define a custom action if nothing close exists yet.
  2. Recreate the people assigned to that step as members of the action's approver group, in place of the step's routing rule in Kissflow.
  3. For process instances still started by hand, the console request form replaces reaching the approval step: pick the action, attach whatever the form used to collect, write a reason.
  4. For instances your integrations start automatically, requestApproval() and waitForApproval() from @duereason/sdk (or the no-code webhook recipe if you would rather not write a backend) replace the point where the instance reached the approval step.
  5. Replace whatever reads the step's approved status back into the rest of the process or into a downstream integration with a check of decided.status and a verification of decided.grant before the step that actually acts - the system doing the work should check the grant, not just the step status.

What has no direct equivalent

DueReason has no BPM process builder, no routing engine, and no form designer for arbitrary data capture - it is not a BPM-platform replacement and does not try to be. If the real value you get from Kissflow is the whole process - the steps before and after approval, the routing, the forms - keep Kissflow for that and add DueReason around the one step that needs a signed, independently verifiable decision rather than expecting a native replacement for the process engine itself.

Questions

Does moving to DueReason mean rebuilding our whole Kissflow process?
No. DueReason replaces one approval step at a time, not a whole process. Keep Kissflow for the steps, routing and forms around it, and point the one step that needs a signed, verifiable decision at a DueReason action instead.
Does DueReason do BPM routing and process building like Kissflow?
No, and it is not trying to. DueReason answers one question - is this action approved, by whom, with what evidence - and reaches that answer through @duereason/sdk, the MCP server, the GitHub Action or the REST API, rather than offering a BPM process builder with routing rules.
What does Kissflow cost, compared to DueReason?
Kissflow does not publish a single public price list; third-party figures reported range from roughly $50/workflow/month to $2,500/month for a Basic enterprise plan, so treat any figure as [UNVERIFIED] until quoted directly for your plan. DueReason is free today for one organization with up to five members, all core features included.
Do I need engineering to move one approval step over?
No. Picking the closest template, adding people to its approver group, and filing requests from the console form is console-only setup, the same as reaching an approval step by hand in Kissflow; engineering is only needed once you want an automation or an agent to request approval through the API instead of a person using the form.
Can I self-host instead of using the hosted product?
Yes. Self-hosting runs on one Postgres database and one pre-built image started with Docker Compose, with no process or routing configuration of its own - the same actions, grants and ledger work the same way whether you use the hosted product or run it yourself.

Move one approval step to DueReason

Keep Kissflow for the process around it - point requestApproval() and waitForApproval(), or the console request form, at the one step that needs a signed, verifiable decision.

Create your account

Sources

This guide explains the regulation as we read it; it is not legal advice. Check the official text and your national law, which may add obligations.

Start with DueReason

Create a free account, try it live, or talk to us about your workflow.

Get product updates