Automation shouldn't get more expensive just because your business grows.

Never priced per task or per user. You pay for compute time, and on a fixed-price environment each transaction costs less as volume grows.

Three ways to pay

  • Processing time

    Pay for the hours the engine actually works. Billed by the hour, used by the millisecond.

  • Reserved environments

    A fixed monthly price for an environment that runs 24/7. The more it runs, the less each run costs.

  • Perpetual licence

    Own it, run it on your servers, and move the cost from OPEX to CAPEX.

Start on processing time. When volume turns steady, a reserved environment fixes the monthly price, however many runs it handles.

Community

For individuals getting started with automation.

FREE

No credit card required

Hosted by PROCESIO
Start for free
Processing Timei
  • 1 h of monthly processing time
  • 1 personal workspace (1 user)
  • Unlimited processes
  • Unlimited actions per process
  • Unlimited parallel executions
  • Community support

Limitations: 1 personal workspace (1 user) and 1h of monthly processing time.

AI included: procesio-cli, AI Connector Builder (free), AI Decisional. Bring your own model key, no AI markup.

Most Popular

Professional

For teams starting small, paying only for the hours they use.

€10/ hour

per hour of monthly processing time, billed yearly

Hosted by PROCESIO
Buy now
Processing Timei
  • Everything in Community, plus:
  • Unlimited users
  • Unlimited workspaces
  • Collaboration
  • User roles per workspace
  • Import & export workspace resources
  • Customer support

AI included: procesio-cli, AI Connector Builder (free), AI Decisional. Bring your own model key, no AI markup.

Business

For steady volume at a fixed monthly price.

Custom

per reserved environment, monthly or yearly

Hosted by PROCESIO
Book a meeting
Reserved Environmenti
  • Everything in Professional, plus:
  • On-prem agent
  • Reserved execution environment - runs 24/7
  • 90-day expert access included
  • Expert technical support

AI included: procesio-cli, AI Connector Builder (free), AI Decisional. Bring your own model key, no AI markup.

Enterprise

Self-hosted and regulated use cases.

Custom

per licensed environment, yearly

Self-hosted
Book a meeting
Licensed Environmenti
  • Everything in Business, plus:
  • Deploy on your own infrastructure
  • A lower price per environment as you add more
  • Dedicated support consultants
  • Engineering team access, always included
  • Information security compliance support, always included

AI under your control. Pick the model, including one running on your own servers. AI steps sit only where you put them in the process. A person approves what matters, and AI decisions land in the run history for as long as the process keeps its run data.

AI included: procesio-cli, AI Connector Builder (free), AI Decisional. Bring your own model key, no AI markup.

Processing time

What one processing hour buys

Billed by the hour, used by the millisecond. Waiting for a person or a timer is free; waiting on an external call counts as Processing Time.

A worked example: supplier invoices

Take an invoice process with 13 steps: 10 platform actions at about 10 ms each, plus 3 calls to your ERP at about 0.4 seconds each. Each run works for roughly 1.3 seconds. At 2,000 invoices a month that's about 43 minutes, comfortably inside one processing hour. The time an invoice spends waiting for an approver isn't counted.

10 platform actions × ~10 ms
0.1 s
3 calls to the ERP × ~0.4 s
1.2 s
One run
≈ 1.3 s
2,000 runs a month
≈ 43 min

When the hours run out

We email you when 80% of the month's processing hours are used. If they run out, a buffer of 30% of your monthly hours keeps your processes running, and that extra time is invoiced at the end of the month. Once the buffer is gone too, new runs wait for the next month or for more hours. Workspace owners can set a lower cap if they'd rather never go over.

How fast you start

You can build a first automation in hours, with procesio-cli and your AI assistant or in the visual designers.

Large enterprise rollouts: first automation live by Day 60, guaranteed. This applies to large enterprise contracts where our team does the implementation, counted from project kickoff. If the first automation isn't in production by Day 60, we keep working on it, and the extra implementation time is on us until it is.

Full Comparison

Everything side by side

Community
Professional
Business
Enterprise

Additional resources
N/A
Processing hours/month
Reserved Execution Environments (EEs)
Licensed Execution Environments (EEs)
Billed yearly
Free
€120 per hour a year (€10 a month)
Custom, per environment
Custom, per environment
Billed monthly
Free
€12 per hour a month
Custom, per environment
N/A
Installation one-time cost
N/A
N/A
N/A
Custom
Infrastructure
Included
Included in the price
Included in the price
Client brings own infrastructure
Platform maintenance
Included
Included in the price
Included in the price
10-20% a year
Perpetual licensing option
N/A
N/A
N/A
Available - contact sales(Optional: own the licence outright instead of annual renewal. Contact sales for details.)

