Frequently Asked Questions

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:

• 2FA
• SSO (SAML2 / OAuth2)
• Credential Manager (encrypted vault)
• Audit logs
• Self-hosting options
• No-user-limit governance (roles, workspaces)

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:

• API orchestration
• File processing
• Approvals
• Document generation
• Local scripts via the on-prem agent

Cloud: up to 500 MB per file
On-Prem / Enterprise: custom file size limits can be configured based on your infrastructure

PROCESIO uses:

• Data Models for structured mapping
• Streaming for large files
• Chunking patterns via ForEach
• Direct integrations with SQL, SFTP, storage services, etc.

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:

• When processes run
• When form events trigger a process (onSubmit, onClick, onInput)

Waiting for human approval does not consume Processing Time.

Processing Time:

• Pay only for consumed compute time
• Unlimited parallel EEs (auto-scaled by PROCESIO)
• Best for small/irregular workloads

Execution Environments:

• Fixed number of EEs with unlimited processing time
• Ideal for predictable workloads and SLAs

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:

• Processing Time model: unlimited EEs → near-infinite parallelism
• Reserved/On-Prem: parallel limit = number of EEs (e.g., 4 EEs = up to 4 processes at the exact same moment)

Choose Processing Time if:

• You are starting small
• Workloads are irregular
• You want auto-scaling and zero DevOps

Choose Reserved Execution Environments if:

• You have predictable or always-on workflows
• Need strict SLAs
• Want unlimited processing at a fixed cost

Choose On-Prem EEs if:

• You require full data residency
• Must run inside your infrastructure
• Need predictable licensing with no cloud dependency

Yes. You can:

• Use scripting (NodeJS, Python, JavaScript)
• Connect to external AI APIs
• Run local scripts via the on-prem agent
• Use Custom Actions for heavy C# processing

Yes, self-hosting requires a Kubernetes cluster (minimum 5 nodes), storage services, databases, and other microservices as listed in the self-hosting RFC.

• Custom pricing per year per EE license (contact our sales department for a quote)
• €10–20k one-time installation
• 15–20% yearly maintenance
• No infrastructure is included; clients bring their own

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:

• Workspaces
• Processes
• Actions per process
• Process history