Gladius unifies CRM + BDC + Detail + Service messaging into one mesh — built for franchise dealers and OEM programs.
Why OEMs should care
01
FTC Safeguards, GLBA, and the patchwork of state data laws (CCPA / CPA / VCDPA / CTDPA) are getting harder every quarter. Gladius ships defense in every release through AWAIS — our Autonomous Web Application Intelligence System. PII column encryption, tenant-isolation auditor, schema-drift scanner, public incident feed. The compliance posture you want your franchise dealers to have is the codebase, not a Word document attached to an MSA.
02
Eight to twelve vendor relationships per rooftop is normal. CRM, BDC, chat, AI follow-up, digital retail, service scheduler, reputation, video, payments, DMS integration, lead aggregator, detail vendor. Each one has its own contract, its own invoice, its own permission model, its own outage page. One vendor replacing eight cuts dealer admin and contract management by 70–80% — and gives your program one throat to choke instead of twelve.
03
When one franchise dealer sees a new attack pattern, every other rooftop on Gladius — across all five verticals — hardens in under 30 seconds. The public log lives at /awais/incidents. No incumbent CRM publishes anything like it because none of them have anything like it.
04
We accept ADF/XML inbound at /api/webhooks/adf — the standard OEM lead-provider format — with HMAC-SHA256 signing per dealer. Standard webhook events go outbound. Both protocols are documented at /api-docs with real curl examples. We’re ready to integrate the day a program approves us.
Certifications + integrations we’re pursuing
We don’t claim certifications we don’t hold. The list below is exactly where we are today — what we already support live, and what we’re actively applying for.
Ford & Lincoln franchise network — preferred-vendor catalog.
Chevrolet / Buick / GMC / Cadillac digital lead program.
Toyota Service Provider catalog — CRM + dealer-tech vendors.
Jeep / Ram / Chrysler / Dodge BDC + lead-program vendor list.
Already supporting today
Standard OEM-lead-provider format. Live at /api/webhooks/adf, HMAC-SHA256 signed per dealer. Accepted from any source.
Standard webhook delivery for partner integrations. Documented at /api-docs.
What we ask of OEM partners
Ask 01
We sign 90-day pilots with explicit success metrics agreed up front. Your program team observes outcomes directly — speed-to-lead, appointment-set rate, show rate, gross retention, dealer NPS. No black box.
Ask 02
Our public roadmap lives at /roadmap. Where it aligns with your program’s 2026–2027 priorities, we’d ask for a sponsored review path so we can integrate to spec rather than reverse-engineer from a PDF.
Ask 03
After pilot results are in: jointly published case studies, an OEM-branded co-pilot brief, dealer-meeting co-presentations. We don’t market with partners before the receipts exist. We market with partners because the receipts exist.
Why us vs the incumbents
Every claim below is consistent with what your dealers can already read on /compare and /owners.
vs CDK / Reynolds
vs VinSolutions / Elead
vs newer entrants
The receipts
Six public surfaces an OEM program review team can audit today without an NDA.
/awais/meshOpen →Live cross-vertical defense mesh visualization.
/awais/incidentsOpen →24h anonymized attack feed. Refreshed hourly.
/compareOpen →Honest comparison against VinSolutions, Elead, DealerSocket, DriveCentric.
/securityOpen →FTC Safeguards posture, breach SLA, encryption-at-rest spec.
/api-docsOpen →ADF webhook, lead ingest, status aggregate, SVG badges — with curl examples.
/case-studiesOpen →Named rooftops. Outcomes we’ll publish on demand.
Direct contact for OEM partners
Program reviews live or die on response time. Every contact below routes to the founder, not a BDR queue.
Full work history, the floor years, and what Gladius is being built to replace.
Gladius Technologies LLC · Tampa, FL · 2026