Import & export workspace resources
Export only
Collaboration

Unlimited users
Unlimited workspaces
User roles per workspace

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

Monthly processing time
1 h
Purchased hours
24/7 Reserved EEs
24/7 Licensed EEs
Maximum file size(The maximum size of a file that you can automate and process)
500 MB
500 MB
500 MB
Custom
When the processing hours run out(Reserved and licensed environments have no hour limit; runs queue only while every environment is busy)
New runs wait until the next calendar month
Alert at 80%. Then a 30% buffer keeps runs going, invoiced at month end. After the buffer, new runs wait for the next month or for more hours
No hour limit
No hour limit

Custom URL path

On-prem agent

SSO (SAML2 / OAuth2)

Customer support(Your personalised support level depends on the plan you select)
Customer support from our team
Expert technical support from our team(90-day expert access included)
Dedicated consultants offer high-priority support & guidance.(90-day expert access included)
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
From 1 FTE a month
From 1 FTE a month
From 1 FTE a month

Included in every plan

Community, Professional, Business and Enterprise all come with these.

Essentials

  • Unlimited features
  • Unlimited processes
  • Unlimited actions per process

Governance & Observability

  • Personal workspaceEvery user gets one, with 1 h of processing time a month
  • Credential ManagerCentralised, encrypted credential vault: update once, change everywhere
  • AnalyticsGain insights into workflow utilisation and performance over time
  • Process Instances: UnlimitedThe process execution history for debugging, logging, and audit
  • Data retentionDecide per process how instance data is kept, down to clearing it as soon as the run ends

Process Execution

  • Process InputsExecute complex processes by parsing and filling required inputs
  • Process OutputsSet 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 executionExecute multiple process instances in parallel
  • Maximum process running time: UnlimitedConfigurable, even unlimited, process run timeout
  • Minimum interval between scheduled processes: 1 minuteMinimum time between scheduled process runs

Processing

  • Data transfer: Unlimited
  • Real-time execution monitoringImmediately identify, isolate, and troubleshoot process instance execution issues with real-time visual monitoring

