Olympus for service-department-scale operations.
OlympusPer-tech audit. Tenant isolation. Network-wide deployment. Custom-trained models on your OEM's proprietary technician corpus. Built for dealer networks that diagnose hundreds of vehicles a week · and need to prove it. Available as Dealer Group ($100/seat + $90/M overage) or OEM Custom for manufacturer-scale rollouts.
Trusted by dealership service departments
Diagnostic intelligence at the bay.
Olympus reads live vehicle data, cites OEM evidence, remembers every vehicle, and learns from every diagnostic. Built for the way real technicians work · not how SaaS dashboards think they work.
Live OEM integration
Module inventory, self-tests, freeze frames, and PIDs flow through the OEM protocol bridge · every read structured, typed, and tier-classified per the read-surface safety case. No screen scraping, no GUI brittleness.
Cited Ford evidence
Every diagnosis pinned to OEM Workshop Manual procedures and Technical Service Bulletins. Olympus says exactly which TSB applies and which WSM section to torque to. When the WSM doesn't have it, Olympus says so. No fabrication.
Persistent vehicle memory
Olympus remembers the vehicle across the bay. Last week's freeze frame, last month's recurring symptom, last quarter's TSB hits · every diagnostic builds on the prior session for that VIN. No re-litigating context.
Argus telemetry
Every CLI command, chat transcript, diagnostic adapter call, and error fingerprint streams to a structured event store. `olympus admin telemetry replay` plays back any technician's session. The product gets smarter on every diagnostic.
McGraw Ford · 90 seconds to first diagnostic.
Two technician benches. Two real vehicles · a 2021 Escape and a 2026 F-Super Duty. One PowerShell command on a fresh Windows VM, and 90 seconds later the technicians were running real live diagnostics on real vehicles with real DTCs.
Two technician benches, two real vehicles, the full install path through diagnostic bridge deploy to first diagnostic with real DTCs in 90 seconds. Dealer rollout playbook validated; the install harness gates every future dealer.
Service-department-scale features.
Olympus runs at the bay, not the desk. Per-tech audit, multi-rooftop admin, white-label install, and tenant-private fine-tuning · built for dealerships that diagnose hundreds of vehicles a week.
Per-tech audit log
Every diagnosis, every cited source, every parts-and-labor decision logged per technician with 7-year retention. Service managers see who diagnosed what, when, and with what evidence · exportable per-rooftop for compliance reviews.
Multi-rooftop console
Central admin across all your dealership locations. Tech provisioning, license allocation, usage analytics, and support requests in one pane of glass. Per-rooftop spend caps, per-rooftop tier rules, single-pane oversight.
White-label install
Branded installer banner, custom shim names, and dealership-specific install URLs. Your technicians see your brand from first-launch through every diagnostic. Optional dealer-internal CDN for the install bundle.
Custom model fine-tuning
Olympus learns your dealership's repair patterns. Recurring symptom-to-fix maps, your shop's torque preferences, your senior tech's diagnostic style · baked into a tenant-private model. Your data trains your model. Period.
Your repair data, your boundary.
SSO from your IDP, VPC-isolated model inference, and dealership-specific SLAs. Repair data stays on your tenant · never used to train foundation models.
SSO + SAML
Single sign-on via Okta, Azure AD, Google Workspace, or any SAML 2.0 provider. SCIM provisioning so onboarding/offboarding flows from your IDP into Olympus automatically.
VPC-isolated inference
Olympus deployed inside your AWS account via PrivateLink. Model inference runs inside your cloud boundary without traffic leaving your VPC. Your repair data never crosses the public internet.
Custom SLA + retention
Dealer-network-specific SLA terms, audit-log retention windows, and deletion policies. Compliance commitments (BAA for healthcare-adjacent fleets, custom data-handling for government contracts) negotiated per OEM Custom contract.
Running one OEM or scaling to many?
Olympus deploys inside your cloud boundary via PrivateLink for full VPC isolation. Multi-OEM expansion (GM Tech2, Toyota TIS, Honda HDS) is roadmap-bound · OEM Custom customers co-design the OEM expansion sequence with the Olympus team.
Common Dealer Group + OEM Custom questions, answered.
- How does pricing scale with technician count?
- Dealership is monthly per-seat for single shops up to 24 technicians. Dealer Group is annual per-seat (25-seat minimum) with tenant isolation and audit export · for multi-rooftop operators. OEM Custom is volume-negotiated contract pricing at manufacturer scale · pricing depends on dealer-network seats, fine-tuning scope, and deployment topology. Contact sales for a quote tailored to your operation.
- Can I integrate with my dealership's existing systems?
- OEM Custom includes SSO + SAML (any SAML 2.0 IDP) and dedicated forward-deployed engineering for DMS / RO ticketing integrations. Dealer Group includes per-tech audit log + CSV export and API access for usage reporting. Dealership tier integrations are roadmap-bound.
- What happens to my dealership's repair data?
- Stays on your Olympus tenant. Dealer Group adds tenant isolation (separate inference credentials, separate audit boundary). Repair data is never used to train foundation models. OEM Custom is the explicit opt-in path for fine-tuning a tenant-private model · trained on your OEM's proprietary technician corpus, exclusive to your dealer network.
- What are the deployment options?
- Standard SaaS by default · your dealership accesses Olympus over the public internet with TLS 1.3 in transit and AES-256 at rest. OEM Custom adds VPC-isolated model inference via AWS PrivateLink so model traffic never leaves your VPC. On-prem deployment is roadmap-bound; contact sales if it's a hard requirement.
- What's the deployment time?
- Dealership: same-day self-serve onboarding. Dealer Group: 1-2 weeks for tenant setup. OEM Custom: 1-3 weeks for first dealership rollout, network-wide phased over 3-9 months depending on franchise count. Forward-deployed engineering team leads the OEM Custom timeline end-to-end.
- What about brands beyond Ford?
- Ford is supported today. Multi-OEM expansion (GM Tech2, Toyota TIS, Honda HDS) is roadmap-bound. OEM Custom customers can co-design the OEM expansion roadmap with the Olympus team.
Transform how your dealership diagnoses.
Dealer Group at $100/seat + $90/M overage · annual contract · 25-seat minimum · ready in 1-2 weeks. OEM Custom for manufacturer-scale rollouts · network-wide deployment, OEM-branded installer, tenant-private fine-tuning, VPC-isolated inference, dedicated forward-deployed engineering team.