STATUS AS OF OCTOBER 20, 2026
Security starts with
an accurate account.
Tav has a public synthetic demo, local record tools and a separate private beta verified with synthetic data. Customer access is not available. This page distinguishes working software from the operational checks still required.
What the public demo does today
- Displays bundled, invented robot records and evidence references.
- Runs comparisons in your browser. Selections reset on refresh.
- Has no uploads, customer database, analytics, authentication, or lead-storage form.
- Does not connect to robots or send configuration changes.
- Contact links open your email app or configured contact service. That provider handles what you choose to send.
When publicly hosted, the hosting provider may process standard request logs. Local preview runs on your computer; no public deployment is claimed here.
Certifications and independent assurance
No Tav certifications or independent security audits are claimed. No evidence of SOC 2 or ISO 27001 certification has been supplied. A future provider’s certification would not certify Tav.
Verified assurance details, scope, dates, and supporting references will be added when available.
Local record workspace
The development-only workspace imports approved JSON metadata into browser memory, records manual hardware reports and runs, compares exact revisions, and exports JSON files. It is excluded from the public static release. Files are not uploaded; no browser database or automatic backup is used. Refreshing or closing the tab loses the session unless you exported it.
Corrections append author, reason and prior revision while preserving historical run references. Authors and evidence availability are user-reported. An editable local file is not authenticated or tamper-proof. Structural validation is not a universal secret detector. Keep private exports outside the repository; do not import credentials, raw source, weights, datasets or recordings.
Local collector · October 9, 2026
The separate Python collector reads explicitly configured local sources and produces metadata-only JSON for manual inspection and import. It records Git commit and dirty state, file hashes, selected measurements, and visibly manual hardware reports. Capture itself does not upload or change robot configuration. A separate upload queue can send reviewed metadata to an authenticated beta endpoint with a scoped credential. Missing inputs remain unknown; user-supplied text still requires review for sensitive information.
An optional ROS 2 adapter reads one allowlisted numeric parameter through the configured ROS environment, which may use its network. The base collector works without ROS. Live robot trials and pilot-engineer validation remain outstanding.
Private beta: verified with synthetic records
The app runs locally with hosted Supabase Auth and PostgreSQL, separately from this public demo. Synthetic persistence, organization isolation and ingestion checks passed on October 18; pilot measurement checks passed on October 20. Verified controls include:
- Organization-scoped accounts and invite-based owner, member, and viewer access.
- Authorization and database policies tested across two organizations, including references and exports.
- Server-enforced immutable revisions and an authenticated submission audit, while imported author names remain user-reported.
- Scoped, revocable collector credentials; server-side privileged keys; allowlisted metadata and bounded ingestion.
- Record export, organization deletion, and documented backup restoration and recovery procedures.
Source code, credentials, raw weights, datasets, and recordings are outside the upload scope. The private-beta software accepts approved metadata, hashes, and references. Imported author names and physical confirmations remain user-reported. These synthetic checks do not establish production readiness or independent security assurance.
Required before customer hosting
Managed backup restoration, production hosting and TLS, separate environments, operational error monitoring and request limits must be configured and verified. Account email delivery and production account policies also need activation and checks. A local PostgreSQL recovery test has passed; it is not a managed Supabase recovery drill. No customer retention period or recovery-time guarantee is claimed before the operating policy is agreed and tested.
Contact
For a security concern, start with a sanitized description. Do not email secrets or private robot records.
Contact the founders →