Fujitsu RunMyProcess review

Fujitsu RunMyProcess is a low-code platform for designing workflows, building apps and connecting business systems. Its homepage describes tools for visual process design, governance and deployment across cloud, hybrid and multi-cloud environments. The aim is to coordinate people, data and systems in business processes, rather than automate a single isolated task.

The platform combines a BPMN drag-and-drop designer for multi-lane processes with a WYSIWYG editor for responsive web and mobile apps. Those apps can connect to workflows, while a native NoSQL database provides flexible-schema data storage. Integration options include connectors, REST and SOAP APIs, and secure agents for cloud and on-premise systems. Listed AI services cover document processing, sentiment analysis, text summarization, translation and personally identifiable information detection. Governance and monitoring features include access management, audit logs, versioning, deployment controls and real-time process metrics. That is a broad feature set on paper; the published information does not specify usage limits or technical requirements.

The main strength is breadth. RunMyProcess brings process design, app building, data handling, integrations and governance into one low-code platform. Teams can map multi-lane processes in a visual BPMN editor, then build responsive apps that connect to those workflows. That could reduce the need to assemble separate tools for process modeling and front-end forms, though the published material does not establish how much work that saves.

Its integration approach also covers different environments: the listed options include connectors, REST and SOAP APIs, and secure agents for on-premise systems. That matters for organizations with a mix of cloud and locally hosted software. Deployment across cloud, hybrid or multi-cloud environments is another stated option, not a restriction to one hosting model.

• Process and app design: BPMN workflow editing and a WYSIWYG app editor are both listed.
• Data and AI: A native NoSQL database sits alongside services for document processing, sentiment analysis, summarization, translation and PII detection.
• Oversight: Access controls, audit logs, versioning, deployment management and real-time process metrics are listed as governance and monitoring features.

For buyers looking for process orchestration with governance in scope, that combination deserves evaluation. The available product description does not provide implementation examples or comparative results, so breadth should not be mistaken for proof of fit.

The purchase case is hard to assess because pricing is opaque. The pricing information checked on November 6, 2026, lists a custom quote and no published starting price; monthly and annual terms are also not published. It lists no free plan, and trial availability is not specified. With no public price or plan breakdown, buyers cannot compare the cost with alternatives without contacting Fujitsu for a quote.

The published details also leave important limits unanswered. There are no stated caps for users, workflows, apps, data storage, API calls, connectors or AI processing. The number of available connectors and any limits by deployment type are not published either. That does not mean the platform has no caps; it means buyers need to confirm them before estimating total cost or designing around the service.

The published material names governance and monitoring features but does not explain their plan availability, configuration requirements or additional fees. Pricing confidence is marked low, so even the quote-based summary should be treated as a starting point, not a complete price comparison. Ask for a written quote and a plan-specific list of limits, included integrations, AI allowances and deployment costs before committing.

The available pricing information lists one plan, Custom, with no published monthly or annual price. It describes the offer as quote-based, so there is no public starting price to use for budgeting or compare with another platform. The pricing data was checked on November 6, 2026, and marked low confidence; confirm current terms with Fujitsu before relying on it.

There is no tier jump to calculate: the published information lists no priced tiers beyond Custom. It also lists no add-ons, but that does not establish that optional charges are unavailable. Monthly and annual billing terms are not published, and the data does not specify contract length, user or workflow limits, implementation fees, or what drives a quote.

For procurement, ask Fujitsu to price your expected users, processes, environments, integrations, support, and deployment needs. Request the same scope under monthly and annual terms, plus any setup or overage costs. Without those details, a total-cost comparison remains guesswork.

Treat a move as a process redesign and integration project, not just a software swap. RunMyProcess covers BPMN workflows, responsive apps, a native NoSQL database, connectors and APIs, governance, and deployment across cloud, hybrid, or multi-cloud environments. The published material does not say how workflows, app logic, records, audit logs, or integrations can be exported, or whether Fujitsu provides migration tooling.

Before committing, ask for export formats and access to process definitions, app data, and audit history. Map each workflow, connector, and permission to its replacement, then confirm how existing systems will be authenticated and tested. Get migration scope and fees in writing; pricing is quote-based, and implementation charges are not specified on the vendor's site.

We have no Reddit posts or comments in the published material, so we can't say what users commonly cite when leaving. For an exit plan, ask Fujitsu about data retrieval, deletion, transition support, and any contract notice periods before signing.