Common questions.

SurveyOS is a tablet-first inspection platform for marine surveyors, mechanics, and their insurance partners — one field capture produces multiple professional report outputs with a defensible audit trail.

Marine surveyors (independent, NAMS-SAMS certified, or practice firms), marine mechanics and yard foremen, insurance underwriters and brokerages, and multi-site operators (yards, marinas, fleet-service businesses).

The Phase 1 MVP ships with a full template for inboard-diesel sportfish vessels, with the 1984 Egg Harbor 35.5 / 36 as the reference profile. The schema supports any vessel type — sailing, outboard, commercial, multi-hull, personal watercraft — and additional templates are added as tenants onboard.

No. SurveyOS is standards-aware, not standards-authoritative. We attach references (family + key + your plain-English topic note) to findings, but we never reproduce copyrighted standards text. Your reports stay clean; the referenced authority stays authoritative.

When you start an inspection session, all checkpoints materialize into the tablet's local database. You can complete the entire inspection with no connectivity. Every answer is queued with a client-generated sync ID so retries are idempotent. Once you get signal — at the marina, in the truck, at the office — the batch uploads automatically.

Three things. First, the observation / inferred cause / recommendation trichotomy is enforced at four layers — UI, API validation, database constraint, and report renderer. Second, evidence is SHA-256 anchored on capture and frozen on report issuance. Third, every state change writes to an append-only audit log at the database level. A report's content hash is deterministic from its payload, so tampering is detectable.

Not directly. The original finding remains in the issued (frozen) report. To update, you supersede — a new finding is created, linked bidirectionally to the original. Reissuing the report creates a version 2 that supersedes version 1. Both versions are preserved in full.

Evidence uploads require SHA-256 verification on commit. Once referenced in an issued report, evidence is frozen — a database trigger refuses any attempt to modify or delete it. Storage is S3-compatible (AWS S3, Cloudflare R2, or bring-your-own via presigned URLs).

At two layers. First, the application always queries with tenant scope through withTenant() transactions. Second, Postgres row-level security policies on every tenant-scoped table enforce isolation at the database — if application code has a bug, the database still refuses to cross tenants.

REST API with tenant-scoped tokens on Firm and Enterprise tiers. Webhooks fire on engagement.created, finding.added, report.issued, and work_order.completed. SSO / SAML on Enterprise. Direct integration with AlphaGentic CRM, FleetOS operations, and custom claims systems via API.

Yes — on Practice, Firm, and Enterprise tiers. Your logo, your letterhead, your disclaimer language, your signature block. Enterprise can fully theme the rendered HTML and PDF output.

Yes. Full export of audit trail, findings, evidence, and frozen report packages as CSV + JSON + ZIP, at any time. Your work is yours.

Yes — 14 days of full-product access, no credit card required. Reports generated during the trial are preserved if you convert to a paid plan.

FleetOS and SurveyOS are sibling products under VesselGrade. FleetOS covers charter and rental operations (booking, crew, revenue, fleet management). SurveyOS covers inspection, survey, and condition reporting. They share the same design language and will eventually cross-integrate, but they're separate products serving separate jobs.

Phase 2 introduces multi-agentic workflows: AI-assisted finding drafting with human approval, automated standards cross-referencing, and agentic report composition. Phase 1 is the audit-defensible foundation; Phase 2 rides on top.