Process Design

  • Advanced Workflow BuilderThe most advanced visual workflow builder
  • Test actions at design time
  • Resource MapStructured visualisation and analysis of linked processes
  • Data ModelsModel the data structures, defining how data is stored, transferred, and transformed between systems
  • Data StoreTables inside PROCESIO that processes read and write, with SQL queries through Query Store
  • Action templatesConfigure an action, save the template, and reuse it
  • Breakpoint & DebugAdd breakpoints in the process and run in debug mode
  • Error PortImplement error handling similar to a Try-Catch block, allowing for alternative process routing upon error detection
  • Process Execution notificationYou can configure your processes to send email notifications in case of success or error
  • Scripting actions (C#, JavaScript, Node.js, Python and Ruby)
  • Create custom actions & connectorsUsers can create their own PROCESIO actions and connectors, using C#
  • AI Connector BuilderWrites and compiles a connector from an API's documentation, ready to install as a custom action
  • AI DecisionalBranch a process on conditions written in plain language, decided by the AI model you connect
  • Built-in AI agents and tools (AAT)Ready-made skills for AI agents that run as governed, audited processes

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 triggersTrigger Forms, Processes, JavaScript, Map Data per form/section/components with Conditional Logic
  • Data Store from formsForm events can read, add, update and delete Data Store rows
  • Dynamic Tables
  • Form variables
  • Custom notifications
  • Custom Design System (CSS, styleguide, light and dark themes)
  • Public Forms
  • Document signingAdd a PDF to a form, place signature fields and send it to signers in a set order or all at once

Flows

  • Connect Tasks from different forms into a single flow
  • Customizable Dashboard

Document Designer

  • Document Designer availability
  • Generate documents (PDF, Word and HTML)From templates filled with process data

Webhooks

  • Webhooks availability

Integration

  • Access to PROCESIO endpoints: Unlimited (no rate limit)
  • procesio-cliOpen-source command line your AI agents use to create, test and run processes
  • Call API actionWhat you can do with Postman, you can do with this action. You can configure it to connect to any REST API
  • SQL actions (SQL Server and MySQL)Run queries and commands on your own databases

Security

  • Two-factor authenticationImplement an additional layer of security for identity verification
  • 6 ISO certifications

Support

  • Community Support

FAQ

Common questions answered

What is Processing Time?

Processing Time is the actual compute time spent executing actions inside a process. It is metered to the millisecond, so you pay only for the time your actions actively run. Queuing and platform orchestration are not billed. Waiting for a person or a timer is free; waiting on an external call counts as Processing Time.

What is an Execution Environment (EE)?

An Execution Environment is a computing unit that runs processes. Think of it as a container that executes your workflow actions. In the Processing Time model, EEs are auto-scaled by PROCESIO. In Reserved or Self-Hosted plans, you own a fixed number of EEs.

What is a Process in PROCESIO?

A Process is a visual workflow made of actions: API calls, data transformations, scripts, document generation, approvals and more. You build it in the drag-and-drop Process Designer, or your AI agents build it through procesio-cli.

What is a Process Instance?

Every time a process runs (via API, webhook, schedule, form, or manual start), PROCESIO creates a process instance to track that execution with full history, logs, and debug data.

What is an Action?

An Action is a single operation inside a process: an API call, data mapping, file read, approval, script execution and so on. PROCESIO has 200+ platform actions and supports custom C# actions.

What is the difference between a Platform Action and a Custom Action?

Platform Actions are built by PROCESIO and preloaded in every EE, so they start fast. Custom Actions are C# actions you deploy to a workspace, written by hand or generated from an API's documentation by the AI Connector Builder. They load the first time a process uses them. Both consume Processing Time the same way.

What is the Data Store?

The Data Store keeps data inside PROCESIO, in tables your processes and forms share. Processes add, read, update and delete rows with filters, and the Query Store action runs SQL queries over them. Forms can read and write the Data Store straight from their events, without calling a process.

Can PROCESIO replace RPA tools?

For most work driven by APIs, databases and files, yes: API orchestration, file processing, approvals, document generation, and local scripts through the on-prem agent. PROCESIO doesn't click through desktop screens itself. When a step only exists in a user interface, an RPA tool can do that step while PROCESIO runs the process around it.

Is AI in PROCESIO available today?

Yes. procesio-cli, the AI Connector Builder and AAT, the agents and tools built into PROCESIO, are all live. Processes in production use AI models to read documents and classify data.

Can my AI agents build and run PROCESIO processes?

Yes, through procesio-cli, an open-source (Apache-2.0) command line with an MCP server. Your own agents and coding assistants, such as Claude Code or Codex, use it to create, test, run and fix processes, forms and documents in your workspace. Credentials stay in your operating system's secret store. What the agent builds is an ordinary PROCESIO process you can open, review and audit.

What is AAT?

AAT (Agents and Tools) is the set of AI agents and tools built into PROCESIO. They give AI agents ready-made skills. Each skill runs as a PROCESIO process, so every agent action goes through a governed, audited flow.

Can PROCESIO build a connector from an API's documentation?

Yes. Give the AI Connector Builder the API's documentation. It asks a few clarifying questions, plans the connector, writes the C# code, compiles it in an isolated build and hands you a Custom Action to install in your workspace. From then on the connector works like any other action in the Process Designer. The AI Connector Builder is free; model usage runs on your own key.

Which AI models can a process use?

Claude, Copilot, Gemini, ChatGPT, or a model you run yourself. Processes use them to read emails, PDFs and files, pull out the data that matters, classify it and clean it. Rules take the routine cases and AI the ambiguous ones. A person only looks at what needs judgment.

What do the AI features cost?

Your AI provider bills model usage, not PROCESIO, because processes call models with your own API keys. There's no AI markup from us. The AI Connector Builder is free, and procesio-cli is open source. A model call inside a process counts as Processing Time, like any other external call.

Is it safe to use AI on our data?

You decide where the data goes. Processes call the model you choose with your own API key, kept in the encrypted Credential Manager, and that model can run on your own servers. AI steps sit only where you put them, a person approves what matters, and AI decisions stay in the run history for as long as the process keeps its run data. procesio-cli works the same way: it's driven by the AI assistant you use, such as Claude Code, Claude Cowork or the ChatGPT desktop app, on your own account.

Can I use PROCESIO like Lovable or Bolt?

For business apps, yes. Your AI assistant builds the forms, Data Store tables, processes and documents through procesio-cli. The result runs on a platform your IT team governs, with users and roles, credentials, run history and hosting taken care of, and there's no generated codebase for anyone to maintain. Those tools are the better choice for a pixel-perfect consumer front end, such as a marketing site or a mobile app with its own custom design. PROCESIO forms take custom CSS and JavaScript; they are still built for business processes.

What is the maximum file size PROCESIO can process?

Cloud plans support up to 500 MB per file. On-Prem and Enterprise deployments can configure custom file size limits based on your own infrastructure.

Will PROCESIO handle our volume?

One energy & utilities company moved more than 5 million tasks a year onto PROCESIO. On Processing Time we add execution environments as load grows; on Reserved or self-hosted plans you add environments. Large files are streamed, big batches are split into chunks, and you pay for compute time, not data volume.

Do connectors or integrations cost extra?

No. Connectors are included in your plan: REST APIs, SQL Server and MySQL, SMTP, IMAP/POP3, SFTP, AWS S3, Azure Storage and the rest. A connector you add yourself, coded by hand or generated by the AI Connector Builder, runs as a Custom Action, again with no per-connector fee.

Should I use the Data Store or my own database?

Use the Data Store for data that belongs to the automation: lookup tables, statuses, work queues, the records a form collects. Keep data in your own database when another system owns it or other applications need it. Processes reach SQL Server and MySQL through the SQL actions, so one process can use both.

Can PROCESIO generate documents?

Yes. In the Document Designer you build a template and bind it to process data, including tables, lists and images. Any process can then generate it as PDF, Word and HTML, for invoices, contracts, reports or email bodies. Word mail merge and DOCX to PDF conversion are available as actions too.

What is a Task in Forms & Tasks?

A Task is a human activity inside an automation flow: an approval, data review, document check, or any step that needs a person to act before the process continues.

How do approvals and other human steps work?

A process hands a step to a person through a User Task form: an approval, a review, a detail only they know. The assignee gets an email and finds the task under "Assigned to me". The process waits, and once they submit, it continues with their answer. Waiting uses no Processing Time.

Are Forms and Tasks billed separately?

No. Forms and Tasks are free to create and use. Processing Time is only consumed when processes run or when events trigger a process: form events such as onLoad, onBeforeSubmit and onAfterSubmit, or element events such as onClick and onInput. Waiting for human approval does not consume Processing Time.

Can people sign documents in PROCESIO?

Yes. Put a PDF on a form, place the signature blocks and pick who signs: the person filling in the form, colleagues from your workspace, or both. They can sign one after another or at the same time. Each signer draws, uploads or types a signature, or declines and says why. PROCESIO stamps the signed PDF and records every signing step. Once the last signature is in, the process moves on. You don't need a separate e-signature service.

What is the difference between Processing Time and Execution Environments?

Processing Time: you pay only for consumed compute seconds, EEs are auto-scaled, ideal for small or irregular workloads. Execution Environments: fixed number of EEs with unlimited processing time, ideal for predictable workloads and strict SLAs.

Which pricing model should I choose?

Start on Processing Time while volume is small or uneven: you pay only for the compute you use, and we scale it. When volume is steady, move to Reserved EEs: a fixed monthly price with no hour limit, so the cost of each transaction falls as volume grows. Self-hosted EEs are for organisations that need data on their own servers, on a yearly or perpetual licence.

What is the difference between Execution Time and Processing Time?

Execution Time is the total time a run takes, including waits, queues and scheduling. Processing Time counts only the time actions are actively executing, and that is what you're billed for. Queues and platform orchestration are never billed. Waiting for a person or a timer is free; waiting on an external call counts as Processing Time.

Are API calls, webhooks, or triggers billed separately?

No. API calls and triggers only consume Processing Time or EE capacity during execution. There is no per-call, per-trigger, or per-webhook fee.

Do I pay for idle time?

On Processing Time, no: you pay only for active compute. On Reserved or Self-Hosted EEs you pay a fixed price for environments that run 24/7, with no limit on processing hours, so the more they run, the less each run costs.

Does PROCESIO charge per user, per task, or per process?

No. There are no fees per user, task, run, process, action or connector. Every paid plan includes unlimited users, workspaces, processes and actions. You pay for compute capacity, as Processing Time or as Execution Environments.

What does one processing hour buy?

Take an invoice process with 13 steps: 10 platform actions at about 10 ms each, plus 3 calls to your ERP at about 0.4 seconds each. Each run works for roughly 1.3 seconds. At 2,000 invoices a month that's about 43 minutes, comfortably inside one processing hour. The time an invoice spends waiting for an approver isn't counted.

Can I limit how much Processing Time a workspace consumes?

Yes. Workspace owners can set a processing cap so a workspace never uses more than planned, buffer included.

Do delays or wait actions consume Processing Time?

No. A Delay action pauses the workflow without consuming compute. Waiting for a person or a timer is free; waiting on an external call counts as Processing Time.

What if an external API call is slow? Do I pay extra?

Yes. Waiting for a person or a timer is free; waiting on an external call counts as Processing Time. Network latency, slow external APIs and retries add to it, because the action is running inside an EE while it waits for the answer. You pay for the time, not the number of calls.

What happens if I run out of Processing Time?

We email you when 80% of the month's processing hours are used. If they run out, a buffer of 30% of your monthly hours keeps your processes running, and that extra time is invoiced at the end of the month. Once the buffer is gone too, new runs wait for the next month or for more hours. Workspace owners can set a lower cap if they'd rather never go over. On the free Community plan there is no buffer: new runs wait for the next month. If your volume is steady, a Reserved EE plan gives you unlimited processing time.

What happens if all my Execution Environments are busy?

On the Processing Time plan: PROCESIO auto-scales EEs, so there is virtually no waiting. On Reserved or Self-Hosted plans: new instances queue until an EE becomes free.

How many processes can run in parallel?

On Processing Time plans, PROCESIO adds EEs automatically as load grows, so parallel runs aren't tied to a fixed number. On Reserved and self-hosted plans, the limit is the number of EEs you have: 4 EEs run 4 processes at once, and further runs wait in the queue.

Can I run heavy scripts or custom code inside PROCESIO?

Yes. You can write code in C#, JavaScript, Node.js, Python and Ruby, package heavy processing as a Custom Action, and run scripts on your own machines through the on-prem agent.

Can I choose between cloud and on-premise?

Yes. The same platform runs in PROCESIO's cloud, hosted in Romania (EU), or self-hosted on your own Kubernetes cluster. There's also a middle path: stay in the cloud and let the on-prem agent handle the steps that must reach systems inside your network.

Does self-hosted PROCESIO require Kubernetes?

Yes. Self-hosting needs a Kubernetes cluster of at least five nodes, S3-compatible storage such as MinIO, databases and a few other infrastructure components. A monitoring stack comes with it (Grafana, Prometheus, Loki and Tempo). PROCESIO provides the deployment documentation and engineering support.

What extra costs exist for Self-Hosted deployments?

A yearly licence per EE at custom pricing, a one-time installation fee, and 10-20% yearly maintenance. Infrastructure isn't included; you bring your own. A perpetual licence is also available. Book a meeting for an exact quote.

Can I run processes inside my private network?

Yes. The on-prem agent runs on Linux or Windows inside your network and handles the steps that touch local systems: databases, file shares, shell commands, local scripts. It only opens outbound connections, so you don't open inbound ports or expose anything to the internet.

Is the on-prem agent billed separately?

No. The on-prem agent is included in Business and Enterprise plans. You pay only for your Processing Time or Execution Environments.

How does IT keep control of what teams build?

Every team builds in a workspace, and IT decides who gets in and with which role. Sign-in can run through SSO (SAML2 or OAuth2) with two-factor authentication, credentials sit in the encrypted Credential Manager instead of config files, and every run is recorded in the process history for as long as you choose to keep it. Paid plans have no limit on workspaces, processes or users, so a new team adds no per-user or per-workspace fee. The free Community plan has one personal workspace and 1 hour of processing time a month.

Is there a free plan?

Yes. The Community plan is free forever: 1 hour of processing time per month, 1 personal workspace, unlimited processes and actions. No credit card required. Sign up at procesio.app/create-account.

Do we need a big project to go live?

No. One person can build a first automation in hours on the free plan, with procesio-cli and an AI assistant or in the visual designers. Large enterprise rollouts also come with a guarantee: the first automation is live in production by Day 60. This applies to large enterprise contracts where our team does the implementation, counted from project kickoff. If the first automation isn't in production by Day 60, we keep working on it, and the extra implementation time is on us until it is.

Do I need coding experience to use PROCESIO?

No. Your team can start from the AI assistant it uses today, such as Claude Code or Codex: it builds through procesio-cli, and anyone can open the result in the visual designers. Business users build there by drag and drop; developers add C#, JavaScript, Node.js, Python and Ruby where a step needs code. The PROCESIO Academy is free.

What is the BPOF (Business Process Optimization Framework)?

A 30-day engagement for companies that don't yet know what to automate first. We map how the work runs today, find where it stalls, rank the fixes by return and hand you a roadmap your board can approve. If you go on to implement with us, the BPOF fee counts in full against it.

Is there training or certification for PROCESIO?

Yes. The PROCESIO Academy is free. Its five learning paths cover people who build, sell or run PROCESIO, starting with PROCESIO Day One. Skill badges and learning paths are open to everyone; partner staff can go on to a practical exam, marked by a person, to become PROCESIO Certified. Courses are in English.

How can my company become a PROCESIO partner?

There are four ways in: implementation partner, reseller, referral partner and technology partner. Apply through the partner portal at partners.procesio.app. Partners register their deals and get them protected, receive a sales and brand kit, and run the whole partnership from one portal.

Which certifications does PROCESIO hold?

PROCESIO holds 6 ISO certifications: ISO/IEC 27001 (information security), ISO 9001 (quality management), ISO/IEC 20000-1 (IT service management), ISO 37001 (anti-bribery management), ISO 14001 (environmental management) and ISO 45001 (occupational health and safety). The platform has also passed a CASA Tier 2 lab-tested assessment.

What security features does PROCESIO have?

Two-factor authentication, SSO over SAML2 or OAuth2, role-based permissions per workspace, an encrypted Credential Manager and audit logs. Data is encrypted with TLS 1.2 in transit and AES-256 at rest. Independent penetration tests run twice a year. Data retention settings let you decide how process-instance data is kept, down to clearing it as soon as a run ends.

Does PROCESIO have a SOC 2 report?

No. PROCESIO's security controls are certified under ISO/IEC 27001, alongside 5 other ISO standards, and the platform passed a CASA Tier 2 assessment. You can send security questionnaires through the contact page.

Where is my data stored?

On PROCESIO-hosted plans, data stays on a private cloud in Romania (EU), hosted by ITPS (part of ETA2U Group) in its Timișoara data centre, which is ISO 9001 and ISO 27001 certified. Customer data isn't transferred outside the European Economic Area. If you self-host, it stays on your own servers.

Is PROCESIO GDPR compliant?

Yes. PROCESIO processes and stores customer data in the EU, and you can self-host for full control. The Data Processing Agreement is published at procesio.com/dpa, and the Data Protection Officer is at dpo@procesio.com.

Can PROCESIO be used in regulated industries?

Yes. PROCESIO serves clients in energy & utilities, financial services, healthcare, retail and logistics. It holds 6 ISO certifications including ISO/IEC 27001, lets you clear process-instance data as soon as a run ends, and can run fully self-hosted when data must stay inside your own infrastructure.

How does PROCESIO compare to Zapier or Make?

Zapier and Make are built for quick app-to-app automations and charge per task or operation, so the bill climbs with volume. PROCESIO charges for compute time, with unlimited users and connectors. It also covers what those tools leave out: full code in C#, JavaScript, Node.js, Python and Ruby, forms and documents, enterprise governance and on-premise deployment.

How does PROCESIO compare to Power Automate?

Power Automate is strongest inside Microsoft 365 and for desktop automation (RPA) of apps without an API. It is sold per user, per bot or per run, in Microsoft's cloud. PROCESIO charges for processing time, a reserved environment or a perpetual licence, with unlimited users, includes forms, a Data Store and documents from templates, and can run entirely on your own servers.

How does PROCESIO compare to Workato or MuleSoft?

PROCESIO does the same core work (API orchestration, enterprise security, governance, complex logic), priced by compute instead of by task, message or credit, and a perpetual licence is available for the whole platform on your own servers. One client that moved over from Jitterbit cut its automation costs by 70%. You write logic in standard languages instead of proprietary ones like DataWeave, and your AI assistant can build processes through procesio-cli.

Can we migrate to PROCESIO, and what if we want to leave?

Yes. Workspace resources can be exported and imported, and our team moves clients over from Jitterbit and other platforms: one energy & utilities company moved more than 5 million tasks a year in weeks and cut its automation costs by 70%. If you leave, your code steps are plain C#, JavaScript, Node.js, Python or Ruby, data in your own databases stays where it is, and your workspace resources can be exported. On a perpetual licence you can keep running PROCESIO on your own servers.

PROCESIO

Not sure which plan fits?

Book a meeting with our team. We'll go through your processes, estimate how many hours they need, and help you pick between processing time, a reserved environment and self-hosting.

Book a meeting

Open in new tab

Calendar not loading? Open the booking page in a new tab