Trust · Architecture and security
Built to keep your data and your rules safe
Designers write configuration; the engines read it. Every rule the screen shows is checked again on the server.
Rules enforced twice
Screen and step access rules are applied in the browser and re-checked on the server for every submission.
Roles and branches
Menus, cases and fields limited by role, branch and process step.
Full history
Every workflow move is recorded with who, when and the data at that moment.
Encrypted sign-in
Encrypted credentials, two-factor codes, session revoke, idle-time warning.
Your choice of database
Transaction data in normalised tables on SQL Server, Oracle or MySQL; case history in a document store.
Keys stay on the server
Outside services are called by the server; phones and browsers never see credentials.
Transaction data sits in third-normal-form tables on SQL Server, Oracle or MySQL, and the platform serves web and phone over APIs. Rules shown on screen are checked again on the server.
In this stop
3 more topics on Architecture and security
- Your data, properly modelledBuilding by configuration does not mean storing data in a heap. When a screen is published, the platform creates proper relational tables for it.
- Fits a modern estateDynamicForm does not replace your systems. One model serves every channel over APIs, runs on your own database and calls the services you already…
- Open by designRecords are stored in ordinary database tables you can query with plain SQL.
Build your first app free
Up to 10 users. 30 days to build, then 30 days live after go-live.
Updated 30 September 2026