Resources
Evaluation resources for product, security, and commercial review.
Nothing here is behind a form. Model your direct-acquisition economics using your store’s assumptions.
For the GM
Run the numbers, then run the evaluation.
What a general manager needs to make a decision in a thirty-minute meeting.
The direct-acquisition model
Enter your store's assumptions and see what the arithmetic says. The formula is shown next to every output, nothing is filled in for you, and each result is labelled modeled.
Open the model
How the 60-Day Proof of Value works
The measured baseline, the success metrics agreed in writing before go-live, the reviews at day thirty and day sixty, and the decision at the end. Entry criteria included, so you know before you apply whether your store qualifies.
Apply for a 60-Day Proof of Value
What is in the agreement
How term, exit, and data ownership are settled, and why the commercial specifics are written into the order form rather than published on a marketing page.
Read the terms
For compliance and legal
The agreements, as published.
The documents themselves, in full, with nothing behind a form.
Data Processing Agreement
The dealership is the controller and RooftopOS is the processor. Sub-processors, the notice period before one is added, breach notification and cross-border transfers are inside. Retention is not published there — the periods are set in the executed agreement.
Read the DPA
Privacy Policy
What is collected, how it is used, who else processes it, and the choices a dealership and a consumer each have. No retention schedule is published; the periods are set in the executed agreement.
Read the policy
Terms of Service
Acceptable use, data ownership, what the availability target is and is not, termination, and limits of liability.
Read the terms
Messaging consent walkthrough
How consent is captured against the version of the language a customer was shown and retained with the record, across all three applications. Walked through with your counsel during evaluation.
Available during evaluation
Accessibility statement
The conformance target RooftopOS builds to, how it is tested, and how to report a barrier.
Read the statement
For IT and security
Architecture and posture, published rather than gated.
Enough for a reviewer to form a view before a call, not after one.
Sub-processor list
Every vendor in the path, what it can see, where it processes, and a link to its own security documentation. Built by auditing the code rather than by restating a legal page.
See the list
Control status
Every control published with its current state in one closed vocabulary — Verified, Implemented, Partially Implemented, Planned — and the basis for each.
Read the matrix
Security architecture
Tenant isolation, encryption, access control, retention, and incident handling — including the controls inherited from providers rather than operated by RooftopOS.
Read the architecture
Data residency
Persistent storage is in United States regions. The edge network is global, and the difference is spelled out rather than glossed.
Read the detail
Live service health
A real request against the backend on every page load, with the live check, the operating target, and the measured history kept as three separate claims.
Check status
Product status and changelog
What shipped, when, and what each application's status actually means. The same source the sales conversation quotes.
Read the changelog
For press and analysts
Newsroom.
Fact sheet, boilerplate at two lengths, founder biography, and a direct contact.
Press kit
Company fact sheet, boilerplate written to be printed verbatim, founder biography, brand assets, and a direct media contact.
Open the press kit
Founder letter
Why an operator on the desk built software instead of buying it.
Read the letter
Operator briefs
Dated write-ups on the operational and regulatory questions dealerships actually ask, each one signed and each one stating what it is not.
Read the briefs
Available to qualified parties under NDA
Detailed security-control evidence, architecture specifics that would expose attack surface, implementation evidence, and commercial and financial detail are shared under a mutual NDA rather than published. That is a deliberate boundary, not an omission — everything above it is on this page in full.
Don’t see what your team needs?
Contact sales and it is routed to the product or operating lead who owns the answer.