Workflow Management
FireStart
EU-Made Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by FireStart GmbH · www.firestart.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
FireStart at a glance
- Vendor
- FireStart GmbH
- Headquarters
- Not stated on the vendor’s pages as of 13 Oct 2026
- Data hosting
- Not stated on the vendor’s pages as of 13 Oct 2026
- Free plan
- Not stated on the vendor’s pages as of 13 Oct 2026
- Panel verdict
- The AI panel rates FireStart 2/5, the mean of 6 judges. FireStart is a BPMN 2.0 workflow platform from FireStart GmbH, Linz, Austria, with public starting prices of Prozessmodellierung ab 390 €/Monat and Prozessautomatisierung ab 830 €/Monat, and an unpriced enterprise tier. how scores are made
- As of
- Vendor pages captured 1 Oct 2026 to 13 Oct 2026; evaluated by the panel 15 Oct 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
FireStart is a BPMN 2.0 workflow platform from FireStart GmbH, Linz, Austria, with public starting prices of Prozessmodellierung ab 390 €/Monat and Prozessautomatisierung ab 830 €/Monat, and an unpriced enterprise tier. It is strongest on process design, where scores sit at 7: BPMN 2.0 modelling, a versioned process library with publishing approvals, no-code forms with required fields and validation, external submission by link without login, and escalations, deadlines and deputies documented. Hosting and portability follows at 6-7, led by an on-premise edition running completely in the customer's data center, an air-gap mode without internet, and a hybrid option. Run reliability is the weak point at 1-2: we found no public information on retries, error paths or execution history, and the only monitoring content is an AI alert-clustering use case for the customer's own IT alerts. Pricing transparency sits at 3, with the billing unit undefined. Sovereignty scores spread 2-4: EU hosting and Made in Austria are claimed throughout, but no subprocessor list with locations is published and the contracting entity's jurisdiction is not confirmed on the captured pages.
Speaks for it
- BPMN 2.0 modelling, a versioned process library with publishing approvals, and escalations, deadlines and deputies are documented
- No-code forms with required fields and validation are usable by link by customers and partners without login
- An on-premise edition runs completely in the customer's data center, with an air-gap mode and a hybrid option
- A role lifecycle of request, approval, auto-provisioning, regular review and clean deprovisioning is described
- AI workflows are stated to run with the customer's own AI model
Held against it
- Run reliability scores sit at 1-2, with no public information on retries, error paths, execution history or a status page
- Pricing transparency scores sit at 3, with the billing unit undefined and the public calculator estimating savings rather than the monthly invoice
- Integrations and connectors scores sit at 4, with the 65+ connectors and over 500 integrations count naming no system, trigger or action
- Governance and audit scores sit at 3-4, with no public information on SSO, credential storage, execution-data retention or what the audit trail records about users
- Sovereignty scores spread 2-4: no subprocessor list with locations is published, and the captured pages call the cloud both EU data centers and the German cloud
Best for
- You need an approval backbone for finance processes — invoice approval, payment runs, budget approvals — with escalations, deadlines and deputies
- Your organization must run the engine in its own data center, including air-gapped operation without internet
- You want customers and partners to submit requests through forms shared by link, without login
- You want AI workflow steps to run on your own AI model
Avoid if
- You need documented behaviour when a workflow step fails — retries, error paths, searchable execution history — before anything runs unattended; the pages' only monitoring content is an AI alert-clustering use case for IT alerts
- You depend on named connectors with documented triggers and actions, since the public claim is a count that names none
- You want to evaluate before any sales contact, since trial access is set up after a short initial call
The scores
| Criterion | Panel median |
|---|---|
| Process design, forms & approvals | 3.5 of 5 |
| Connectors, API & on-premise reach | 2 of 5 |
| Execution, error handling & monitoring | 0.5 of 5 |
| Governance, credentials & audit trail | 2 of 5 |
| Hosting options & portability | 3.5 of 5 |
| European sovereignty | 2 of 5 |
| Pricing transparency | 1.5 of 5 |
Process design, forms & approvals
Show reasoningHide reasoning
How this is scored
Modelling the process people take part in: a visual designer or BPMN, forms, approval steps with roles and substitutes, deadlines and escalation, and versioning of a process that is already running — judged on whether a business owner can change a process without breaking the instances in flight.
0 — Linear trigger-action chains only; no human steps, no forms and no statement on approvals or roles.
3 — A visual builder with branching and a simple approval step, but approvers are named individuals rather than roles, there are no deadlines or escalation, and changing a process has no versioning.
5 — A visual designer with conditions and parallel paths, built-in forms, approval steps assigned to roles or groups, deadlines with reminders, and versions of a process kept with the running instances on their original version.
8 — BPMN 2.0 modelling or an equivalent documented notation, substitutes and escalation chains, multi-stage approvals with four-eyes rules, forms in German with validation and file upload, a task inbox for participants, and a test or simulation mode before publishing.
10 — The process is a governed asset: version history with diff and rollback, migration of running instances to a new version documented, process analytics on cycle time and bottlenecks per step, and the design documented well enough that a business team can maintain it without the vendor.
The Process Owner
BPMN 2.0 modelling, a versioned process library with approvals before publishing, no-code forms with required fields and validation, and explicit escalations, deadlines and deputies cover exactly what my invoice approvals need, approvers on holiday included. I found no public information on a task inbox for participants, a test or simulation mode before publishing, or how a new process version treats the requests already in flight, which is what keeps this short of the top. 2 6 5 1
The Integration Engineer
The captured pages document BPMN 2.0 modelling with a versioned process library, no-code forms with required fields and validation, external submitters via link without login, and approvals with escalations, deadlines and deputies — the core of a serious approval platform. I found no public information on a test or simulation mode before publishing, four-eyes rules, or what happens to running instances when a process is changed, which keeps this just below the fully governed picture. 2 5 6
The Operations Analyst
BPMN 2.0 models, no-code forms with required fields and validation, human-in-the-loop approvals, and escalations, deadlines and deputies are all stated on the pricing and form-builder pages — the shape my invoice-approval runs need. A versioned process library and export are named, though we found no public information on migrating running instances, a task inbox for participants, four-eyes rules, file upload on forms, or a test mode before publishing. 2 5 6
The Head of IT
BPMN 2.0 modelling, escalations, deadlines and deputies, and no-code forms with required fields and validation cover most of what I demand before a department builds anything. I found no public information on four-eyes rules, file upload, a participant task inbox, or a simulation mode before publishing, and the versioned process library is claimed without saying whether a change leaves running instances on their original version. 2 5 6
The Data Protection Officer
BPMN 2.0 modelling, a versioned process library, escalations, deadlines and deputies, and no-code forms with validation and external submission by link are all evidenced, which is a serious approval backbone. What the trail would show a works council is thinner: we found no public information on four-eyes rules, a task inbox for participants, a test or simulation mode before publishing, or how running instances are handled when a process version changes. 2 5 6
The Skeptic
BPMN 2.0 modelling with a versioned process library, publishing approvals, human-in-the-loop approvals, escalations, deadlines and deputies are named, and forms are no-code drag-and-drop with required fields, validation and external use by link without login. We found no public information on four-eyes rules, a participant task inbox, simulation before publishing, or how a process version change treats instances already running. 2 5 6
Connectors, API & on-premise reach
Show reasoningHide reasoning
How this is scored
Reaching the systems a European company actually runs: maintained connectors judged by name rather than count, a generic HTTP and webhook step, custom connectors, and a way to reach systems behind the firewall without opening it.
0 — No connectors beyond email, and no API or webhook step.
3 — A large connector count on a logo wall, with no statement of which actions each supports or who maintains them, and no generic HTTP step.
5 — Named connectors with their triggers and actions documented, including Microsoft 365 and at least one ERP or accounting system common in DACH (e.g. SAP, DATEV, Microsoft Dynamics), a generic HTTP/REST step, inbound webhooks, and a documented API to start and query workflows.
8 — Custom connectors buildable from an OpenAPI description or code, an on-premise agent or self-hosted runner reaching internal databases and file shares, SOAP and database steps, OAuth handled per connection, and connector maintenance ownership (vendor, partner or community) stated.
10 — Integration is engineered: a versioned public API with a deprecation policy, connector changelogs, rate limits per connector published, event-driven triggers rather than polling where the source allows it, and the vendor maintaining the German-market connectors (DATEV, SAP, ELO or d.velop) itself.
The Process Owner
The claim is 65+ connectors and over 500 integrations, yet no connector is named, no triggers or actions per connector are documented, and I found no public information on a generic HTTP or webhook step or a documented API. A genuine on-premise edition with full access to the installation for custom integrations is the one solid answer for reaching systems behind our firewall. 2 7 8
The Integration Engineer
The connector story is a count — "65+ Konnektoren, über 500 Integrationen" — with no named system, no documented triggers or actions, no maintenance ownership, and I found no public information on a generic HTTP or webhook step or a documented API to start and query workflows. The one thing I can wire with confidence is the on-premise edition running completely in the customer's data center with full access to the installation for custom integrations, which reaches internal systems without opening the firewall — real reach, but documented as a place, not as steps. 2 7 8
The Operations Analyst
The only figure is '65+ Konnektoren, über 500 Integrationen' — a count with no named systems, no documented triggers or actions, and no statement of who maintains them, and we found no public information on a generic HTTP or webhook step or a public API. The on-premise edition running completely in the customer's data center, with full access to the installation for custom integrations, is the one evidenced way to reach systems behind the firewall. 2 7 8
The Head of IT
A connector count of "65+ Konnektoren, über 500 Integrationen" with no named connectors, no documented triggers or actions, and no maintenance ownership gives me nothing to inventory or hold anyone to. The on-premise edition running inside our firewall with full installation access is genuine reach into internal systems, but I found no public information on a documented API, inbound webhooks, or a generic HTTP step. 2 8
The Data Protection Officer
The captured pages give a count — "65+ Konnektoren, über 500 Integrationen" — without naming a single connector or documenting its triggers and actions, and we found no public information on a generic HTTP step, inbound webhooks, or a documented API to start and query workflows. The genuinely strong element is the on-premise edition running inside the customer's firewall with full installation access for custom integrations, so internal systems are reachable without opening anything. 2 7 8
The Skeptic
"65+ Konnektoren, über 500 Integrationen" is a count with no connector named, no triggers or actions documented and no maintenance ownership stated; the on-premise pages promise full installation access for custom integrations behind the customer's own firewall, which is the only genuine reach behind the firewall shown. We found no public information on a generic HTTP or webhook step, or on a documented API to start and query workflows. 2 7 8
Execution, error handling & monitoring
Show reasoningHide reasoning
How this is scored
What happens when a step fails at 3 a.m.: retries, error paths, alerting, an execution history someone can search, limits on runtime and throughput, and a status page that admits incidents.
0 — Nothing stated about failed runs; an error stops the workflow silently.
3 — Failed runs are marked and an email is sent, but retries are manual, execution history is short or undocumented, and runtime and throughput limits are unstated.
5 — Automatic retries with configurable back-off, an error path or error workflow, a searchable execution log with input and output per step, failure alerts by email or chat, and runtime, payload and rate limits documented.
8 — Replay of a failed run from the failing step, idempotency guidance, queueing and concurrency controls, execution history retention stated per plan, monitoring exportable to the customer's own tools, and a public status page with incident history and an uptime commitment.
10 — Operations are designed for production: an SLA with service credits, horizontal scaling or high-availability setup documented for self-hosted installs, dead-letter handling, end-to-end tracing across workflows, and post-incident reports published.
The Process Owner
I found no public information on retries, error paths, execution history, runtime or throughput limits, or a status page — nothing about what happens when a step fails overnight. The captured pages cover AI clustering of monitoring alerts, which concerns IT alerts and not the fate of a failed workflow run, and beyond an always-available marketing claim there is nothing here to approve an invoice release on. 9 10 13
The Integration Engineer
Everything captured about monitoring is the AI alert-clustering solution — clustering, correlation, root cause, with claims of -70% alert volume and -50% MTTR — which is a product offering for IT alert triage, not the engine's behaviour when a workflow step fails. I found no public information on retries, error paths, execution history, replay from the failing step, runtime or payload limits, or a public status page, so a failed run at 3 a.m. is entirely undocumented. 9 10
The Operations Analyst
We found no public information on retries, error paths, a searchable execution history, or documented runtime and throughput limits — the captured pages say nothing about what happens when a step fails overnight. The AI alert-clustering solution claims to group monitoring alerts and cut alert volume and MTTR, but that is infrastructure alerting rather than workflow run failure handling, and we found no public information on a status page or an uptime commitment. 2 9 10
The Head of IT
Nothing on what happens when a step fails at 3 a.m.: I found no public information on retries, error paths, searchable execution history, runtime or throughput limits, or a status page. The alert-clustering pages describe an AI use case for the customer's own monitoring, not the platform's failure handling, and "always available" on the cloud page is the only availability statement I could find. 9 13
The Data Protection Officer
We found no public information on what happens when a step fails: no retries, no error paths, no searchable execution history with inputs and outputs per step, no stated runtime or throughput limits, and no status page. The AI alert-clustering pages describe clustering monitoring alerts as a customer use case, and the cloud pages mention automatic updates — neither evidences the platform's own behaviour on failed runs. 9 10 13
The Skeptic
The only monitoring evidence is AI clustering and root-cause analysis of the customer's IT alerts — a product use case, not behaviour when a workflow step fails. We found no public information on retries, error paths, execution history and its retention, runtime or throughput limits, incident disclosure or a status page. 9 10
Governance, credentials & audit trail
Show reasoningHide reasoning
How this is scored
Keeping automation from becoming shadow IT: roles and permissions, SSO, where connection credentials are stored, separate environments with controlled publishing, an audit trail of changes and approvals, and what the execution log retains of the payload. An approval record is also a record of employees' behaviour, so what the trail captures matters to a works council.
0 — Single-user accounts or one shared login; no roles, no audit log and no statement on credential storage.
3 — Admin and member roles and shared team folders, but credentials are visible to anyone who can edit a workflow, there is no audit log, and execution payloads are kept without a stated period.
5 — Role-based permissions per workflow or folder, SSO via SAML or OIDC, credentials stored encrypted and usable without being revealed, an audit log of workflow changes, and the retention period of execution data stated.
8 — Separate development, test and production environments with a publishing approval, SCIM provisioning, external secret stores supported, payload redaction or log-off per workflow, configurable execution data retention, and the audit trail exportable — with the fields it records about users described.
10 — Governance a works council and an auditor can both sign off: field-level masking of personal data in logs, delegated administration per department, a central inventory of every workflow and connection with its owner, certifications published (ISO 27001 or SOC 2), and documentation of what the platform records about individual users.
The Process Owner
Permission management and audit trails are explicitly listed, process changes pass through approvals and publishing in a versioned library, and the role lifecycle runs from request through manager approval to clean deprovisioning. I found no public information on single sign-on, where connection credentials are stored, how long execution data is retained, or what the audit trail records about individual users — the first questions our works council will ask. 2 12 8
The Integration Engineer
Permission management and audit trails are claimed by name, and a role lifecycle of request, approval, provisioning and review is described, which is more than a bare single-user picture. But I found no public information on SSO, where connection credentials are stored, separate environments with a publishing approval, or execution-data retention — the captured privacy text covers only newsletter e-mail addresses — and nothing on what the trail records about individual users for a works council to read. 2 3 12
The Operations Analyst
Permission management and audit trails are named as included features, and the roles solution describes a governed lifecycle from request and approval through automatic provisioning, regular review and clean deprovisioning. Beyond those statements we found no public information on SSO, where connection credentials are stored, separate environments with a publishing approval, retention of execution payloads, or which fields the audit trail records about users — the questions a works council asks. 2 12
The Head of IT
Permission management and audit trails are claimed, and the role lifecycle of request, approval, provisioning and regular review is spelled out — more role discipline than most products show. But I found no public information on SSO, separate test and production environments with controlled publishing, where connection credentials are stored, execution-data retention, or an exportable audit trail, and the only compliance evidence is GDPR claims rather than ISO 27001 or SOC 2. 2 12
The Data Protection Officer
Permission management and audit trails are named, publishing runs through approvals, and a role lifecycle of request, approval, provisioning and clean deprovisioning is described — but we found no public information on SSO, where connection credentials are stored, how long execution payloads are retained in the log, or whether payloads can be redacted or masked per workflow. The fields the approval trail records about individual employees, which a works council will ask for, are not described anywhere we could see. 2 12
The Skeptic
Permission management and audit trails are named features, the roles solution documents request, approval, auto-provisioning, regular review and clean deprovisioning, and finance processes are described as audit-proof. We found no public information on SSO, where connection credentials are stored, separate environments with a publishing approval, the retention period of execution payloads, or an exportable audit trail describing what it records about individual users. 2 9 12
Hosting options & portability
Show reasoningHide reasoning
How this is scored
Where the engine runs and whether the workflows can leave: cloud regions, self-hosted or on-premise editions, the licence of the engine, and export of workflow definitions in a format another tool or a later version can read.
0 — Cloud-only with no stated region, and no export of workflow definitions.
3 — Cloud-only with a region named, and an export that produces a proprietary file only the same product can import.
5 — An EU cloud region selectable, workflow definitions exportable as documented JSON or BPMN 2.0, and an API to read definitions and execution history for backup.
8 — A self-hosted or on-premise edition with its system requirements documented, workflow definitions versionable in Git, the engine's licence published, and a documented migration path between cloud and self-hosted in both directions.
10 — The customer owns its automation: an open-source or source-available engine, definitions in an open standard executable elsewhere, air-gapped installation supported, and a stated exit process that hands back definitions, credentials metadata and execution history in documented formats.
The Process Owner
There is a real on-premise edition running entirely in our data center, claimed to work air-gapped without an internet connection, alongside an EU-hosted cloud and a hybrid option, with all data staying in our own infrastructure. I found no public information on system requirements for self-hosting, the engine's licence, Git-based versioning of definitions, or a documented migration path between cloud and on-premise, and export appears only as 'export and process documentation' without a stated format. 1 2 7 8 13
The Integration Engineer
The deployment choice is real: cloud with automatic scaling and updates, on-premise entirely in the customer's data center, a hybrid enterprise option, and an air-gap mode that runs without internet connection. Portability is thinner — an export and process documentation feature is listed but its format is unstated, and I found no public information on system requirements for on-premise, the engine's licence, Git versioning of definitions, or a documented migration path between cloud and on-premise. 1 2 7 8 13
The Operations Analyst
An on-premise edition runs completely in the customer's data center and is described as working without internet for air-gap environments, alongside cloud and hybrid options — real portability of the engine itself. The captured pages give different wordings for the cloud's location, calling it both EU data centers and the German cloud, export is named only for process documentation without a format, and we found no public information on system requirements, the engine's licence, or a documented migration path between cloud and on-premise in either direction. 2 7 8 13
The Head of IT
An on-premise edition that runs entirely in our data center, is claimed to work air-gapped without internet, and comes with a hybrid option and full installation access is the exit route I insist on, and process export and documentation is listed with the modelling tier. However the export format is never named, and I found no public information on the engine's licence, documented system requirements, Git-versionable definitions, or a migration path between cloud and self-hosted in either direction. 2 7 8 13
The Data Protection Officer
An on-premise edition running entirely in the customer's data center — air-gap capable, hybrid option, customer-decided storage and backup — plus BPMN 2.0 models with export and documentation is a solid base for keeping the workflow chain on-site. We found no public information on the on-premise edition's system requirements, the engine's licence, Git versioning of definitions, or a documented migration path between cloud and self-hosted in either direction. 1 2 7 8
The Skeptic
EU cloud hosting, an on-premise edition running completely in the customer's data center, a hybrid option and air-gapped operation with all data staying in the customer's infrastructure are documented, and the modelling tier mentions export and process documentation without naming a format. We found no public information on system requirements for self-hosting, definitions versionable in Git, the engine's licence, a migration path between cloud and on-premise in either direction, or an API to read definitions and history for backup. 2 7 8 13
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting entity is, where workflows execute and where execution logs with their payload copies are stored, and who the subprocessors are — including the AI model providers behind any AI steps. Independently sourced by the sovereignty pipeline. A self-hosted edition counts only for the data that actually stays on the customer's servers.
0 — Non-EU vendor and contracting entity, execution location unstated, and subprocessors unnamed.
3 — An EU region offered as an option while the contracting entity is non-EU, or the subprocessor list is absent, or AI steps send data to model providers of unstated location.
5 — EU execution and log storage as standard and an EU contracting entity, but parts of the chain — AI steps, support access, telemetry — are non-EU without an explained safeguard.
8 — EU execution on named infrastructure, EU contracting entity, subprocessor list published with locations including AI providers, a DPA covering execution payloads, and a self-hosted option that sends no workflow data to the vendor.
10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor, AI steps runnable on European or self-hosted models, certification published, and a self-hosted edition that works without any call home.
The Process Owner
Made in Austria and hosted in the EU are claimed consistently, the privacy policy says data does not leave the EU, AI workflows can run on our own AI model, and an on-premise edition keeps everything on our servers. We found no public subprocessor list with locations, no named hosting infrastructure, no data-processing agreement mentioned, and the contracting entity's jurisdiction is not confirmed on the captured pages. 1 2 3 6 8
The Integration Engineer
EU hosting is stated as standard rather than an option, made in Austria and GDPR-compliant are repeated, AI workflows run on the customer's own AI model, and the on-premise and air-gap editions keep data on the customer's own infrastructure. But the contracting entity's jurisdiction is not confirmed on the captured pages, hosting is named only as "EU data centers", and I found no public information on subprocessors — including anything behind the AI features — or a data-processing agreement covering execution payloads. 2 3 7 13
The Operations Analyst
Made in Austria, hosted in the EU and GDPR-compliant appear throughout the captured pages, the privacy policy states the website and services run on EU servers, and AI workflows are said to run with the customer's own AI model. The independent sourcing could not confirm the contracting entity's jurisdiction, ownership or execution-log residency on the vendor's own pages, and we found no public information on subprocessors or their locations. 1 2 3
The Head of IT
EU hosting is claimed consistently, the platform is made in Austria, AI workflows run with the customer's own AI model, and the on-premise edition keeps data on our own infrastructure. Against that, the contracting entity is not confirmed on the captured pages, no subprocessor list with locations is published, and the captured pages describe hosting variously as the German cloud and as hosted in the EU without naming infrastructure. 2 8 13
The Data Protection Officer
"Made in Austria" and EU data centers are claimed on the marketing pages, but the independently confirmed record leaves the contracting entity's jurisdiction, ownership, data residency and every subprocessor unconfirmed, and no subprocessor list with locations is published. The automation features mention "KI-Workflows mit deinem KI-Modell", which is the right shape, yet we found no public information on where the AI steps' models actually run, on a DPA covering execution payloads, or on where the execution log keeps its copy of the data. 2 9 13
The Skeptic
EU hosting is claimed across captures including a privacy-policy statement that data does not leave the EU, the vendor presents as made in Austria, AI workflows run "mit deinem KI-Modell", and the on-premise edition keeps all data in the customer's own infrastructure. The subprocessor list is absent, and we found no public information confirming the contracting entity's jurisdiction, the ownership, certifications, or a data processing agreement covering execution payloads. 1 2 3 8
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the monthly cost of their own processes from public pages alone: what the billing unit is (task, operation, execution, run, user or flow) and what counts as one, the allowance per tier, overage prices, and the cost of premium connectors, self-hosting, environments and AI steps.
0 — No public prices at all; every tier is a sales conversation.
3 — A starting price exists, but the billing unit is undefined or what counts as one task or execution is unstated — the invoice is unknowable.
5 — Tier prices public with the billing unit defined and the monthly allowance given, but at least one commonly needed piece (overage, premium connectors, extra environments, self-hosted licence, AI steps) is unpriced.
8 — Every tier priced publicly with its unit, allowance and limits, overage priced per unit, premium connector and add-on prices listed, self-hosted licensing stated, minimum term and VAT treatment given.
10 — Complete price computability: the monthly cost derivable for a given number of workflows, runs and steps per run, with a published calculator or worked examples, every add-on and overage on a public page, and the effect of loops and retries on the count explained.
The Process Owner
Two public starting prices exist — Prozessmodellierung ab 390 €/Monat and Prozessautomatisierung ab 830 €/Monat — plus an enterprise tier whose 'individual limits' and on-premise option are left unpriced. The billing unit is never defined: I found no public information on what is counted, the allowance per tier, overage prices, or the cost of the self-hosted licence and AI steps, so I cannot compute what my monthly approvals would actually cost. 2 13 11
The Integration Engineer
Two tiers carry public starting prices — Prozessmodellierung "ab 390 €/Monat" and Prozessautomatisierung "ab 830 €/Monat" — while the enterprise tier with on-premise, the unlimited option and custom integrations has no price. The billing unit is never defined: I found no public information on what the monthly price includes per user, process or execution, on allowances, overages, premium connectors, self-hosting licence or AI steps, so a buyer cannot compute their own invoice; the calculator on the site estimates saved effort, not platform cost. 1 2
The Operations Analyst
Two tiers carry public starting prices — 'ab 390 €/Monat' for process modelling and 'ab 830 €/Monat' for process automation — but the billing unit, the monthly allowance and what counts as a task or run are unstated, so I cannot compute what a loop over 5,000 rows would cost. The enterprise tier lists individual limits and an unlimited option without figures, 'you only pay for what you use' names no unit, and we found no public information on overages, premium connectors, self-hosting licences, minimum term or VAT treatment. 2 13
The Head of IT
Two starting prices are public — Prozessmodellierung "ab 390 €/Monat" and Prozessautomatisierung "ab 830 €/Monat" — but the billing unit and what counts as one process or user are undefined, monthly allowances and overage prices are unstated, and the enterprise tier with its "Individuelle Limits, Unlimited-Option" carries no figure. The "you only pay for what you use" phrase on the cloud page does not make the monthly invoice computable from public pages. 2 13
The Data Protection Officer
Starting prices of "ab 390 €/Monat" for process modelling and "ab 830 €/Monat" for process automation are public, but the billing unit — per user, per process, per execution — is never defined, nor the allowance per tier, overage prices, or the cost of the enterprise tier's "Individuelle Limits, Unlimited-Option". A buyer cannot compute the monthly cost of their own processes from these pages alone; the "pay for what you use" scaling claim also gives no unit to count. 2 13
The Skeptic
Two from-prices are public — "ab 390 €/Monat" for process modelling and "ab 830 €/Monat" for process automation — but the billing unit is undefined: nothing states what counts as a process, user, run or step, what the from-price includes, or any allowance, and the enterprise tier is individually quoted. The trial requires an initial call, "you only pay for what you use" names no unit, and the public calculator computes savings rather than the monthly invoice; we found no public information on overage, premium connectors or add-on prices. 2 11 13
European sovereignty — proven facts
0 of 4 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined ⚠ unverified | — | uncited Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined ⚠ unverified | — | uncited Report an error |
| Subprocessors | Not determined | — | uncited Report an error |
Questions about FireStart
Is FireStart European?
Yes. whats-best.ai classifies FireStart as EU-Made.
Where does FireStart store data?
Not stated on the vendor’s pages as of 13 Oct 2026.
Does FireStart have a free plan?
Not stated on the vendor’s pages as of 13 Oct 2026.
What are the best alternatives to FireStart?
As of 15 Oct 2026, the panel rates Tray.ai (3/5), n8n (3/5) and Camunda (2.5/5) highest among the other 16 Workflow Management products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is n8n (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: FireStart alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 1 Oct 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data residency, Legal entity. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 29 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 5 hosting facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 5 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 4 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 4 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 subprocessors facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 support fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 2 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
Sources (13)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.firestart.com Checked 13 Oct 2026 +1 earlier capture: 1 Oct 2026 Details →
- 2 Pricing page www.firestart.com Checked 13 Oct 2026 Details →
- 3 Privacy policy www.firestart.com Checked 13 Oct 2026 Details →
- 4 Legal notice www.firestart.com Checked 13 Oct 2026 Details →
- 5 Process design, forms & approvals — found from sitemap www.firestart.com Checked 13 Oct 2026 Details →
- 6 Process design, forms & approvals — found from sitemap www.firestart.com Checked 13 Oct 2026 Details →
- 7 Connectors, API & on-premise reach — found from sitemap www.firestart.com Checked 13 Oct 2026 Details →
- 8 Connectors, API & on-premise reach — found from sitemap www.firestart.com Checked 13 Oct 2026 Details →
- 9 Execution, error handling & monitoring — found from sitemap www.firestart.com Checked 13 Oct 2026 Details →
- 10 Execution, error handling & monitoring — found from sitemap www.firestart.com Checked 13 Oct 2026 Details →
- 11 Governance, credentials & audit trail — found from sitemap www.firestart.com Checked 13 Oct 2026 Details →
- 12 Governance, credentials & audit trail — found from sitemap www.firestart.com Checked 13 Oct 2026 Details →
- 13 Hosting options & portability — found from sitemap www.firestart.com Checked 13 Oct 2026 Details →