Workflow architecture built around durable business execution.

01 / ARCHITECTURE

Keep authority at the application and organization boundary

The browser and Android companion are clients of the platform. The server establishes identity and evaluates organization membership, roles and scopes before protected work is performed. Client presentation and local subscription state are not independent sources of authority.

PostgreSQL-backed state holds business data, definitions and operational records within the multi-tenant organization model. Row-level controls and server-side checks work together to enforce tenant boundaries. The architectural objective is to make the subject and scope of an operation explicit.

02 / ARCHITECTURE

Separate definition change from running execution

Published process and form versions provide stable definitions for runtime use. Running instances pin the version they execute, so a newly published design does not silently replace their history or future steps. Application packaging extends this principle into release, installation and upgrade workflows.

A durable job represents work that must survive beyond an individual request. Workers claim eligible work using time-bounded leases, and fencing concepts prevent a superseded worker from committing as though it still owned that work. These controls address concurrency and interruption; they are not a promise that an external system can never observe a duplicate request.

03 / ARCHITECTURE

Operate waiting, failure and recovery deliberately

Timers and scheduled occurrences depend on deployed worker and scheduler operation. Idempotent handling, bounded retries and incidents support recovery from supported failures. Operational history provides evidence of what the runtime recorded so an operator can investigate before retrying.

Private object storage supports controlled attachment delivery. Email infrastructure supports configured notifications. Billing verification is a separate server-side responsibility that determines organization plan capabilities. These services have distinct roles rather than allowing a client or integration response to grant arbitrary platform authority.

04 / ARCHITECTURE

Understand the technology in its operating context

The web application uses Next.js on Vercel, with PostgreSQL through Neon for persisted state. Clerk supplies identity infrastructure, Resend supports email and Vercel Blob provides private object storage. RevenueCat participates in subscription receipt processing while verified backend state determines organization entitlements.

The Android companion provides a mobile entry into supported platform work and subscription flows. It does not replace the server execution model. During technical evaluation, discuss the complete path from a client action through authorization, persistence, worker execution and operational inspection.

• Inspect a running process across a version change.
• Exercise a retry and review the recorded outcome.
• Check tenant-scoped access from more than one role.
• Review package requirements and recovery procedures.

Questions for technical evaluation

How should a workflow architecture be designed?

Use the educational guide to frame the design decision before comparing product capabilities.

• Workflow Automation: Architecture, Use Cases and Governance
• Building Operational Applications Around Business Processes