Fujitsu RunMyProcess review

Fujitsu RunMyProcess is an enterprise low-code process orchestration platform, not a code library or command-line tool. It sits between business users, applications and the systems that hold operational data. Teams use its visual BPMN designer to model multi-lane workflows, then build responsive web and mobile interfaces that connect to those workflows.

The platform also includes a native NoSQL database, API management, governance controls and monitoring. For integrations, the homepage lists native connectors, REST and SOAP APIs, and secure agents for cloud and on-premise systems. It describes the platform as cloud-native and promotes cloud, hybrid and multi-cloud deployment. Those statements do not, by themselves, establish whether customers can run the platform on their own infrastructure; confirm the supported deployment model with Fujitsu.

In a stack, RunMyProcess is the orchestration and application layer above business systems, coordinating people, data and process steps rather than replacing every system of record.

The homepage names REST and SOAP APIs as integration surfaces and says teams can expose processes and business logic as reusable APIs. It also lists native connectors and secure agents for connecting cloud and on-premise systems. That gives developers several routes into existing systems, but the homepage does not name supported SDKs, programming languages, a CLI, webhooks or plugins. Confirm SDK availability and version support in Fujitsu’s documentation before planning an implementation around a language-specific client.

The visual BPMN designer and WYSIWYG editor are the primary build surfaces described: one models workflows; the other builds responsive interfaces connected to them. The homepage describes built-in AI services for document processing, sentiment analysis and related tasks. Connector totals are inconsistent across homepage sections, which cite both 50+ and 70+ connectors. Validate the specific systems and operations your workflows need, and ask for current API references, authentication details, rate limits and examples.

The pricing information lists one plan, Custom, for organizations seeking a quote. It publishes no monthly or annual price, starting price, included usage, add-on prices or billing terms. It also lists no free plan or free trial. Budgeting therefore starts with a sales conversation rather than a public rate card.

The vendor does not publish whether a production bill scales by users, workflow executions, API requests, environments, storage, connectors or compute. It also does not publish overage rates or usage thresholds. Do not assume a flat subscription or usage-based pricing from the available plan description. Ask for a written quote that separates platform fees, implementation and support services, and any usage-based charges. Request examples at expected workflow volume and a schedule of overages, if any. The homepage advertises professional services for integration, consulting, staffing, modernization and compliance, but does not publish their prices. With no public price or free tier to compare, value depends on the quote and the cost of the surrounding deployment.

The homepage does not publish an open-source licence or state that the platform’s source code is available. It describes cloud, hybrid and multi-cloud deployment, but those descriptions do not confirm a self-hosted installation option. Ask Fujitsu which components run in customer-controlled infrastructure and what the deployment requirements are.

The homepage also does not describe data-export formats, migration tooling or termination procedures. That matters because workflows, app interfaces, data models and integrations can become platform-specific assets. Before building production processes, ask how to export process definitions, application data, audit records and attachments, and whether exports remain usable outside RunMyProcess. Confirm contractual access to your data and the cost and support available for migration. Without those details, the degree of lock-in is difficult to assess.

The homepage lists granular role-based access control, organization hierarchies, audit logs, versioning, controlled releases and real-time process metrics. It also states that Fujitsu RunMyProcess is ISO 27001 certified. These are relevant governance and security features, but they do not replace a review of the actual controls, certification scope and contractual commitments for your deployment.

The vendor does not publish API rate limits, workflow-volume limits, service-level targets, recovery objectives or public scaling thresholds in the published material. Its homepage describes a flexible-schema NoSQL database with real-time scaling, but teams should request capacity guidance for their workload. Before production, confirm limits for API calls, concurrent processes, storage and environments; escalation and incident support; backup and restore procedures; and how deployments are rolled back. Also verify connector behavior when dependent systems are unavailable. Those details determine whether the platform meets your reliability and compliance requirements.