Encryption
Data encrypted in transit (TLS 1.2+) and at rest (AES-256).
Security & architecture
A reviewable, one-way, read-only architecture designed to pass IT, OT, and security review. Control systems stay inside their existing boundary. This page is the artifact your technical team can forward internally.
Architecture
LIMIS reads from an approved endpoint and presents context in the workflow layer. There is no inbound path to control systems.
Arrows flow left to right only. A detailed data-flow diagram is included in the downloadable brief.
Security posture
The specifics below are written for a security questionnaire and technical review.
Data encrypted in transit (TLS 1.2+) and at rest (AES-256).
Role-based access across IT, OT, operations, quality, and leadership. SSO / SAML available on enterprise plans.
Source access uses a least-privilege, read-only service account or equivalent reviewed integration pattern.
Submissions, reviews, role changes, exceptions, and timestamps are logged and traceable.
Certifications & compliance
Independent assurance, not just our own assertions.
For food & beverage and pharma-adjacent lines: support for 21 CFR Part 11 controls, electronic signatures, and a GxP-ready audit trail.
Hosted in [region] with options for [additional regions].
Deployment
Deployment is one of the first questions an OT team asks. Here are the options.
Default. Hosted on [cloud provider, region], with a dedicated tenant for your data.
Available for sites that require data to stay within their own network. [Confirm availability.]
Field capture works offline in dead zones and syncs when connectivity returns. Air-gapped options on request.
Ownership & exit
No lock-in. The terms of getting your data out are defined before you start.
The customer owns all submitted records and context. LIMIS presents approved data under the agreed model.
Standard export to [CSV / API / other] is included, so records remain usable outside LIMIS.
On exit, data is exported and then deleted per the agreed retention and deletion terms.
Availability target and support response times are defined per plan. See Pricing.
Technical review
We are built to be reviewed. Request the brief, or set up a session with your IT, OT, and security stakeholders.