Arqen Edge
Arqen Edge is the runtime your development team builds on: they declare the application in a signed manifest, the kernel executes it deterministically on any site — online or offline.
Back to Arqen PlatformThe manifest is the software
Your developers declare screens, actions, rules and roles in a JSON manifest following the Arqen technical specification. Updating a deployed fleet means publishing a new version — not shipping code.
Five engines, one transaction
Formula computes, Action/FSM governs states, Data-Link connects data, RBAC authorizes and Constraint validates. Every action flows through the whole pipeline in a single deterministic transaction: same input, same output, always.
Offline-first, for real
PIN login, business actions and local audit all work without Internet. When connectivity returns, the CDC outbox drains events to the cloud with retry and dead-letter — the store never stops.
Audit chain & RLS
Every action enters an append-only SHA-256 hash chain verified on schedule; tenant isolation is enforced by PostgreSQL FORCE ROW LEVEL SECURITY — a database guarantee, not a code convention.
Resilient synchronization
Circuit breaker, backoff retry, end-to-end idempotency and automatic snapshots before every remote migration: the sync layer is designed to survive failures, not to avoid them.
One engine, your applications
We ship the engine, not the apps: retail POS and field service are our reference manifests proving the same container runs any domain. Your domain is a new manifest — tables, SQL migrations and UI included — not a code fork.