Cloud backend for instrumentation-class device software
Arcatraz Systems runs the server infrastructure behind device applications: a configuration database API, usage telemetry ingestion, and software license validation for Windows and Linux deployments. This page documents the platform's purpose, components, and operational requirements.
Architecture
The platform is split into three independent services behind a single API gateway. Each service scales and audits on its own, but they share one authentication layer — a deployment authenticates once and receives scoped access to all three.
| Component | Endpoint family | Primary role |
|---|---|---|
| Configuration Database | /v1/config/* | Profiles, device parameters, tenant settings |
| Metrics Ingestion | /v1/metrics/* | Usage counters and diagnostic signals |
| License Service | /v1/license/* | Signed entitlement verification |
Configuration Database
Applications fetch device profiles, firmware parameters, and tenant settings from the service database through authenticated, TLS-encrypted API calls. All responses are versioned; clients request a schema version and receive data they are guaranteed to understand, so the platform can evolve without stranding older devices in the field.
Writes are idempotent by design. Device software can safely retry any failed request after a power cut or network drop, with conflicts resolved server-side using last-writer-wins semantics on versioned records.
Usage Metrics
Device software reports usage counters and diagnostic signals in compact batches. The ingestion pipeline validates envelopes, discards duplicates, and aggregates events into fleet-level statistics for the deploying organization's operational teams.
Typical footprint is a few kilobytes per device per day — small enough for metered links and bandwidth-constrained sites. Payloads carry a deployment identifier, never a user identifier.
License Validation
Signed license verification supports per-seat and volume entitlements, offline grace periods, and revocation checks. Raw license keys never traverse the network: the client answers a signed challenge, and the response carries the entitlement state with a configurable grace window for disconnected environments.
Every verification is written to an audit log that the customer's compliance team can export from the dashboard.
Network Requirements
| Requirement | Value |
|---|---|
| Direction | Outbound only (no inbound listeners needed) |
| Protocol / port | HTTPS / TCP 443 |
| Hostnames | Documented, fixed set; static IP allowlist available |
| Offline tolerance | Cached config + license grace window (configurable) |
FAQ
Which platforms does the client library support?
Windows 10/11 and Server 2019+, plus glibc and musl Linux builds. The wire protocol is documented HTTPS/JSON, so custom integrations are straightforward.
Can the platform work behind a strict corporate proxy?
Yes. All traffic is standard outbound HTTPS; proxies with TLS inspection are supported, and a static IP option exists for allowlist-only firewalls.
What happens if the API is unreachable?
Devices continue operating on cached configuration and their license grace window, and queue metrics locally until connectivity returns.
Is any personal data collected?
Metrics are keyed by deployment, not by person. See the Privacy Policy for the full data inventory.