Security and trust

Clear tenant boundaries. Verifiable operational evidence.

Uptivra is designed so customer separation, least privilege and safe background execution are properties of the system—not dashboard promises.

Fail closed

Missing tenant context, invalid scope or uncertain authority denies the action.

Callers cannot select tenant authority through payloads, jobs or provider data.

Incidents, delivery outcomes, audit records and report snapshots remain attributable.

Controls in the beta

These are shipped architectural controls. Uptivra does not claim certifications it has not earned.

Application authorization and PostgreSQL row-level security reinforce each other for requests, jobs, reports and webhooks.

MSP owners, administrators, technicians, viewers and customer roles receive explicit, customer-scoped permissions.

Provider credentials, webhook secrets and probe tokens are encrypted or one-way hashed, never returned after creation.

Central workers enforce public-target and safe-port rules; private targets require signed site-probe assignments.

Sensitive changes, support access, key rotation, incidents and report delivery produce immutable tenant-scoped audit records.

Webhook signatures, replay protection, durable leases, idempotency and bounded retries protect external event processing.

Layered authorization

Authenticated principal→Role & customer scope→Tenant transaction→PostgreSQL RLS→Audited result

Responsible disclosure

Please send a clear description and reproducible evidence to our security contact. Do not access another customer’s data or disrupt service.

Clearer operations start here

Request a team-guided 14-day Growth trial. No card required. Access begins only after our team confirms fit and creates your tenant.