High-level architecture
How components interact for FormFit scanning and manufacturing workflows.
User-facing tier
The browser loads the Forge web application from a globally distributed edge network. Scan video and photos are uploaded only over HTTPS (TLS). Uploads typically use time-limited, scoped URLs so files stream directly to object storage over encrypted connections without transiting application servers for the raw bytes.
Application core
The API enforces authentication, orchestrates scan and order state, issues storage grants, and enqueues work. A relational database holds structured records; a queue/cache tier coordinates asynchronous jobs and worker capacity. Identity fields (for example name and contact information) are stored separately from scan video, images, and mesh artifacts, so those categories are not commingled in one identifiable bundle in our data model.
Processing tier
Isolated compute instances run mesh generation and manufacturing prep on Vitacore-owned hardware and software in British Columbia, Canada, on our local, airgapped network. They are not reachable from the public internet. They read and write through the same storage and database contracts as the API, not via ad-hoc public endpoints.
Hosting
Scan reconstruction and related processing run on Vitacore-owned hardware and software in British Columbia, Canada, on a local airgapped network (no public internet ingress to those systems). Photogrammetry reconstruction runs in that same environment. Customers may connect from anywhere; traffic uses secure, encrypted connections between the customer's device and our systems (HTTPS/TLS).