Security

Last updated: June 10, 2026

This page describes how the DeviceNexus platform is built and operated from a security standpoint. It is written to be accurate rather than impressive — if you have questions it does not answer, ask us at security@devicenexus.ai.

Architecture

DeviceNexus is a multi-tenant SaaS platform with strict per-tenant scoping:

• Tenant-scoped APIs. Every API request is authenticated and resolved to a single organization (enterprise). Devices, recordings, datasets, training jobs, and models are owned by exactly one tenant, and all queries are scoped to the authenticated tenant. Cross-tenant isolation is part of our end-to-end test suite.
• Authentication. Users authenticate through our identity provider, which issues short-lived (15-minute) JWTs signed with RS256. Services verify signatures against the public key; tokens carry the user’s organization and module entitlements. API keys and device credentials are scoped to a single tenant.
• Devices. Robots and edge devices enroll using tenant-scoped enrollment tokens with configurable expiry and use limits, and thereafter authenticate with per-device credentials. Device connections are outbound from the device to the platform over TLS — robots do not need inbound ports open.
• Encryption in transit. All traffic between browsers, devices, and the platform is encrypted with TLS. Public endpoints are fronted by Cloudflare; origin connectivity uses Cloudflare Tunnels, so origin servers do not expose public inbound ports.

Data Storage

• Application data (device registry, account data, job metadata) lives in managed databases on Google Cloud Platform.
• Large artifacts — camera recordings, datasets, and trained model checkpoints — are stored in Cloudflare R2 object storage, accessed through tenant-scoped, time-limited signed URLs.
• Both providers encrypt stored data at rest by default.

How customer data is processed, who our infrastructure providers are, and the contractual terms governing both are documented in our Privacy Policy, Data Processing Addendum, and Sub-processors list.

Backups

Databases are backed up nightly. Backups are verified by periodically restoring them and checking integrity — a backup we have not restored is treated as a backup we do not have.

Operational Practices

• Production access is limited to the operations team and is credential-gated; customer data is accessed only for support and debugging, and only as needed.
• Secrets (API keys, signing keys, database credentials) are rotated when exposure is suspected, and we are consolidating secret storage into dedicated tooling as part of our pre-launch hardening.
• Dependencies are monitored for known vulnerabilities and updated on a regular cadence.

Compliance Posture — An Honest Note

DeviceNexus does not currently hold a SOC 2 attestation or ISO 27001 certification. We are an early-stage company; a SOC 2 Type I engagement is on our roadmap as the customer base grows. In the meantime, we are happy to complete security questionnaires, walk your security team through the architecture, and contractually commit to the practices described on this page. We would rather tell you exactly where we are than imply a certification we do not have.

Responsible Disclosure

If you believe you have found a security vulnerability in DeviceNexus, we want to hear about it:

• Email security@devicenexus.ai with a description, reproduction steps, and the affected endpoint or component.
• Please do not access data belonging to other tenants, degrade the service, or publicly disclose the issue before we have had a reasonable opportunity to fix it.
• We will acknowledge reports within 3 business days, keep you informed of progress, and credit you (with your permission) when the fix ships. We do not pursue legal action against good-faith research that respects the guidelines above.

Contact

Security questions and vulnerability reports: security@devicenexus.ai