Security and data/Architecture and deployment

A phone, an encrypted connection, a cloud application.

How AIMIS is built and deployed, at the level a reviewer needs before an architecture conversation. Nothing on this page is proprietary. The detailed diagram is available on request.

Request the security overview Trust center

Cloud application · Vendidit operated · Amazon Web Services

Data flow

From the photograph to the export.

PhoneCapture device · iOS / Android

Encrypted transportTLS in transit

AIMIS cloud on AWSVendidit operated · region us-east-1

Identification serviceCommercial AI · provider agnostic

ExportCSV and PDF to the customer

What leaves the device

Photographs and the item data built from them. Location metadata is attached to every photo when the phone's location permission is on — the OS permission is the control.

What is stored

Records and photographs, until the customer deletes them. Object storage, the database and its backups are AES-256 encrypted (AWS-owned keys).

What leaves the cloud

Only the export the customer takes, and photographs sent to the identification service for processing.

Deployment models

What is offered today, and what is not.

Each model is stated with its status. Where something is not offered, the page says so and says why.

ModelDescriptionStatus

Standard cloudMulti tenant application operated by Vendidit on AWS. The default for walkthroughs, pilots and production.Available

Dedicated tenantA separate account or region for one organization, with the same application. Not built for any customer today.Not offered today

Isolated or on premisesA copy running inside a customer environment with no outbound calls. Identification depends on a hosted service today, so this is not offered.Not offered today

Restricted areasWhere camera or device use is restricted, capture happens where policy allows, during packing or staging outside the area. Scoped per facility.Scoping conversation

Controls

The short list a reviewer asks about first.

Items still to be confirmed are marked. Nothing marked ships.

ControlTodayDetail

Encryption in transitTLS for every connection from the phone and the browserTLS 1.2 or higher. Plaintext connections are refused outright, not redirected.

Encryption at restObject storage: AES-256. Database storage: AES-256AWS-owned keys (AES-256). No third-party or customer-managed key-management service is in use.

Tenant separationLogical separation by organization, enforced at the query level. Not a database-level tenant model.Shared infrastructure across all customers; dedicated tenancy has not been built.

Access controlRole based, administered by each moving company's own staff accountsStaff roles today: admin, moving company admin, supervisor, field, desk — plus each customer's own self-service account

Audit eventsEvery custody action — capture, lock, receiving check, identification confirmation — hash-chained and tamper-evidentNo general-purpose "who did what" log exists beyond this custody chain

Backups and recoveryNo recovery-time or recovery-point objective is documented or tested todayBackup frequency and retention: continuous, with point-in-time restore; 3-day retention window

MonitoringError and performance monitoring, plus infrastructure and application logs, both live todayLogs are stored in AWS CloudWatch within the managed hosting environment

Identification serviceCommercial identification API. Provider agnostic — every suggestion is reviewed by a staff member before it becomes part of the record.Customer photographs are never used to train identification models · Subprocessor list

Request the architecture diagram.

Provided under non disclosure agreement to organizations in an active evaluation.

Request the security overview