Frequently Asked Questions

Priostack uses a pay-as-you-go credit system. Each process instance start costs 1 credit. There are no monthly fees or per-seat costs. Credits never expire.

Every account gets 100 credits at signup and 100 free credits every month; a workflow instance start or a human task completion costs one credit. There is nothing to buy.

Yes. Credits are deducted when the instance starts, regardless of whether it completes or enters an incident state. This is because the engine resources are consumed from the moment the instance is created.

Yes. New accounts receive 500 free credits automatically upon signup. No credit card required to get started. Free credits do not expire.

Yes. You can set a low-balance alert threshold in Console → Settings → Billing. When your balance drops below the threshold, you'll receive an email and (if configured) a credits.low webhook event. A hard limit that auto-pauses the account is on the roadmap.

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 workflow engine model (compatible with Camunda Platform 8 worker protocols).

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 instance state, variables, and job data are stored server-side in Priostack's managed storage. Data is encrypted at rest (AES-256) and in transit (TLS 1.3). The primary region is EU (Frankfurt). Data residency options for US and APAC are on the roadmap.

Completed and terminated instances are retained for 90 days by default. Incidents are retained for 1 year. You can export instance data at any time via the API or Console before the retention period expires.

Yes. Use GET /v1/process-instances?format=csv or format=json to export instance data. Process definitions can be downloaded from Console → Process Definitions → Export. We believe in data portability — 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.

Priority support (Enterprise): 4-hour response SLA with dedicated Slack channel and quarterly architecture reviews.

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 SaaS service, and the platform is not available for self-hosting at this time. Enterprise customers can request dedicated single-tenant deployments.

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.

White-labeling is available for Enterprise customers under a separate agreement. This includes custom domain support, branded console UI, and removal of Priostack branding from API responses. Contact sales@priostack.com for details.

Yes. The Priostack Certification Program offers online self-paced courses and proctored exams for BPMN Practitioner, Process Architect, and Platform Engineer roles. Group training packages are available for enterprise teams.

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.