Frequently Asked Questions

One credit is deducted each time a workflow instance is started (POST /api/v1/process-instances). Service tasks, user tasks, and gateways within that instance are included at no extra cost — there's no per-task fee.

No. Credits are one-time packs you buy and use at your own pace. There is no monthly fee, no seat pricing, and no idle cost. If you don't run workflows in a given month, you pay nothing.

Yes. Purchased credits are valid for 30 days from the date of purchase. Free signup credits also expire after 30 days. You'll receive an email reminder before expiry.

Expired credits are not refundable, so we recommend buying packs that match your near-term usage rather than stocking up.

The API returns 402 Payment Required when your balance reaches zero. Pending jobs remain in the queue — no work is lost. Top up your credits and polling workers will resume picking them up automatically.

Credit packs are non-refundable once purchased. If you have questions about your bill or a specific charge, contact support@priostack.com and we'll review it on a case-by-case basis.

No. Any standard BPMN 2.0 file works with Priostack. Task definition extension elements (<taskDefinition type="...">) are fully supported for routing jobs to your workers.

Priostack supports the core BPMN 2.0 execution subset: start/end events, service tasks, user tasks, exclusive gateways, parallel gateways, sequence flows, and message/signal events.

More complex elements (sub-processes, compensation, ad-hoc) are on the roadmap. Check the API docs for the current compatibility matrix.

A single process definition cannot contain more than 150 flow nodes (service tasks, user tasks, gateways, and all other flow elements combined). This limit ensures predictable execution performance and cost per instance.

Processes exceeding this limit are rejected at deployment time with a clear error message — your other processes are not affected.

Yes. Priostack exposes the standard Operate and Tasklist-compatible REST API surface — /api/v1/process-instances, /api/v1/incidents, and a GraphQL endpoint at /api/v1/graphql for human tasks. Configure any compatible client to point at https://priostack.com/api/v1.

Priostack's execution engine performs a structural analysis of your process model at deployment time and can detect deadlocks — situations where a token can enter a state from which the workflow can never reach an end event.

Deadlocked instances appear automatically in GET /api/v1/incidents so you can fix the process model before it affects production.

Priostack persists the state of every process instance. If the service restarts, in-flight instances resume from their last persisted checkpoint. Jobs that were activated before the restart re-appear in the queue once workers poll again.

Yes. When you activate a job with POST /api/v1/jobs/activate you set a timeout in milliseconds. If the worker doesn't complete or fail the job within that window, the lock is released and the job becomes available for another worker to pick up.

Enter your email on the homepage signup form. Your API key will be shown on the page and emailed to you instantly. No credit card required — you receive 100 free instance credits on signup.

In your modeler's connection settings (Gateway / Endpoint), set the cluster address to https://priostack.com and the REST endpoint to /api/v1. Use your API key as the bearer token. That's it — deploy and run as normal.

Absolutely. Priostack is a plain JSON REST API. See the API reference for full details, or jump straight into the curl examples on the homepage.