The RooftopOS Platform

One intelligence layer across the vehicle lifecycle.

A continuous record for every vehicle—activated across acquisition, inventory, sales, service, and ownership.

#demo-cta-_R_q8ckq_{display:none !important}Request a Platform Demo

See How RooftopOS Works

Departments

Acquisition
Sales
Service
Compliance
Merchandising

Reads from the record

Shared Vehicle Record

One record per VIN

2T3P1RFV5MC164821

Acquire
Verify
Service
Merchandise
Engage
Own

Structured events

Writes to the recordReads from the record

Applications

Existing systems, by category

Inventory feedsLive
Dealer websiteLive
DMSIn Development
CRMIn Development

Department
Application
Shared Vehicle Record
Event
Integration
Status

Illustrative product data.

01
Every vehicle gets one file, and it stays open.
02
Three applications write into that file as they do their jobs.
03
Every department reads the same file instead of its own copy.

1 · The Shared Vehicle Record

One record per VIN, written by every application, owned by the dealership.

The VIN is the primary key. Each application reads the record before it acts and writes back what it learned, so the vehicle accumulates a history instead of restarting in each system it passes through.

Shared Vehicle Record field groups, what each holds, the application that writes it, and its current status.
Field group	What it holds	Written by	Status
Identity and equipment	VIN, decoded year/make/model/trim, drivetrain, assembly, open-recall check and factory equipment.	AutoLabels	Live
Pricing	Advertised price, itemized add-ons, and the check against the store's own site.	AutoLabels	Live
Disclosures and documents	What was included, chosen and declined, timestamped against the version shown, with the document set held per VIN.	AutoLabels	Live
Valuation and acquisition	Valuation inputs with their sources retained, plus channel, appraisal, offer terms, approval and check request.	AutoCurb	Live
Condition	Condition photos, reported condition and inspection findings where captured.	AutoCurb AutoFilm	Pilot
Evidence and service	Timestamped video indexed to the finding it shows, visit history, recommendations, and work approved or declined.	AutoFilm	Pilot
Customer decisions	What the customer accepted, declined or asked to defer — and when.	AutoFilm	Pilot
Ownership and activity	Current and prior ownership on the VIN, equity position over time, and the ordered event stream.	RooftopOS	In Development

2 · The application layer

Three applications, one record.

A store can start with any one of them, and the comparison that helps you choose lives on the applications page.

Each application, the department that owns it, what it reads from the Shared Vehicle Record, what it writes back, and its current product status.
Application	Reads from the record	Writes back to the record	Status
AutoCurbVehicle AcquisitionAcquisition	Prior ownership on the VIN, inspection history where it exists, and the store's own valuation inputs.	Channel, appraisal, valuation sources, offer terms, approval and the check request.	LiveAutoCurb
AutoLabelsVehicle Identity and MerchandisingMerchandising and compliance	Decoded identity, factory equipment, add-ons and the acquisition context already on the record.	Verified identity and equipment, itemized pricing, disclosures and the document set per VIN.	LiveAutoLabels
AutoFilmSales and Service VideoSales and service	Vehicle identity, open recommendations, and what a customer previously approved or declined.	Timestamped video indexed to the finding it shows, plus the decision on each recommendation.	PilotAutoFilm

Explore the Applications

3 · Structured events

The vehicle should never start over.

Every write lands on one record as a dated, attributed event, so the next department inherits the last one’s work instead of reconstructing it.

Four writes to the same VIN, in order

Media captured
Inspection evidence captured
Timestamped MPI. Front pads flagged at 3mm.
AutoFilm2026-03-04
Curb event completed
Offer accepted · check requested
Vehicle enters inventory. Acquisition recorded to the record.
AutoCurb2026-03-06
Label created
Window sticker and addendum generated
Advertised price verified against the live website before publish.
AutoLabels2026-03-07
Document added
Vehicle Passport published
QR on the glass. Equipment, disclosures, and history made shopper-facing.
AutoLabels2026-03-07

In DevelopmentEvery entry above is written to the same record today. Passing one application’s context to the next automatically — inspection evidence into an appraisal, acquisition context into merchandising — is the integration being built now.

4 · Access and data ownership

Everyone in the store sees the same record through a different scope.

Access, tenancy and ownership are the same question asked at three scales, and each is answered once here.

Role-based access
Access is resolved from the signed-in user's role and enforced at the database layer, not hidden in the interface.
Roles and scopes
Tenant controls
Each rooftop is a separate tenant, configured in its own branding, with its own users, templates and disclosure language.
How a group operates
Integrations
Listed by category rather than by vendor, each with the status of what actually connects today.
What connects
Audit & compliance
Disclosure and document history are retained per VIN against the version the customer saw, anchored to FTC Act Section 5 and state disclosure law.
Processing terms
Data ownership
The dealership owns its records. They are exportable on request, during an engagement and after it ends.
Trust Center

