Engagement paths
Pricing starts with the workflow you need to prove.
ARQEN is sold around quality-operating scope, user groups, deployment needs, security review, and integration depth. We do not publish one-size-fits-all pricing because pilot, launch, local, cloud, sovereign, and enterprise paths carry different operating boundaries.
Buying path
Pilot
Start here
For a focused workflow evaluation using controlled sample or pilot-context data.
Best for: A quality leader proving one workflow before broad rollout.
Data boundary: Controlled sample or approved pilot-context data.
- 1-2 configured quality workflows
- Home / Quality Attention walkthrough
- NCR/CAPA, Supplier/Audit, Inspection, or Traceability setup focus
- Management Review summary demonstration
- Traceability and evidence-reference export demonstration
- Pilot success criteria and onboarding workshop
Boundary: Pilot work is scoped for evaluation. It does not enable production writes, certified reporting, or controlled evidence storage by default.
Contact us
ARQEN Launch
Hosted pilot
For a hosted pilot workspace covering non-sensitive workflows and buyer evaluation.
Best for: Teams that want a guided workspace without handling sensitive records publicly.
Data boundary: Non-sensitive pilot/demo workflows only.
- Hosted workspace setup when launch URL and access path are configured
- Multiple operating surfaces for a guided team evaluation
- Review Action, Management Review, and Reporting walkthroughs
- Screenshot walkthrough and app-access boundary support
- Readiness review for future integrations and production gates
Boundary: Launch is not a regulated production workspace unless a separate production agreement and required controls are implemented.
Custom
ARQEN Local
Local-first
For local-first evaluation, parser review, QOS rehearsal, and private pilot workflows.
Best for: Teams that need private evaluation on a local machine or customer-controlled environment.
Data boundary: Customer-controlled local data, subject to customer policies.
- Local install and update planning
- Customer-authorized sample-data handling plan
- Evidence-reference and drawing-workflow evaluation boundaries
- Backup and local-storage responsibility review
- Migration-readiness review before any production write path
Boundary: Local evaluation does not create controlled file storage, immutable audit, or production BOM/release authority unless those services are separately implemented and verified.
Custom
ARQEN Cloud
Roadmap-gated
For future hosted SaaS operation once production controls, support, and security posture are implemented.
Best for: Organizations planning a future hosted SaaS path after production gates exist.
Data boundary: Production data only after auth, tenant, storage, audit, backup, and legal gates.
- Future tenant/workspace architecture review
- Production auth and server authorization planning
- Monitoring, backup, recovery, and incident-response planning
- Data retention, deletion, and privacy-operation planning
- Module-by-module production enablement sequence
Boundary: ARQEN Cloud is a roadmap-gated production path. It is not sold as live regulated SaaS until required controls and agreements exist.
Custom
ARQEN Sovereign
Private/regulated path
For private, sovereign, or customer-controlled deployment planning where data boundaries are central.
Best for: Regulated teams with data-residency, controlled-environment, or customer-security constraints.
Data boundary: Sensitive or controlled data only after legal/security review and approved deployment design.
- Data classification and residency review
- Controlled evidence and key-custody architecture planning
- Security/legal review for restricted workflows
- Customer environment and support-boundary planning
- Validation and acceptance evidence planning
Boundary: Do not use public forms or public demo paths for ITAR, CUI, customer drawings, or sensitive production records. Sovereign work requires a controlled engagement.
Custom
Enterprise / Private Cloud
Custom
For organizations planning private deployment, integrations, validation support, and governance review.
Best for: Enterprise buyers planning integrations, governance, validation support, and private deployment.
Data boundary: Defined in the enterprise agreement and security review.
- Architecture and security review
- SSO/SCIM, roles, and tenant/workspace planning
- Audit-event persistence and evidence-storage architecture planning
- Integration planning for ERP, QMS, inspection, document, or supplier systems
- Validation-support and rollout-governance planning
Boundary: Enterprise controls depend on the deployment path. Production auth, tenant isolation, durable persistence, controlled evidence, e-signature, and certified reporting are gated work.
Custom
Prove value
Start with one workflow, known users, sample or approved pilot data, and measurable review outcomes.
Choose boundary
Hosted pilot, local-first, sovereign/private, or future cloud paths carry different data and control assumptions.
Gate production
Production writes, durable persistence, auth, tenant isolation, controlled storage, audit, e-signature, and certified reporting require separate gates.
Typical pilot objective
Prove that ARQEN can reduce scattered quality records, improve review readiness, and connect quality evidence across one controlled workflow without implying production readiness before the required production gates are implemented.
Questions about security or validation? See Security & trust and the security model in docs.