Choose the plan that's right for your automation needs.
For individuals getting started with automation
No Credit Card Required
Limitations: 1 personal workspace (1 user) and 1h of monthly processing time.
For freelancers, solopreneurs & SMB teams
Starting at
€10/ processing hour / month
billed annually
Starting at
€12/ processing hour / month
Everything in COMMUNITY, plus:
For SMB teams, growing businesses
Starting at
€511reserved environment / month
billed annually
Starting at
€613.2reserved environment / month
Everything in PROFESSIONAL, plus:
Self-hosted & Regulated Use Cases
Everything in BUSINESS, plus:
| Feature |
COMMUNITY
For individuals getting started with automation
|
PROFESSIONAL
For freelancers, solopreneurs & SMB teams
MOST POPULAR
|
BUSINESS
For SMB teams, growing businesses
|
ENTERPRISE
Self-hosted & Regulated Use Cases
|
|---|---|---|---|---|
| How much does scaling cost? | ||||
|
Additional resources
|
N/A |
Processing hours/month |
Reserved Environments |
Licensed Environments |
|
Price/year
|
FREE |
120 €/h/year |
6132 €/Env./year |
Custom |
|
Price/month
|
FREE |
12 €/h/month |
613.2 €/Env./month |
N/A |
|
Installation one-time cost
|
N/A |
N/A |
N/A |
€10–20k |
|
Infrastructure
|
included |
Included in the price |
Included in the price |
The client brings his own infrastructure |
|
Platform maintenance
|
included |
Included in the price |
Included in the price |
15–20%/year |
| ESSENTIALS | ||||
|
Unlimited features
|
||||
|
Unlimited Processes
|
||||
|
Unlimited actions per process
|
||||
|
Import & Export Workspace Resources
|
Export only |
|||
|
Collaboration
|
||||
| GOVERNANCE & OBSERVABILITY | ||||
|
Personal workspace
|
(Each user has their own personal workspace that comes with 1h/month of processing time) |
(Each user has their own personal workspace that comes with 1h/month of processing time) |
(Each user has their own personal workspace that comes with 1h/month of processing time) |
|
|
Credential Manager
(Centralized, encrypted credential vault: update once, change everywhere)
|
||||
|
Analytics
(Gain insights into workflow utilization and performance over time)
|
||||
|
Unlimited users
|
||||
|
Unlimited Workspaces
|
||||
|
User roles per workspace
|
||||
|
Process Instances
(The process execution history for debugging, logging, and audit)
|
Unlimited history |
Unlimited history |
Unlimited history |
Unlimited history |
|
Data Retention Policy
(You can configure the data retention for each process)
|
||||
|
Processing limits
|
1h of processing time/month |
The acquired processing time |
Each reserved Execution Environment runs 24/7. |
Each licensed Execution Environment runs 24/7. |
|
What happens after the processing limit is reached?
|
New process instances will not execute until the beginning of a new calendar month. |
New process instances will not execute until the beginning of a new calendar month. |
Process instances will be queued until a reserved Execution Environment becomes available. |
Process instances will be queued until a reserved Execution Environment becomes available. |
| PROCESS EXECUTION | ||||
|
Process Inputs
(Execute complex processes by parsing and filling required inputs)
|
||||
|
Process Outputs
(Set process-level outputs to ensure clear, real-time structured data)
|
||||
|
Call SubProcesses (sync)
(Invoke a sub-process and await its completion before proceeding with the current process)
|
||||
|
Trigger Processes (async/parallel)
(Trigger the execution of other processes from within a process, without waiting for their completion)
|
||||
|
Parallel execution
(Execute multiple process instances in parallel)
|
||||
|
Number of parallel executions
The maximum number of process instances running at the same time
|
unlimited |
unlimited |
Equal to the number of reserved environments acquired |
Equal to the number of licensed environments acquired |
|
Maximum process running time
(Configurable, even unlimited, process run timeout)
|
unlimited |
unlimited |
unlimited |
unlimited |
|
Minimum interval between scheduled processes
(Minimum time between scheduled process runs - in minutes)
|
1 |
1 |
1 |
1 |
|
Scripting actions
|
||||
|
Create Custom Actions & Connectors
(Users can create their own PROCESIO actions and connectors, using C#)
|
||||
|
Breakpoint & Debug
(Add breakpoints in the process and run in debug mode)
|
||||
|
Error Port
(Implement error handling similar to a Try-Catch block, allowing for alternative process routing upon error detection)
|
||||
|
Process Execution notification
(You can configure your processes to send email notifications in case of success or error)
|
||||
|
Maximum file size (MB)
(The maximum size of a file that you can automate and process)
|
500 MB |
500 MB |
500 MB |
Custom |
|
Data transfer
|
unlimited |
unlimited |
unlimited |
unlimited |
|
Real-time execution monitoring
(Immediately identify, isolate, and troubleshoot process instance execution issues with real-time visual monitoring.)
|
||||
| PROCESS DESIGN | ||||
|
Advanced Workflow Builder
(the most advanced visual workflow builder)
|
||||
|
Test actions at design time
|
||||
|
Resource Map
(Structured visualization and analysis of linked processes)
|
||||
|
Data Models
(Model the data structures, defining how data is stored, transferred, and transformed between systems)
|
||||
|
Action templates
(Configure an action, save the template, and reuse it)
|
||||
| FORMS & TASKS | ||||
|
Unlimited usage
|
||||
|
Custom URL path
|
||||
|
Embed in external web pages
|
||||
|
Advanced Form UI Builder
|
||||
|
Approval Flow Builder
|
||||
|
Delegate users per form/section
|
||||
|
Advance triggers
(Trigger Forms, Processes, JavaScript, Map Data per form/section/components With Conditional Logic)
|
||||
|
Dynamic Tables
|
||||
|
Form variables
|
||||
|
Custom notifications
|
||||
|
Custom Design System (CSS, styleguide)
|
||||
|
Public Forms
|
||||
|
Custom URL path
|
||||
| FLOWS | ||||
|
Connect Tasks from different forms into a single flow
|
||||
|
Customizable Dashboard
|
||||
| DOCUMENT DESIGNER | ||||
|
Document Designer availability
|
||||
| WEBHOOKS | ||||
|
Webhooks availability
|
||||
|
Custom URL path
|
||||
| INTEGRATION | ||||
|
Access to PROCESIO endpoints
|
unlimited (no rate call limit) |
unlimited (no rate call limit) |
unlimited (no rate call limit) |
unlimited (no rate call limit) |
|
Call API action
(What you can do with Postman, you can do with this action. You can configure it to connect to any REST API)
|
||||
|
On-prem agent
|
||||
| SUPPORT | ||||
|
Community Support
|
||||
|
Customer support
(Your personalized support level depends on the plan you select)
|
90-day expert access included |
Expert technical support from our team |
Expert technical support from our team |
Dedicated consultants offer high-priority support & guidance. |
|
Engineering Team Access
(Get expert onboarding and strategic guidance)
|
(only for higher-value yearly plans or for strategic partners) |
(only for higher-value yearly plans or for strategic partners) |
||
|
Information security compliance support
(Our information security team provides detailed information to ensure compliance)
|
(only for higher-value yearly plans or for strategic partners) |
(only for higher-value yearly plans or for strategic partners) |
||
|
Implementation effort outsourcing
|
Starting with 1 FTE/month |
Starting with 1 FTE/month |
Starting with 1 FTE/month |
Starting with 1 FTE/month |
| SECURITY | ||||
|
Two-factor authentication
(Implement an additional layer of security for identity verification)
|
||||
A pricing based on parallel execution environments is available for PROCESIO Partners, in order to scale with clients. Request to be a PROCESIO partner today!
FAQs
Haven't found what you're looking for? Explore the PROCESIO Help Center or Contact Us
Processing Time is the actual compute time spent executing actions inside a process. It's metered down to the millisecond and billed at €10/hour in cloud mode. Infrastructure, orchestration, and platform latency do not affect cost.
An Execution Environment is a computing unit that runs processes. Think of it as a container that executes workflow actions, custom code, API calls, etc. All PROCESIO pricing revolves around this unit.
A Process is a visual workflow made of actions (API calls, data transformations, scripts, document generation, etc.). You design it using the Process Designer.
Every time a process runs (via API, webhook, schedule, form, or manual start), PROCESIO creates a process instance. Instances can run in parallel, are debuggable live, and consume Processing Time or EE capacity.
An Action is a "Lego block" inside a process, an operation such as an API call, data mapping, file read, SQL query, decision logic, etc.
Platform Actions: Pre-built actions by PROCESIO, optimized and preloaded in EEs for fast execution.
Custom Actions: User-built C# actions deployable in that workspace, loaded dynamically at first use.
No. They consume the same Processing Time or EE capacity as Platform Actions.
PROCESIO includes:
Suitable for regulated industries (finance, energy, healthcare, etc.).
Yes, for most API/database/file-driven processes. RPA-style UI automation is coming natively in the PROCESIO roadmap, but today you can already replace 70%+ of typical RPA workloads using:
Cloud: up to 500 MB per file
On-Prem / Enterprise: custom file size limits can be configured based on your infrastructure
PROCESIO uses:
Processing Time is proportional to actual compute, not data volume per se.
No. All connectors (REST API, SQL, SMTP, IMAP/POP3, SFTP, cloud storage, etc.) are included. Custom connectors are included as well (via C# Custom Actions). There is no per-connector or per-integration pricing.
A Task is a human activity inside an automation flow (e.g., an approval, data check, or document review). Forms allow users to interact with the process at specific steps. Tasks do not consume Processing Time while waiting for user input.
Forms & Tasks themselves are free to create and use. Processing Time is only consumed:
Waiting for human approval does not consume Processing Time.
Processing Time:
Execution Environments:
Execution Time = total runtime from start to finish, including waiting, scheduling, or queues.
Processing Time = ONLY the time actions are actively executing inside an EE.
You are billed only for Processing Time, never for waiting, queues, network delays, or platform orchestration.
Reserved EEs are cloud-based compute units billed at €0.7/hour (~€6,132/year). You reserve a fixed number of EEs, and each can run processes 24/7 with unlimited processing time.
Licensed EEs apply to self-hosted / on-prem installations. They custom pricing per year per EE, run on your infrastructure, and include unlimited compute with concurrency capped by the number of licensed EEs.
No. API calls and triggers only consume Processing Time or EE capacity during execution. There is no per-task, per-user, or per-integration fee.
Processing Time model: No, you pay only for active compute time.
Reserved/Self-Hosted EEs: Yes, they run 24/7 and provide unlimited compute capacity.
No. PROCESIO does not charge per user, process, action, or connector. You pay only for compute capacity (Processing Time or Execution Environments).
Yes. Workspace owners can set processing caps to prevent overconsumption and ensure predictable monthly spending.
You cannot simultaneously use both Processing Time and Reserved Execution Environment pricing within the same workspace. However, you are permitted to switch between these two pricing models in the same workspace at different times, or to apply them concurrently to different master-workspaces.
A scheduled process only consumes Processing Time if the actions actually run. Idle schedules or processes that exit immediately cost 0 ms.
No. A Delay action pauses the workflow without consuming compute. Processing Time is billed only when actions are actively executed.
Yes. Network latency, external system delays, slow APIs, or retries DO increase Processing Time. You are billed for PROCESIO's internal execution time, which depends on the waiting time for external system responses.
New process instances wait until the next monthly cycle (or until you add more processing hours). Hosted by PROCESIO or Self-Hosted EE plans do not have this limitation.
New instances queue until an EE becomes free.
Processing Time plan: unlimited auto-scaling → no waiting.
Reserved/Self-Hosted: concurrency is limited by the number of EEs.
In the Processing Time model, PROCESIO automatically provisions unlimited parallel Execution Environments to ensure processes run immediately and fast. There is no concurrency limit; your only limit is the amount of purchased Processing Time.
Paid plans allow unlimited parallel executions. The actual concurrency depends on:
Choose Processing Time if:
Choose Reserved Execution Environments if:
Choose On-Prem EEs if:
Yes. You can:
Yes, self-hosting requires a Kubernetes cluster (minimum 5 nodes), storage services, databases, and other microservices as listed in the self-hosting RFC.
Just add more licensed EEs. No changes to your processes are needed.
Yes. The on-prem agent allows processes to run inside your private infrastructure, behind firewalls, without opening inbound ports. The agent executes local scripts, connects to local DBs, and manipulates files securely.
No. The agent is included in Business and Enterprise plans. You only pay for Processing Time or Execution Environments associated with your workspace.
No. All paid plans include unlimited:
No FAQs found matching your search.