What we run
Service Database Access
Applications retrieve their initial configuration and ongoing state from the service database through authenticated REST endpoints. Responses are versioned so deployments can roll forward safely, and every request is scoped to the calling deployment's tenant. Writes are idempotent: field software retries freely after power cuts and network drops, and the server resolves conflicts on versioned records.
Usage Metrics
A batched metrics API receives application usage events and aggregates them for analytics, capacity planning, and operational monitoring. The footprint is deliberately tiny — a few kilobytes per installation per day — so reporting stays invisible even on metered links.
License Validation
License checks return signed entitlement responses, supporting offline grace periods and automated revocation handling. Raw keys never cross the wire; every validation lands in an exportable audit log.
The lifecycle
- Phase 1 — Init
First boot: the installation presents its license credential, receives a deployment identity, and pulls its baseline configuration profile.
- Phase 2 — Sync
The service subscribes to configuration updates. Central changes propagate to the fleet without redeployment.
- Phase 3 — Operate
Steady state: database reads and writes flow through the API; metrics upload in scheduled batches.
- Phase 4 — Attest
License re-validation runs on a schedule, building the audit trail your compliance team exports from the dashboard.
Built for real networks
Everything is outbound HTTPS on port 443 to a documented set of hostnames — nothing inbound, nothing exotic. Behind a strict proxy or an allowlist-only firewall, a static IP option keeps the integration one firewall rule long. And when the network disappears entirely, cached configuration and license grace windows keep software running until connectivity returns.
Questions
Which platforms are supported?
Windows 10/11 and Server 2019+, glibc and musl Linux via the client library, or anything that speaks documented HTTPS/JSON.
How does offline operation work?
Configuration is cached locally and licenses carry a configurable grace window. Metrics queue on disk and flush when the API is reachable again.
Who can see our metrics?
Only your organization. Data is tenant-scoped end to end and processed solely to provide the contracted service, per the Privacy Policy.
Does this replace our database?
No. It is the access, telemetry, and licensing layer in front of the service database that backs your product — not a general-purpose database offering.