DynamicForm Start free trial

Multi-company SaaS

One platform. Each company’s data kept apart.

Run several companies on one platform. Each has its own users, applications, configuration and data, and can run several applications.

Show two generic company workspaces with separate apps, users and storage, and a separate platform administration area.

Illustrative screen

Open the right company from the start

Users never choose a company. DynamicForm recognises it from the company’s own web address or branded mobile app.

Many applications in each company

Run different work inside the same company. Every company has Main, can publish AI Core applications and can create hand-built applications. The structure is platform, company, then application.

Company sign-in, users, reporting lines, branches, holidays, roles and record scope stay shared. So do integration definitions, scoped API clients, company settings, OTP settings and the theme library. Screens, forms, lists, workflows, menus, reports, dashboards, records and documents belong to applications. Each application also owns its theme, logo, branded Android app, app key, logs and separate stores.

Company administration sits outside application work. Company administrators see it in full; helpers see only the functions their roles grant. Explore Applications · Explore Company Admin.

Platform diagram contains separate company areas, each holding application cards behind clear company and application boundaries.
Applications sit inside companies, with separate boundaries at each level.
Two columns distinguish shared company identity, organisation and settings from application designs, records, branding and separate stores.
Company settings stay shared while each application owns its designs, identity and work.

Separation at every layer

Check the boundaries

Every endpoint is denied by default unless an access rule allows it. Automated sweeps check every read endpoint for cross-company leaks. The sweep result is zero leaks.

Choose each application's stores

Give an application separate storage where it needs it. Records, documents, files, logs and cache can use company stores or their own stores. Platform policy determines which layers may be separated.

Choose logical separation within a shared store or physical separation in an application's own database, including on another server. Move layers when needed, including back to company stores. Only that application pauses during the move, and its logs follow it.

My tasks and dashboards still gather the application's work across stores. Storage choices stay within company boundaries while supporting the way each application runs.

Application storage diagram compares company, logical and physical stores across records, documents, files, logs and cache.
Choose each application's stores by data layer within platform policy.

Administration with clear boundaries

A company’s own administrator

Each company has its own administrator. A platform console handles onboarding, web addresses, mobile app keys, company suspension and ending sessions.

Separate platform operators

Platform operators are separate from company users and sign in at a separate address. Work inside a company takes place in an audited session with a stated reason.

Updated 30 October 2026