Managed cloud
We run it for you.
- Where it runs
- Our infrastructure, in a database of your own.
- Connection to us
- We operate the service.
Run IndeForms in our cloud, in your own network, or sealed off from the internet. Your records stay where you put them, and the AI features never see what your people submit.
Each customer has its own database and its own credentials, so one customer cannot read another.
Stored integration credentials are encrypted with AES-256-GCM. Data on phones can be encrypted on the device, so a lost handset gives up nothing readable.
Role-based permissions are checked on every request and denied by default. Sign in through your own identity provider (SAML or OIDC), with a second factor.
Every form change and every status change is recorded with who and when. A submission stays tied to the exact form version it was filled in on.
The signer confirms their identity again at the moment of signing. A signature is bound to one record and cannot be reused.
Submissions are deleted on the schedule you set, after a grace period. Requests to export or erase a person’s data run as tracked jobs.
Voice dictation and text recognition read what a person captured, so they work only with a model running inside your own environment.
Yes. Air-gapped is a supported way to run it. The licence is checked locally, renewals are delivered by hand, push alerts are replaced by in-app updates, and AI features stay off until you connect a model you host.
On-premise and air-gapped: in your own database and file storage, with no copy on our side. Managed cloud: on infrastructure we operate, in a database of your own.
No. Models receive form structure, the question a user types, and totals. Voice dictation and text recognition read captured content, so they run only with a model inside your own environment.
With device encryption switched on, the data stored on the phone cannot be read without the user’s sign-in. Removing the user in your identity provider stops that phone receiving any more work.
Yes. SAML 2.0 and OIDC are supported, with your directory groups mapped to roles. You can require single sign-on and turn local passwords off.