Frequently Asked Questions

Yes, with limits. Every account gets 100 credits at signup and 100 more every day; they add up, with no cap and no expiry. Charged calls cost 1 credit each: a process instance or CMMN case started, a decision evaluated, a model deployed through /api/v1/models, a user task completed through POST /api/v1/tasks/{id}/complete. Deploying BPMN through /api/v1/process-definitions, completing service jobs and every read are free.

Two things are optional and paid: one-off credit packs (small €5 for 5,556 credits, medium €20 for 22,223, large €50 for 55,556) and a monthly scheduling-priority subscription (Free €0, Priority €29.90, Business €598, Always on €4,186), which buys queue order under load only. See pricing.

A start that fails is refunded: the credit is taken before the start and given back when the body is not valid JSON (400) or the process cannot start (422). Once an instance has started, its credit stays spent whether it completes or later enters INCIDENT.

Yes. New accounts get 100 credits at signup, and the API key arrives in the welcome email once the address is verified. After that, 100 more credits arrive every 24 hours. No credit card is required, and no credit expires.

You cannot spend more than your balance: a charged call your balance cannot cover returns 402, and no card is charged unless you asked for it. When the balance falls to 30, 20 and 10 credits you get an email and, if you subscribed a webhook to it, a credits.low event.

Most BPMN 2.0 elements are compatible. The main differences are:

Supported: All standard BPMN 2.0 elements, Zeebe-style service task definitions (zeebe:taskDefinition), and most Camunda Modeler extensions.

Not supported: Camunda 7 Java delegate expressions (camunda:class, camunda:delegateExpression), Groovy scripts in script tasks, and embedded Spring beans. These must be replaced with service tasks and external workers.

See the Camunda 7 Migration Guide for step-by-step instructions.

Priostack supports BPMN 2.0 (the current OMG standard). The execution semantics follow the Zeebe model and zeebe:taskDefinition is read. Workers talk to Priostack over HTTPS and JSON under /api/v1 (there is no gRPC), so Camunda 8 workers keep their job logic but need their transport rewritten.

Yes. Priostack accepts standard BPMN 2.0 XML. You can use Camunda Modeler, bpmn.io, Signavio, or the built-in Priostack Designer. The Designer is recommended as it generates the correct Zeebe extension elements automatically.

Base BPMN 2.0 elements are compatible. Activiti/Flowable-specific extensions (like activiti:assignee) need to be replaced with Zeebe equivalents (zeebe:userTask).

Process definitions, instance state, variables and jobs are kept server-side in JSON files, written atomically on every change and reloaded at start, so running instances survive a restart. There is no PostgreSQL or S3 backend today. Traffic is served over HTTPS.

There is no automatic purge: completed instances and incidents are kept until the account is deleted. You can read them through the API at any time.

Yes. GET /api/v1/process-instances returns your instances as JSON (narrow it with filter.* parameters), GET /api/v1/process-definitions/{key}/xml returns each model, GET /api/v1/incidents/export returns incidents as CSV, and GET /api/usage/export returns your credit ledger as CSV. Your data is always yours.

No. Each account is fully isolated. Process definitions, instances, variables, and API keys are scoped to your account and are never visible to other accounts.

Priostack targets 99.9% uptime. The current status and historical uptime are available at status.priostack.com. Subscribe to status updates via email or RSS.

Planned maintenance is announced 72 hours in advance via status.priostack.com. During maintenance windows, new instance starts may be briefly queued. Running instances and active jobs are not affected - workers will see temporarily empty activate responses and should retry normally.

Community support (free): Community Forum - typically answered within 24 hours by the community and Priostack team members.

Email support (free): support@priostack.com - 2 business day response time.

Yes. The Priostack Community is available at community.priostack.com. It includes discussion threads, process templates, and integration examples. A Discord server is planned for Q3 2026.

Not currently. Priostack is a managed service, and the platform is not available for self-hosting.

Upcoming features (subject to change):

• Official Go, Python, and JavaScript SDKs (Q2 2026)
• PostgreSQL-backed state store for enterprise HA
• US and APAC data residency regions
• API key scoping (fine-grained permissions)
• Process version comparison and diff tooling
• Real-time process monitoring with WebSocket events
• Partner ecosystem integrations (Slack, Jira, Salesforce)

The current API version is v1 (path prefix /api/v1/). We follow semantic versioning. Breaking changes are introduced only in new major versions (v2) with at least 6 months of deprecation notice. Minor improvements and new endpoints are added to the current version without breaking changes.

Yes. The Priostack Partner Program is available for consultants, system integrators, and technology partners. Apply at priostack.com/partners.

Not today. White-labeling is not offered; the only things sold are credit packs and scheduling priority.

Yes. The Priostack Certification Program offers online self-paced courses and proctored exams for BPMN Practitioner, Process Architect, and Platform Engineer roles.

Please report security vulnerabilities responsibly by emailing security@priostack.com or following our security.txt. Do not file public GitHub issues for security vulnerabilities. We target a 72-hour initial response for all security reports.

Yes. Priostack is GDPR-compliant. A Data Processing Agreement (DPA) is available for all accounts - download it from Console → Settings → Legal, or email legal@priostack.com. We act as a data processor; you remain the data controller for all process instance data.