Azure | .NET | SQL Server | IIS
When your team is picking against a clock, downtime is measured in stalled lines and late shipments. This page is about where the software runs, how your data is protected, and what happens when something fails - so you can plan operations around real targets instead of promises.
The system is a .NET stack on IIS backed by SQL Server, divided into layers that map to the way different people work each day:
Sign-in methods follow your deployment and workforce: internal credentials with configurable password policies, Single Sign-On through your identity provider (Active Directory, Okta, SAML), and OAuth 2.0 bearer tokens for API access.
Hosted in a virtualized Azure environment, with application servers and database servers kept as separate workloads. Every client runs as its own isolated instance with a dedicated database - your records are never commingled with another tenant's, and a problem in one instance does not ripple into another.
These handle web requests and hold uploaded files. Backups run on a regular schedule and are replicated across multiple storage providers.
Your business data lives here. Database servers sit behind the production network and are not reachable from outside it*. Databases are backed up continuously, which makes a point-in-time restore possible - for example, rolling back the damage from a bad bulk import or an accidental mass edit.
* Unless an integration genuinely requires it. In that case the endpoint is locked down on least-privilege principles.
Controls are aligned to NIST Cybersecurity Framework (CSF) 2.0 as the primary framework, with voluntary alignment toward ISO 27001:2022. See our Security & Compliance page for application-level controls.
Backups are layered so a single failure mode cannot take your data:
All backup data is encrypted before transmission and at rest. Backups are retained for 1 to 12 months depending on the client, with at least one copy kept on hand for every client, and self-hosted clients may retain copies longer. Backup data is deleted upon request.
| Metric | Target |
|---|---|
| Availability | 99% uptime commitment |
| Recovery Time (RTO) | 4-hour target |
| Recovery Point (RPO) | 1 hour |
Your operation's data is yours. We act as custodian, not owner: you can export any grid or report to Excel, CSV, or PDF through the built-in reporting, and if you ever leave, the data goes with you.
We never sell, rent, or share your data with third parties. Your records exist solely to run your business inside the system - not for analytics, advertising, or any purpose outside your account.
Full data handling practices are in the Privacy & Data Policy.
The same stack can run on your own Windows servers, on-premises or in a cloud you control. Self-hosted clients handle their own infrastructure, backups, and security configuration, with installation documentation, recommended configurations, and optional consulting available. See our documentation for requirements and setup.
The product uses licensed third-party components, mainly under MIT, Apache 2.0, and BSD licenses. The full list ships in the License file inside your installation. Our cloud infrastructure runs on Microsoft Azure with regional redundancy and built-in platform security controls.
See how Inventory Pro handles receiving, barcode scanning, order fulfillment, reporting, and mobile work. Start with the pages your team cares about most.