ADA ERA
Provenance unknown Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: not determined
by ERA a.s. · www.era.aero
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.
ADA ERA at a glance
- Vendor
- ERA a.s.
- Headquarters
- Not stated on the vendor’s pages as of 17 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 17 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 17 Nov 2026
- Panel verdict
- ERA a.s. how scores are made
- As of
- Vendor pages captured 17 Nov 2026; evaluated by the panel 19 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
ERA a.s. (era.aero) sits in this bench's workflow management category, but the only captured public page — the vendor homepage, captured 17 Nov 2026 — lists product names for air traffic management and military systems (IXO, ERIS-ATM, MSS-5, VERA-NG, MASTERCARE among them) and nothing more. On that evidence, no weighted verdict could be computed: each of the seven criteria — process design, integrations and connectors, run reliability, governance and audit, hosting and portability, sovereignty, pricing transparency — was rated "no public information." There was nothing for the judges to split on, and the flagged split list came out empty. The strongest thing the page offers a buyer is the product list itself; weakest is every operational question a workflow buyer asks — we found no public information on a process designer, connectors or an API, failure handling and execution history, SSO and audit trails, hosting and export, or the contracting entity and subprocessors, and no prices, tiers or billing units appear either. Every substantive question goes to the vendor in direct dialogue.
Speaks for it
- names specific air traffic management products on the captured page, including IXO, ERIS-ATM, MSS-5 and MASTERCARE
- names specific military products on the captured page, including VERA-NG, EW-SIM and LAPDIS
- identifies the vendor plainly: ERA a.s., website era.aero
Held against it
- we found no public information on a process designer, forms, approval steps or versioning of a running process
- we found no public information on connectors, an HTTP or webhook step, or a public API
- we found no public information on retries, error paths, execution history, alerting or a status page
- we found no public information on user roles, SSO, credential storage, separate environments or an audit trail
- no sovereignty attributes are on record, with no public information on the contracting entity, execution or log storage, or subprocessors
Best for
- You are sourcing systems for air traffic management or military use and want a named vendor with a published product list to open a direct enquiry.
- You are building a category longlist and need only vendor identity and product names at this stage.
- Your evaluation runs through a formal questionnaire to the vendor, and you need the product names to structure it around.
Avoid if
- You are buying a general business workflow platform for forms and approvals — the captured page presents air traffic management and military products, and we found no public information on a business workflow suite.
- You must shortlist from public documentation alone, with no room for a vendor questionnaire — ask the vendor: the public pages we read do not show it
- Your procurement cannot open without a completed sovereignty file — the record here carries product names and no sovereignty attributes.
The scores
Too little public evidence to rate — fewer than 1 captured source or 3 proven facts — so no star rating is shown. The panel's reasoning is below.
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 — No human steps at all: neither forms nor approval steps, only machine-to-machine automation.
3 — A visual builder with branching and a simple approval or form step.
5 — A visual designer with conditions and parallel paths, forms and approval steps assigned to roles or groups, and deadlines or reminders for open tasks.
8 — BPMN 2.0 modelling or an equivalent documented notation, versions of a process kept with running instances on their original version, 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 not rated — no public information
The only captured page lists product names for air traffic management and military use, and nothing on process modelling, forms, approval steps or versions of a running process. We found no public information on how a process would be designed, how approvers and substitutes are set, or what happens to cases in flight when the process changes. 1
The Integration Engineer not rated — no public information
We found no public information on process design, forms or approvals; the one captured page is a list of product names for air traffic management and military systems, with no description of a visual designer, a notation, approval steps or versioning. 1
The Operations Analyst not rated — no public information
The only captured page is the vendor homepage, which lists product names such as IXO, ERIS and MASTERCARE and nothing about a process designer, forms or approval steps. We found no public information on how processes would be modelled here. 1
The Head of IT not rated — no public information
The captured page gives only lists of air traffic management and military product names, and I found no public information on a visual designer, BPMN, forms, approvals, deadlines or process versioning. A name list is not something I can judge a design capability from. 1
The Data Protection Officer not rated — no public information
The only captured page lists product names for air traffic management and military systems, and I found no public information on a process designer, forms, approval steps with roles or substitutes, or versioning of a running process. The level of process modelling cannot be assessed from this evidence. 1
The Skeptic not rated — no public information
The only captured page is a listing of air traffic management and military product names such as IXO, ERIS-ATM, MSS-5 and VERA-NG; we found no public information on a process designer, forms, approval steps or process versioning. 1
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 catalogue of connectors to common SaaS tools, or webhooks and an HTTP step to call other systems.
5 — Named connectors with their triggers and actions documented, including Microsoft 365 or Google Workspace, a generic HTTP/REST step with inbound webhooks, and an API to start or query workflows.
8 — Connectors to an ERP or accounting system common in DACH (e.g. SAP, DATEV, Microsoft Dynamics), 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, 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 not rated — no public information
We found no public information on connectors, an HTTP or webhook step, a documented API, or any way to reach systems behind our firewall. The capture contains only product-name listings. 1
The Integration Engineer not rated — no public information
We found no public information on connectors with documented triggers and actions, a generic HTTP or webhook step, custom connectors or an on-premise agent; the captured vendor page lists product names only. 1
The Operations Analyst not rated — no public information
We found no public information on connectors, an HTTP or webhook step, or any API; the single captured page names products and describes no integrations. 1
The Head of IT not rated — no public information
The single captured page contains product names and nothing else; I found no public information on named connectors, an HTTP or webhook step, a public API, or any way to reach systems behind our firewall. 1
The Data Protection Officer not rated — no public information
I found no public information on maintained connectors, an HTTP or webhook step, a public API to start or query workflows, or any way to reach systems behind a firewall. The captured page lists ten product names and nothing further. 1
The Skeptic not rated — no public information
The captured page names no connectors, no HTTP or webhook step and no API; we found no public information on how these products would integrate with anything a company runs. 1
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 runs unattended: the product executes no automated workflows whose runs could fail or be monitored.
3 — Failed runs marked with a notification, and a history of recent executions.
5 — Automatic retries or an error path, an execution log with input and output per step, failure alerts by email or chat, and runtime or rate limits documented.
8 — Configurable retries with back-off and replay of a failed run from the failing step, 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 not rated — no public information
We found no public information on retries, error paths, alerting, execution history or a status page. The captured page gives no facts about what happens when an automated step fails. 1
The Integration Engineer not rated — no public information
We found no public information on executions, retries, error paths, run history or a status page; the captured page names products but says nothing about how anything runs or fails. 1
The Operations Analyst not rated — no public information
Nothing on the captured page describes execution history, retries, alerting, runtime or throughput limits, or a status page. We found no public information on run reliability. 1
The Head of IT not rated — no public information
I found no public information on retries, error paths, alerting, execution history, runtime limits or a status page — the captured page stops at product name lists. 1
The Data Protection Officer not rated — no public information
The captured page describes no retries, error paths, alerting, execution history, runtime or throughput limits, or status page. I found no public information on what happens when a step fails, so run reliability cannot be assessed. 1
The Skeptic not rated — no public information
We found no public information on workflow execution, retries, error handling, execution history or monitoring; the capture contains product names only and no operational detail of any kind. 1
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 (BetrVG § 87 (1) 6), so what the trail captures matters to a works council.
0 — No user management: one account per person or one shared login, with no team workspace.
3 — Admin and member roles with shared team folders or workspaces.
5 — Role-based permissions per workflow or folder, SSO via SAML or OIDC, credentials stored encrypted and usable without being revealed, and an audit log of workflow changes.
8 — Separate development, test and production environments with a publishing approval, SCIM provisioning, external secret stores supported, payload redaction or logging 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 not rated — no public information
We found no public information on user roles, SSO, credential storage, separate environments or an audit trail. As the person who releases invoices, I see no evidence of what an approval record would capture, which is what a works council would ask me first. 1
The Integration Engineer not rated — no public information
We found no public information on roles and permissions, single sign-on, credential storage, separate environments or an audit trail; the captured page carries only product name lists. 1
The Operations Analyst not rated — no public information
We found no public information on user roles, SSO, credential storage, environments or an audit trail; the captured page gives no detail beyond product names. 1
The Head of IT not rated — no public information
My core questions — SSO, separate test and production environments, an inventory of workflows with owners, and an exportable audit trail — are all unanswered, because I found no public information on user management, credential storage or logging. The captured page lists only product names. 1
The Data Protection Officer not rated — no public information
I found no public information on roles and permissions, SSO, credential storage, separate environments with controlled publishing, or an audit trail. In particular there is no public statement of what an execution log retains of the payload or what an approval record would capture about employees — the point a works council will ask me first. 1
The Skeptic not rated — no public information
Nothing captured addresses user management, roles, SSO, credential storage or an audit trail; we found no public information on governance for this vendor. 1
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 — Workflows cannot be exported in any form and live only in the vendor's cloud.
3 — Cloud hosting with the region named, and workflows exportable as a file the same product can import.
5 — An EU cloud region available, workflow definitions exportable as documented JSON or BPMN 2.0, and an API to read definitions and execution history.
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 not rated — no public information
We found no public information on hosting regions, a self-hosted or on-premise edition, engine licences, or export of definitions. The capture is a product-name listing with no hosting or portability facts. 1
The Integration Engineer not rated — no public information
We found no public information on cloud regions, self-hosted or on-premise editions, the engine licence, or export of workflow definitions; the captured page describes hosting for none of the listed products. 1
The Operations Analyst not rated — no public information
The captured page names no hosting regions, self-hosted edition, licence or export format. We found no public information on where the engine runs or whether workflows can leave. 1
The Head of IT not rated — no public information
The captured page names no hosting model, no export format such as BPMN or documented JSON, and no engine licence; I found no public information on a self-hosted edition or any exit path for definitions and history. 1
The Data Protection Officer not rated — no public information
I found no public information on cloud regions, self-hosted or on-premise editions, the engine licence, or export of workflow definitions in any format. The captured page lists product names only. 1
The Skeptic not rated — no public information
The captured page states no hosting regions, self-hosted editions, licence terms or export formats; we found no public information on where the engine runs or whether anything can leave the platform. 1
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 — Proven non-EU throughout: non-EU vendor and contracting entity, execution outside the EU, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist, while an EU contracting entity and EU execution are not shown, or an EU region is an option under a non-EU contracting entity.
5 — EU execution and log storage stated (as standard or selectable) and an EU contracting entity or EU representative, with a data processing agreement; parts of the chain such as AI steps, support access or telemetry may run outside the EU.
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 not rated — no public information
The sovereignty record for this vendor is empty, and the captured page states nothing about the contracting entity, where workflows execute, where logs are stored, or which subprocessors are involved. We found no public information on European sovereignty. 1
The Integration Engineer not rated — no public information
No sovereignty attributes were captured: we found no public information on the contracting entity, where execution and logs would be stored, subprocessors, or the vendors behind any AI steps. 1
The Operations Analyst not rated — no public information
No sovereignty attributes are on record, and the captured page states nothing about the contracting entity, execution location, log storage or subprocessors. We found no public information on European sovereignty. 1
The Head of IT not rated — no public information
No sovereignty attributes are on record and the captured page gives only product names, so I found no public information on the contracting entity, where workflows execute, where logs are stored, or who the subprocessors are. 1
The Data Protection Officer not rated — no public information
I found no public information on the contracting entity, where workflows execute, where execution logs with their payload copies are stored, or which subprocessors — AI model providers included — sit behind any step, and no data processing agreement is shown. The captured page names ten products and states none of this, so the sovereignty picture cannot be established from public evidence. 1
The Skeptic not rated — no public information
No sovereignty attributes are on record, and the capture says nothing about the contracting entity, where workflows execute or which subprocessors sit behind any step; we found no public information on European sovereignty. 1
Pricing transparency
not rated — the vendor publishes no price
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 public "from" price or one tier priced, with the rest on request.
5 — Prices public for each tier with the billing period, the billing unit named and the allowance per tier given.
8 — Every tier priced publicly with its unit defined (what counts as one task or execution), 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 not rated — no public information
We found no public information on prices, tiers, a billing unit or allowances; the captured page lists product names without any pricing. I cannot begin to compute a monthly cost from what was captured. 1
The Integration Engineer not rated — no public information
We found no public prices, tier structure, billing unit or allowances; the captured page lists product names only, with no pricing information on it. 1
The Operations Analyst not rated — no public information
We found no public prices on the captured page — no tiers, billing unit, allowance or overage terms. A buyer cannot compute any monthly cost from what was captured. 1
The Head of IT not rated — no public information
There are no prices, tiers, billing units or allowances anywhere on the captured page, so no monthly cost can be computed from public information; I found no public information on pricing. 1
The Data Protection Officer not rated — no public information
The captured page carries no prices, and I found no public information on tiers, the billing unit and what counts as one, allowances, or overages. A buyer cannot compute any monthly cost from this evidence. 1
The Skeptic not rated — no public information
We found no public prices, tiers, billing units or allowances of any kind; the captured page is a product-name listing with nothing on it that addresses cost. 1
Questions about ADA ERA
Is ADA ERA European?
Not determined: the vendor’s pages as captured do not say where ADA ERA is based.
Where does ADA ERA store data?
Not stated on the vendor’s pages as of 17 Nov 2026.
Does ADA ERA have a free plan?
Not stated on the vendor’s pages as of 17 Nov 2026.
What are the best alternatives to ADA ERA?
As of 18 Nov 2026, the panel rates Camunda (3/5), FireStart (3/5) and Appian (3/5) highest among the other 25 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 Camunda (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: ADA ERA alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 17 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- 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.
- We found no public information on pricing on the pages we read (era.aero). If the vendor publishes it somewhere else, send us the page. Know more? Tell us
- We found no public information on compliance on the pages we read (era.aero). If the vendor publishes it somewhere else, send us the page. Know more? Tell us
- 1 product 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
Sources (1)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.era.aero Checked 17 Nov 2026 Details →