For OEMs & large-fleet operators
Conduit at OEM scale.
Multi-tenant by design. Namespace-isolated. Audit-trailed. SSO, RBAC, deployment options scoped to your operation. Built for the procurement desk and the dealer network at the same time.
What enterprise gets
The capabilities your security and platform teams will ask for first.
Most of these aren't differentiators — they're table stakes for getting through enterprise procurement. They are present.
SSO and SAML
SAML 2.0 / OIDC against your identity provider. SCIM provisioning where supported. No separate Conduit credentials to manage.
Role-based access control
Roles for technician, service writer, dealer manager, OEM admin. Scoped by region, dealer, equipment family. Permissioned at the document level.
Audit logs
Every query, every answer, every citation, every correction is logged with user, timestamp, and source documents. Exportable.
Namespace isolation
Each tenant's documents, embeddings, conversations, and corrections live in a dedicated namespace. No shared retrieval, no cross-tenant learning, no shared model fine-tunes.
Custom standards integration
Your internal service standards, regional regulations, and brand-specific TSBs ingested alongside the OEM corpus and weighted in retrieval.
Flexible deployment
Managed by default. Isolated and customer-cloud options scoped per enterprise contract.
Data residency options
Storage and processing region scoped per contract for tenants with residency requirements.
Named technical account manager
A single point of contact for ingestion, eval review, corrections triage, and roadmap. Weekly syncs during pilot, monthly thereafter.
Compliance & validation
Every release is graded before it ships.
Conduit ships with a multi-dimensional eval framework that validates retrieval quality, citation correctness, and safety behavior on every release. The same framework is what we run against your corpus during pilot before any tech sees an answer.
Retrieval
The right chunk reached the model. Measured against a per-tenant golden set. Recall, precedence, ranking.
Citation
The cited page actually contains the claim. No fabricated sources, no fabricated page numbers, no fabricated specs.
Safety
Warnings, cautions, and notices from the manual surface alongside the procedure they apply to. Severity preserved.
Per-tenant eval results — your corpus, your queries — are part of every release report. You see what the framework measured, what passed, what failed, and what changed since last release.
Deployment & integration
How Conduit lands inside your operation.
Pick the one that matches your team's shape and your dealer network's existing software. The retrieval and eval layer is the same in all three.
Reference app
Our white-label technician chat surface, configured for your equipment, your branding, your roles. Fastest path from contract to a tech using it on the bay floor.
Best for: shipping a working surface to dealers without building one.
Widget & API
Embed Conduit's answer surface inside your existing dealer portal, service tools, or technician app. Authenticated API for query, retrieval, citation, and correction submission.
Best for: OEMs with existing dealer-facing software they want to keep.
Custom build
Co-development against your spec. Your team owns the surface, our team owns the retrieval and eval layer. Suited to large enterprises with internal product teams.
Best for: enterprises with a product team and a defined dealer-network surface.
Procurement-friendly
The questions your security and legal teams will ask.
Answered up front. Detail lives under NDA — these are the postures we hold to.
Data ownership
Your documentation stays yours. Your tenant's embeddings, conversations, and corrections stay yours. We hold a license to operate the service against them. You can export and walk at any time.
Training posture
We do not train, fine-tune, or improve any model on your data. Each tenant is isolated. There is no cross-tenant transfer, no shared model state, no shared retrieval index.
Model and provider transparency
Conduit uses purpose-selected language and embedding models with documented latency, cost, and quality characteristics. Provider choices, failover behavior, and bake-off methodology are disclosed under NDA. Models can be swapped without re-ingestion.
Tenancy model
Logical multi-tenancy by default with namespace isolation at the storage and retrieval layer. Single-tenant and customer-cloud deployments scoped per enterprise contract.
Security posture
TLS in transit, encryption at rest, scoped credentials per tenant, principle-of-least-privilege for service accounts. SOC 2 process is in motion — stage and timeline disclosed under NDA.
Service level
Enterprise SLAs — uptime targets, response times, dedicated capacity, residency — negotiated against the contract. We don't publish a one-size-fits-all number; the right answer depends on your tier and your operation.
IP ownership
Your documentation, your tenant's configurations, your tenant's corrections — yours. The Conduit platform, retrieval pipeline, eval framework, and prompt engineering — ours. Licensed, not transferred.
SOC 2, full security questionnaire, model and provider list, and architecture diagrams are available under NDA. Ask and we'll send the package.
Get started
Talk to us about an enterprise deployment.
First conversation: 30 minutes. Your equipment, your dealer network, your security posture, your timeline. We'll tell you what's realistic and what isn't before you spend an hour on a security questionnaire.