Frequently Asked Questions

Yes. Priostack is free, with limits, and no card is required. Each account can hold up to 5 agents and 5 spaces on the Agent Context Network, and each agent account stores up to 500,000 objects. Workflow API accounts get 100 credits at signup and 100 more every day; credits add up, with no cap and no expiry. Two things are optional and paid: one-off credit packs (from €5) and a monthly scheduling-priority subscription (from €0).

Yes. When your balance is too low, charged workflow calls return 402 until the next daily grant or a pack top-up; reads keep working. The agent network never returns 402: an hour your balance cannot cover is simply not charged. The 5-agent and 5-space limits answer 409, and a full agent account refuses new objects. No limit resets on a monthly cycle, and nothing is deleted.

1 credit each: starting a process instance (POST /api/v1/process-instances), starting a CMMN case (POST /api/v1/cases) and evaluating a decision (POST /api/v1/decisions/{id}/evaluate). Service tasks, gateways and the other elements inside an instance add nothing.

Deploying: BPMN through POST /api/v1/process-definitions is free. Any model (BPMN, DMN, CMMN or ArchiMate) through POST /api/v1/models costs 1 credit, refunded if the deploy fails.

Completing work: completing or failing a service job (POST /api/v1/jobs/{key}/complete or /fail) is free. Completing a user task through POST /api/v1/tasks/{id}/complete costs 1 credit; the same task completed through GraphQL completeTask or a job call is free.

Free: every read (instances, incidents, lists, topology). Connectors are not charged. An orchestration (PAOL) run, started from the dashboard, costs 1 credit per action its net fires.

Charged calls return 402 Payment Required; reads keep working. Instances already running keep moving, because activating and completing service jobs is free. Your balance comes back with the next daily grant (100 credits every 24 hours from signup, paid at the next check, which runs every 6 hours) or when you buy a credit pack. No card is charged unless you asked for it.

Yes, at any time. Contact support@priostack.com and we close it for you. If you subscribed to scheduling priority, end it from the wallet first; it stops at the end of the paid period. Your credit balance is removed with the account.

Priostack is designed for three primary audiences:

Enterprise architects who maintain ArchiMate models and need a direct link from strategy to operational execution - without maintaining separate tooling for BPM, case management, and architecture.

Business analysts and process managers who design BPMN and CMMN workflows and need to deploy, monitor, and manage them from a single dashboard without engineering overhead.

Consultancies and integrators who deliver operational transformation projects for clients and need a multi-client platform that combines process automation, decision management, and architecture traceability.

No. The dashboard, modelers, and workspace are designed for business analysts and architects. You can model, deploy, and monitor processes without writing code.

For custom worker implementations (service tasks), a developer is needed to build the polling workers that consume POST /api/v1/jobs/activate - but the orchestration, monitoring, and decision evaluation are fully no-code.

Yes. Create a workspace per client to organise each client's work. All workspaces draw on your account's single credit balance: there is no separate plan, no wallet per workspace and no per-client billing.

Priostack currently supports:

BPMN 2.0 - process automation with full execution semantics (service tasks, user tasks, gateways, events).

CMMN 1.1 - adaptive case management with plan items, stages, and milestones.

DMN 1.3 - decision tables and decision requirement diagrams for business rules.

ArchiMate 4.0 (Open Exchange) - enterprise architecture models compiled for dependency analysis.

IFML - interaction flow models for designing user-facing application behaviour.

No. Standard BPMN 2.0 and CMMN 1.1 files work as-is. Task definition extension elements (<taskDefinition type="...">) are supported for routing jobs to workers. Import via the Modeler, or deploy directly via the REST API.

Priostack does not enforce a fixed number of flow nodes. A deploy is refused with 422 only when the model does not parse or compile, and the error names the problem.

Partly. Priostack ships with a built-in tasklist at /tasklist and a full dashboard at /dashboard. External tools reach the same data through Priostack's own REST API under /api/v1 (instances, incidents, jobs) and a GraphQL endpoint at /api/v1/graphql (getTasks, getTask, completeTask, claimTask). These are not the Camunda Operate or Tasklist APIs, so a Camunda tool connects only once its calls are pointed at these endpoints with an API key.

When you deploy a process model, Priostack analyses it automatically and flags any path where a workflow could get stuck before a single real instance has started. When a job fails with no retries left, the instance moves to INCIDENT and a record appears in GET /api/v1/incidents. Other run failures move the instance to INCIDENT without a record: list them with GET /api/v1/process-instances?filter.state=INCIDENT. A service task whose worker never answers raises nothing on its own; the instance stays ACTIVE, so bound the wait with a timer boundary event.

Every instance state is persisted to disk. If the service restarts, in-flight instances resume from their last checkpoint. Jobs re-appear in the queue once workers poll again - no work is lost.

No. Priostack does not expire a job: the timeout field of POST /api/v1/jobs/activate is accepted and ignored, and an activated job stays with its worker until it is completed or failed (or the server restarts). To bound a long task, model a timer boundary event on it, and have workers release jobs they cannot finish with POST /api/v1/jobs/{key}/fail.

Enter your email on the homepage signup form and confirm the address from the email we send. Your API key arrives in the welcome email once the address is verified, with 100 credits on the account. No card is required.

In your modeler's connection settings, set the cluster address to https://priostack.com and the REST endpoint to /api/v1. Use your API key as the bearer token. Or use the built-in modeler in the dashboard - no installation needed.

Absolutely. Priostack is a plain JSON REST API. See the API reference and the guides it links, or use the curl examples on the homepage to start immediately.

Yes. Join the Priostack Community Telegram group to ask questions, share workflows, and get feedback from other architects and analysts using Priostack.

For longer-form discussions, visit the community forum where you can post questions, share case studies, and browse the knowledge base.

Yes. We host monthly async community calls - recorded sessions where the team walks through new features, answers submitted questions, and showcases community-built workflows. Recordings are posted in the Telegram group and the forum within 24 hours.