DynamicForm Start free trial
Step 1 of 15 · Why DynamicForm · topic 4 of 5

Fits a modern estate

Built for multi-channel, API-first systems

DynamicForm does not replace your systems. One model serves every channel over APIs, runs on your own database and calls the services you already have.

Multi-channelThe same model draws standard web pages in the browser and screens in the Android app.
API-firstScreens, data and workflows are served over documented REST and OData APIs, so other systems can use them.
Your databaseBusiness data in your own relational tables on SQL Server, Oracle or MySQL; case history in a document store.
Calls your servicesEach outside service or microservice is registered once and called by the server at the right step.
Scales outRun several servers behind a load balancer, sharing a Redis cache and real-time updates.
Stays fastDashboards and work lists are served from Redis as prepared results; heavy work runs in the background.
Cloud-basedHosted by us as a service; larger set-ups by discussion.
One model serves every channel and calls your servicesDynamicForm in the middle holds screens, workflows, menus and the AI configurators. Above it, the web browser, the Android app and other systems using its APIs. Below it, your SQL database, your services called by the server, and scale-out across several servers.One model serves every channel and calls your servicesWeb browserStandard web pagesAndroid appSame screens, offlineOther systemsREST and OData APIsDynamicFormone model, run directly by the engineScreensWorkflowsMenusAI configuratorsYour SQL databaseSQL Server, Oracle, MySQLYour servicesCalled by the serverScale-outMany servers, one cache
DynamicForm in the middle; the web, the Android app and other systems above; your SQL database, your services and scale-out below.

Try it with your own requirement document

Start the free trial, upload your document and see the first stage generated.

Start free trialTalk to sales

Updated 30 September 2026