Representative role scopes — a store configures its own.

Owner / dealer principal: Full access across the rooftop, including configuration, users and billing.
Used-car director: Acquisition, appraisal, inventory and merchandising across the used-vehicle operation.
Sales manager: Appraisal approval, offer terms, pricing and deal-level disclosures.
Service advisor: Assigned repair orders, inspection evidence, and the approvals attached to them.
Accounting: Acquisition, document and export access. No customer messaging, no pricing changes.
Compliance administrator: Disclosure, consent and document history across the rooftop, read-only by default.
Group administratorIn Development: Configuration and consolidated reporting across more than one rooftop.

Dealer groups: a group is a set of rooftops, not a shared pool.

Group administration has not been exercised across more than one rooftop. RooftopOS has one founding design partner, and the relationship is set out on the customers page.

Tenant separationLive: Each rooftop is a separate tenant, enforced at the database layer.
Per-rooftop configurationLive: Products, disclosure language, templates and users are configured per store.
Role-based permissionsLive: Access is resolved from the signed-in user's role, per rooftop.
Store-level autonomyLive: A store's numbers and language belong to that store.
Group-level visibility, policy and reportingIn Development: Reading across a group from one session, publishing templates down to each store, and rolling reporting up with export.

RooftopOS provides workflow, documentation, and recordkeeping technology. It does not provide legal advice. Dealerships should review configurations and compliance requirements with qualified counsel.

5 · Existing systems

What RooftopOS connects to, by category.

Naming a DMS, CRM or valuation provider here would imply a certification or partnership, and RooftopOS claims neither. Each category carries the status of what connects today.

Inventory feedsLive: Inbound inventory ingestion with nightly sync and per-VIN re-check.
Dealer websiteLive: Dealer-branded surfaces on the store's own domain; Passport embeds on the VDP.
Valuation providersLive: Pluggable valuation layer — the dealership's own book runs alongside or instead of a third-party source.
SMS and emailLive: Customer messaging with versioned consent captured and retained per interaction.
Document storage and exportLive: Per-VIN document history, exportable on request.
Identity and user managementLive: Roles and permissions enforced at the database layer, not the interface.
Reporting and exportPilot: Operational reporting across applications, with CSV export.
DMSIn Development: Export and accounting handoff available today. Real-time write-back via webhooks is being built.
CRMIn Development: Structured hand-off of customer and vehicle events into the store's CRM.
Public API and webhooksPlanned: Documented API surface for dealer groups and technology partners.

6 · Current versus planned

Every platform capability, in one of four states.

Live

Operating in production.

Shared Vehicle Record, one per VIN
Keyed on the VIN, read and written in production by the applications a store enables.
Acquisition through check request
Off-street, service-lane and in-store acquisition as one workflow.
Verified identity, equipment and pricing
Decoded and itemized against the VIN, checked against the store's own site.
Disclosure and document history per VIN
Retained against the version the customer saw.
Dealer-branded customer surfaces
On the store's own domain and in its own brand.
Role-based access and tenant separation
Both resolved at the database layer, not filtered in the interface.

Pilot

Operating under a limited early-access agreement. Not generally available.

Sales and service video with timestamped evidence
No price is published while it is in pilot.
Cross-application reporting and export
Reporting that reads across applications, with CSV export.

In Development

Actively being built. Not available yet.

Automated handoffs between applications
Context moving onward without a person carrying it.
DMS and CRM connections
Export and accounting handoff work today; real-time write-back does not.
Group visibility, policy and consolidated reporting
Reading across the rooftops in a group from one signed-in session.
Ownership and equity over time
Prior ownership on the VIN, with an equity position between visits.

Planned

Approved roadmap. Not yet in development.

Public API and webhooks
Approved roadmap. Nothing can be built against it today.

See what one connected vehicle record changes across your dealership.

#demo-cta-_R_q4kq_{display:none !important}Request a Platform Demo

Or reach the team another way

One intelligence layer across the vehicle lifecycle.

One record per VIN, written by every application, owned by the dealership.

Three applications, one record.

The vehicle should never start over.

Four writes to the same VIN, in order

Everyone in the store sees the same record through a different scope.

Role-based access

Tenant controls

Integrations

Audit & compliance

Data ownership

Representative role scopes — a store configures its own.

Dealer groups: a group is a set of rooftops, not a shared pool.

What RooftopOS connects to, by category.

Every platform capability, in one of four states.

See what one connected vehicle record changes across your dealership.