Community
Explore PROCESIO, learn the basics, and experiment with limited execution time.
€0
(per processing time)
Business
Tailored resources and servies for companies that want to UP their Automation game.
€6,132
(per execution environment)
Enterprise
Tailored resources and servies for companies that want to UP their Automation game.
On demand
Based on business KPIs such as the number of invoices, documents, or transactions.
The pricing per Execution Environment (€0.7 / hour / env) is Comparable to AWS, Azure, and GCP compute pricing and decreases with higher volume
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!
Talk with an expert to receive a personalized demo or a tailored quotation.
We decided to charge per time and not per task because it is a more accurate and transparent way of measuring the value we provide.
We understand that it’s not common practice for automation software to charge credits this way, and most of them have a “per task” charging approach – but it makes more sense and it is directly correlated with the value that PROCESIO brings.
Time consumed by action while processing. Currently, the average execution time of a platform action is 100 miliseconds. The execution time of a custom action may differ in accordance with its complexity.
Actions are the building blocks used to create a process. You can drag them from the left-hand menu to the canvas to perform integration and automation functions.
At PROCESIO we distinguish between Platform actions and Custom actions. While Platform actions are pre-built actions ready to be used, Custom actions are self-built actions by users.
A process is a set of actions executed in sequential order with the aim of achieving the desired outcome. Outcomes can vary depending on the use case.
Use-case examples: System/ Software integrations, data transformation, and more.
A Process Instance is the state of a process that was executed at a specific point in time using a specific data configuration.
An Action Run is the execution of an action in a process with an estimated execution time of ~200 ms.
A Custom Action is an action built by a user and uploaded in their PROCESIO workspace with the scope of using it within a process to achieve the desired outcome.
A Custom Action Run is the execution of the custom action. Its execution time depends on how complex the action is.
