IT & deployment. Nothing to install.
Written for the IT and engineering people who have to live with whatever gets bought.
What deployment involves
Days, not a project
There is no server to stand up, agent to roll out, or VPN to change. The site's plant model and first rounds are built in the product — the first real round has gone live within days of starting, and that pace is the working assumption.
No workstation footprint
Amberhold runs in the browser — desktop, tablet, and the phones operators already carry. Evergreen Chrome, Edge and Safari are supported; there is nothing to package or patch.
No inbound network changes
All traffic is outbound HTTPS to the application's own domains. No firewall inbound rules, no site-to-site links, no on-prem components.
Architecture
Managed Google Cloud, London region
Containerised application services (Cloud Run) with a managed PostgreSQL evidence store (Cloud SQL), static delivery via a global CDN edge. All primary infrastructure sits in europe-west2 (London).
Tenant isolation in the data model
Customer data is partitioned by tenant with server-enforced scoping — cross-tenant references are rejected at the database layer, not just filtered in code.
Identity
Microsoft Entra ID single sign-on, so your own directory decides who your people are and your existing policies apply unchanged. Individual, invitation-first accounts where a site prefers them — no shared logins, no self-signup. Either way, signing in never grants access by itself: a membership on the site does, and revoking it takes effect on the next request.
Interfaces
API
A versioned, documented read API is live: GET /api/v1/sites/{siteId}/readings, described by an OpenAPI document you can read without an account. It serves the same projection as the CSV export, so a report and a spreadsheet can never disagree about a reading. Systems authenticate with their own Microsoft application identity — see Machine identity.
Reporting stance
Your data is not locked into our dashboards: the intent is that you plug your own tools (Power BI, Grafana) into exported or API data rather than being sold ours.
Support
Engineer-level, direct
Support goes to the people who build the product — no ticket tombola, no tiers of script-readers. UK working hours, with the pragmatism of a supplier whose whole reputation rides on a small number of sites.
A question this page didn't answer?
Ask it directly — supplier questionnaires and security reviews are answered promptly, by the people who built the platform.