By business
By size
By platform
Find your fit
Tell us what you run and how big it is, and we will show you the platform, the products and the pricing tier that match.
→ Who We ServeThe ecosystem triangle
AF-X is the only platform family present on all three sides.
→ See the triangleData X
One clean record of every vehicle, customer, part and site — held in the region you chose.Intelligence X
The numbers the business runs on, live, with the same definition on every site.AI X
AI inside the product at the point the decision is made — rank, predict, price, draft, answer.Your data. Your workflow. Automotive AI that does the job, not the demo.
→ How AF-X uses your data→ What AI native meansWhere do you want to start?
The claim
The only automotive platform family that runs dealer retail, independent workshops, fleet & mobility, parts distribution and remarketing — on one platform, with one data model.
Keep the system you run the business on. AF-X connects to it, reads from it, writes back to it, and adds the layer that was missing. Nobody has to migrate to get started.
Products never talk to your systems directly. They call the AF-X Integration Layer, which handles authentication, mapping, retries and audit. Swap a DMS or a payment provider and the products above it do not change.
Explore the system categories AF-X commonly connects with and the typical data exchanged.
Connect customer, vehicle, sales and workshop information with AF-X workflows.
Exact data scope, direction and write-back capability depend on the connected system, market and agreed implementation.
Discuss your integration →Connect workshop planning and job information with AF-X workflows.
Exact data scope, direction and write-back capability depend on the connected system, market and agreed implementation.
Discuss your integration →Connect vehicle, contract and driver information with fleet workflows.
Exact data scope, direction and write-back capability depend on the connected system, market and agreed implementation.
Discuss your integration →Connect commercial and financial information with relevant AF-X workflows.
Exact data scope, direction and write-back capability depend on the connected system, market and agreed implementation.
Discuss your integration →Connect customer and engagement information across AF-X workflows.
Exact data scope, direction and write-back capability depend on the connected system, market and agreed implementation.
Discuss your integration →Connect catalogue and availability information with parts workflows.
Exact data scope, direction and write-back capability depend on the connected system, market and agreed implementation.
Discuss your integration →Connect payment activity with customer and commercial workflows.
Exact data scope, direction and write-back capability depend on the connected system, market and agreed implementation.
Discuss your integration →Connect document and signature information with the relevant customer journey.
Exact data scope, direction and write-back capability depend on the connected system, market and agreed implementation.
Discuss your integration →Connect trusted vehicle information with sales, service and fleet workflows.
Exact data scope, direction and write-back capability depend on the connected system, market and agreed implementation.
Discuss your integration →Connect selected connected-vehicle information with fleet and service workflows.
Exact data scope, direction and write-back capability depend on the connected system, market and agreed implementation.
Discuss your integration →Connect manufacturer and network information with relevant operational workflows.
Exact data scope, direction and write-back capability depend on the connected system, market and agreed implementation.
Discuss your integration →Connect market-specific services required by local operating processes.
Exact data scope, direction and write-back capability depend on the connected system, market and agreed implementation.
Discuss your integration →Examples of systems and providers AF-X can connect with. Availability depends on product, market and agreed implementation scope.
A named AF-X integration lead owns the work end to end. Your team’s involvement concentrates in discovery and verification. Timing depends on the system and the data scope, and is agreed at the end of discovery.
We map your systems, data owners, volumes and the workflows each platform needs. Nothing is assumed from a logo.
Connectors are configured or built against your sandbox. Field mappings and error handling are agreed with your team.
One site, live data, read-first. Write-back stays disabled until the pilot behaves as designed.
Your team and ours reconcile records, test failure and retry paths, and confirm security and access scopes before anything scales.
Roll out across locations with monitoring, alerting and a hypercare window owned by your integration lead.
Published after technical validation.
Test against realistic data before production.
Every event AF-X emits, with payload schemas.
One accountable owner from discovery to hypercare.
Integration is where most risk lives. These are the controls that apply to every connection, regardless of platform or provider.
Security & trust →Every connection uses the narrowest data scope agreed in discovery. Scopes are reviewed at renewal.
TLS 1.2+ for every call; encrypted storage for any cached or queued data.
Every read and write is logged with actor, time and payload reference, exportable to your SIEM.
SSO via SAML or OIDC, SCIM provisioning and role-based access mapped to your directory groups.
Data residency is agreed and documented before go-live, not discovered afterwards.
Data-processing agreement, retention schedules and subject-request tooling across every integration.
Events are signed, idempotent and replayable so your systems never miss or double-process a change.
Failed syncs surface in the product and to your team; nothing fails silently.
100% cloud · AI native · outcome and performance driven
Practical answers about your existing systems, delivery time, security and who looks after the connection.
No. AF-X connects with the systems you already run, adding new products and workflows without requiring a core-system replacement.
AF-X can connect with automotive platforms, enterprise systems, data providers and specialist tools through available APIs, webhooks, file exchanges and agreed custom connections.
We assess the available connection methods and recommend the safest practical approach. This may include scheduled file exchange, middleware or a controlled custom connector.
Timing depends on API readiness, data quality, security requirements and the number of workflows involved. A focused connection may take a few weeks; broader integrations are planned and delivered in phases.
Access is limited to the data required for the agreed workflow. Authentication, permissions, encryption, logging and data handling are defined during the integration assessment.
Responsibilities are agreed before delivery. AF-X can build and support the connector directly or work with your internal team, system provider or implementation partner.
AF-X monitors supported connections through its ongoing Run service. If another provider changes an API or data structure, we assess the impact and coordinate the required update.
Yes. AF-X can begin with the connection required for the first product or workflow, then add systems and data flows as the rollout expands.
Book a demo for the whole estate, or start with one product on the system you already have.
ONE CONNECTIONEVERY PRODUCTYOUR PACE
