Nebula XDP Everything Data Platform

Every system. Every location.
One auditable feed.

Nebula XDP connects every system a location runs, DMS, CRM, website, service, marketing and inventory, and delivers one normalized, auditable feed per store. Whether you run the stores, market them or build on their data, you get clean data without building the pipelines.

For agencies, franchise groups, OEMs and data teams.

8 in 1
Data types, one feed
Daily
DMS sync for every store
5
Governed objects behind every answer
Who it is for

Clean data, ready to use, whoever you are in the chain.

Agencies

Baseline every client store, prove ROI against DMS sales, and sell the data layer under your own brand at your own price. No Snowflake or data warehouse to buy.

Franchise groups

One normalized view of every location, rolled up by group and region, with store level security.

OEMs

Store level sales, lead and service data across your network, reported by region or district.

Data and technology companies

Skip building DMS and CRM integrations. Build on one normalized, auditable feed and get certified where buyers shop.

The problem

Four ways data from many locations fails quietly.

None of these show up as an outage. They show up as a benchmark nobody trusts, a text that should not have gone out, and a unit advertised after it sold.

01

Schema variance

Every DMS and CRM names and shapes the same fact its own way, so benchmarks across stores break before they start.

02

Consent leakage

An opt out captured at one location never reaches the others. That is TCPA and email law exposure, multiplied by every store.

03

Inventory fiction

Units that are sold, on hold or not yet funded keep showing as available, and ads and price tags drift from the truth.

04

Analytics without authority

Dashboards describe the problem, but nothing is allowed to act on it, and nobody can say why a number moved.

The question it answers

What is actually happening at each store, on each unit, with each rep?

One audited book

Five objects. One version of the truth.

Whatever the source system calls it, every record lands in one of five governed objects. Every report, every message and every price change reads from the same book.

Object 01

Customer

One identity resolved record per person, across every system and every location.

Object 02

Unit

Every unit with its true state: in stock, on hold, funded or sold.

Object 03

Consent

Opt in and opt out held on the customer, across every channel, synced to every location.

Object 04

Price

Advertised price, fees and the history of every change.

Object 05

Event

Every sale, lead, visit, message and repair order, in order, with its source.

The lineage rule

If an agent cannot explain, in lineage terms, why it sent a text or changed a price, it is not allowed to act.

How it works Connect, normalize, act

From every login to one feed you can defend.

Connect

Every system a location already runs

Live connectors across DMS, CRM, website, service, marketing and inventory, plus aKillion products and a growing partner network. Pick the feeds each store needs. Nothing is bundled.

  • DMS synced daily for every store
  • CRM synced at least weekly, faster on request
  • Website identity pixel ingested in real time
  • Failed pulls retried, and every failure attributed to the location it belongs to
Normalize

One format, whatever the source

Each DMS and CRM names and shapes the same fact differently. Nebula XDP maps every feed to one consistent, identity resolved schema, so a store in one system compares cleanly to a store in another.

  • Schema variance resolved
  • Identity resolved across systems
  • Bad records held in a dead letter queue, never silently dropped
  • Every record traceable to its source
Act

Answers first, then governed action

Baseline a store on day one and prove what changed after, on the same normalized data both times. When you are ready, approved changes flow back into the systems your stores already use.

  • Baselines, scorecards and portfolio benchmarks
  • Before and after ROI tied to DMS sales
  • Approved changes written back to the system of record
  • A human approval gate on anything that touches price or outreach
The same fact from three sources
DMS A DealDate03/14/2026
DMS B contract_dt20260314
DMS C SaleDate14 Mar 2026
sold_date2026/03/14

One schema, and every record traceable back to the source it came from.

A platform, not another tool

How this differs from buying one more SaaS login.

Typical SaaS
Nebula XDP
Pipeline
Nightly or hourly batch sync.
Continuous parsing, with retries and dead letter handling.
Inventory
Feed in, feed out.
A state machine: holds, funding, location and a price built for price transparency rules, with changes written back.
Audit
Application logs.
Lineage on every ingest and every change written back, plus a history for every question asked.
Workflow
Another portal to log in to.
Runs underneath the tools your stores already use.
Identity
A CRM scoped to one location.
One customer and one unit object for the whole group. A new location is a client, not a rebuild.
Compliance
Opt out lives inside one messaging tool.
Full opt in and opt out management on the customer, across every channel, synced to every tool that could reach them.
AI
Read only insights on a silo.
Named AI employees that can write changes back, behind human gates.
Pricing
Stitch market files by hand and edit units one at a time.
Market data and the unit book in one workbook, a human approval, and a guarded change written back nightly.
What your team gets

Built for organizations that run on many locations.

One normalized feed

DMS, CRM, pixel and service data mapped to one consistent format across every store you manage.

Store and rep level data

Deal, lead and activity data from the DMS and CRM at the store and salesperson level, ready for your scorecards.

Before and after proof

Baseline a store at kickoff and measure against the same normalized data after. A like for like read for every program and campaign.

Runs under the tools you have

No new portal for store staff to learn. Nebula XDP works underneath the DMS, CRM and website each location already runs.

A new location is not a rebuild

Add a store, a brand or an acquisition as one more client on the same object model. Its first day looks like every other store.

Use it, or sell it as your own

Run it across your own stores, or private label it inside what you sell. A flat platform fee plus per store feeds at one published margin.

No Snowflake. No data warehouse. No storage bill.

Storage, normalization and a dedicated data environment for every store come with Nebula XDP. Agency partners get warehouse grade data without buying, configuring or paying for Snowflake, BigQuery or any other data storage provider.

Mix feeds by store

Take the DMS, the CRM, or both. Store by store.

Neither core feed is required. Connect a DMS feed alone where that is all you need, a CRM feed alone somewhere else, or both at the stores that matter most, and pay only for what is live at each one. Add the second feed later, and billing starts when it activates.

Store 01
Store 02
Store 03
Store 04
Store 05
Store 06
2DMS only2CRM only2Both feeds

Try it. Toggle feeds per store. Every store keeps at least one live feed, which is what makes it an active store. Website pixel and service layers add on in any combination.

Integrations

Connects with the systems your stores already run.

20+ connections and growing: live data feeds, aKillion products and a partner network. Pick what each store needs.

DMS
DealerVaultCDKLightspeedTekion
CRM
VinSolutionsDriveCentricCDK eLeadsProMaxTekionKastor, by aKillion
Website
Smart PiXLRigel, by aKillion
Service
XtimeDealerFX
Marketing and calls
Google AnalyticsGoogle AdsCallRevu
Inventory
Stockwave
Partner network
Automotive consumer dataFirst party audience dataAutomotive insights and analyticsPowersports appraisal and inventoryLocal media and advertisingStore team engagement

Get certified where buyers already shop

Build on Nebula XDP and take your solution through certification on public marketplaces, including CDK Fortellis, DealerVault and DriveCentric, so buyers can find, approve and connect it in the places they already buy.

Availability at any given store depends on that store's own contract with the provider. Certification is granted by each marketplace under its own program. Provider and marketplace names are used for identification only and belong to their respective owners.

Security model

Every query logged. Every store sealed.

Security is enforced where the data lives, at the storefront, not only at the front door.

  • MFA per storefront. Multifactor authentication is enforced on each storefront, not just the account login.
  • Tamper evident audit log. Every query and every download against store data is logged and cannot be quietly edited.
  • One feed, one store. Each feed is bound to one store. Data is never pooled or cross queried between stores, groups or clients.
  • Dedicated environment. A secure, dedicated data environment is provisioned and maintained for every store.
Query and download logRecording
09:14:02QUERYStore 07rep_scorecardMFA OK
09:14:19DOWNLOADStore 03sold_units_q3.csvMFA OK
09:15:40SYNCStore 12dms.dailyOK
09:16:05QUERYStore 07lead_activityMFA OK
09:16:58RETRYStore 21crm.weeklyOK
09:17:31QUERYStore 03baseline_kickoffMFA OK
Illustrative. Tamper evident log of every query and download against store data.
Role based accessPeople see the stores and the data their role allows.
Production kept apartLive data runs separately from the sandbox.
EncryptedAt rest and in motion.
Everything loggedLogins, writes and admin actions.
Daily backupsHeld in a separate region.
Reporting and audit

Full reporting, from one location to the whole portfolio.

Assign stores to groups and regions, and every report rolls up the way you run the business. Every query and download behind those reports is logged.

STORE

One location, down to the rep

Deals, leads, activity and service for a single store, with every figure traceable to its source record.

STORE GROUP

Stores you group together

Assign stores to a group, such as a franchise group, a brand or an agency client roster, and report on them as one unit.

REGION

Regional rollups

Assign stores and groups to regions or OEM districts. Regional reports roll up automatically as the assignment changes.

PORTFOLIO

Everything you manage

Every connected store side by side, with rollup metrics validated before go live.

What runs on the book

Turn the feed into revenue, not just reports.

The same governed data behind your reporting runs the work: marketing, inventory, pricing and conversations with customers. AI employees do the work, and a person approves anything that matters.

One preference graph, every location.

Every message starts from one customer record and one consent record. Opt in and opt out are managed in full at the customer level, for every customer and every channel, so a choice made at one location is honored at all of them.

  • Omnichannel outreach from one customer record
  • Full opt in and opt out management at the customer level
  • Every customer and every channel covered, synced to every location
  • Location voice inside group rules, with adaptive cadences
  • Verified recipients and email hygiene before anything sends
Reads fromCustomerConsentEvent
Illustrative conversation
AI employeeHi Dana, your lease on the SUV ends in about 90 days. Want to see what an upgrade could look like with your current equity?
CustomerMaybe. What would payments look like?
AI employeeI can have options ready for you. Does Saturday at 10 or 2 work for a quick visit?
Customer2 works.

Inventory as a state machine, not a spreadsheet.

A unit only reaches a website or an ad when its state says it can. Holds, funding and price rules are checked before anything publishes, so what should not be live stays off the site.

  • Sold, held and unfunded units are never advertised as available
  • Advertised price built with price transparency rules in mind
  • Fees, hold state and advertised price written back to the system of record
Reads fromUnitPriceEvent
How it runs
1
Raw feedUnits arrive from every source
2
Hold logicDeposits and holds applied
3
Funding checkUnfunded deals stay accurate
4
Schema normalizationOne unit object for the group
5
Approved publicationOnly then does it go live

Pricing that recommends, then waits.

Market data and your own unit book meet in one regional workbook. A person approves. Only then does a guarded change write back, with its history kept on the unit.

  • One field changes, inside a capped band
  • No duplicate replays of the same change
  • Written back nightly, with change history on the unit
Reads fromUnitPrice
How it runs
1
Market file and unit bookCombined automatically
2
One regional workbookRecommendations per unit
3
Human approverNothing moves without a yes
4
ValidationOne field, capped band, no replays
5
Nightly updateWritten back, with history on the unit

Instant speed to lead, around the clock.

New leads get a reply in seconds on text, chat or email. AI employees qualify on timing, budget and trade, then book the appointment and hand a complete record to your team.

  • Inbound reply, qualification and booking, around the clock
  • Missed call rescue so no lead goes cold
  • Rigel website intent handed into a live conversation while the visitor is still engaged
Reads fromCustomerUnitEvent
Illustrative conversation
CustomerIs the white pickup on your site still available?
AI employeeIt is. Are you thinking about financing, leasing or paying cash? And do you have a trade?
CustomerFinancing, and I have a 2019 sedan to trade.
AI employeeGreat. I can hold it for a test drive today at 5:30 and have a trade estimate ready. Want me to book it?

Keep the service lane full.

Recall notices, maintenance due and declined work become conversations that book appointments, using repair order history from the service feed.

  • Recall and maintenance due outreach
  • Declined work follow up with booking built in
  • Reactivation of customers who have not been back
Reads fromCustomerConsentEvent
Illustrative conversation
AI employeeHi Marcus, there's an open recall on your truck and it's due for its 30k service. Want to take care of both in one visit?
CustomerSure, how long does it take?
AI employeeAbout 2 hours. Tuesday at 9 or Wednesday at 1 are open, and a loaner is available.
CustomerTuesday at 9.

Intelligence that recommends, then waits for you.

Analytics and ad data are tied to inventory and CRM, so a manager can ask a question in plain language, set a metric goal and get an alert when it drifts. Recommendations wait for a person before anything changes.

  • Answers from the same normalized data behind your reports
  • Metric goals and proactive alerts
  • Follow ups and task management for the team
Reads fromAll five objects
Illustrative conversation
ManagerHow did the East region close last week against goal?
AI employeeEast delivered 212 units against a goal of 230. Two stores were behind on lead response time. Want the rep level breakdown?
ManagerYes, send it.
AI employeeSent to your inbox. I also flagged 38 open leads older than 24 hours.
One conversation, every channel
TextWeb chatEmailVoiceRich media, patent pending DMMS

AI employees are scoped and priced separately from Nebula XDP. Every message checks the consent record held on the customer before it sends, on every channel.

From kickoff to live

Four steps. You bring access. We handle the pipes.

01

Kickoff and access

Your dashboard is created. You share access for the feeds each store is connecting within 5 business days.

02

Core mapping

We configure each store's chosen connections from the certified connector inventory.

03

Security hardening

Multifactor authentication is enforced for every storefront.

04

Validate and go live

Sync is validated across your stores and rollup metrics are confirmed before launch.

Transparent pricing

One monthly subscription. No hidden spread.

Platform fee

One flat fee

For your whole portfolio, set by active store count. Billed once per account, not per store.

+
Per store data feeds

Rate card plus one margin

Only for the feeds each store actually runs. One fixed margin, printed beside every rate.

=
Your monthly subscription

One predictable bill

The platform fee plus the feeds that are live. Selling it as your own? You set your retail price on top.

Tier 1

1 to 24 active stores

Single groups and agencies getting started

$1,995per month, whole portfolio
Get the rate card

Tier 2

25 to 82 active stores

Growing portfolios and regional groups

$3,495per month, whole portfolio
Get the rate card

Tier 3

83+ active stores

Large groups, OEM programs and national agencies

$4,995per month, whole portfolio
Get the rate card
Every tier includes
Partner dashboardPipeline architecture and QAData normalizationDedicated environment per storeMFA per storefrontPortfolio rollupsQuery and download audit logData storage included
One margin on every feed. Published.

Every data feed is priced at its rate card plus one fixed margin, and both numbers are printed side by side. No hidden spread on the systems your stores already pay for. The same margin applies to every provider and every tier.

A store counts as active once it has at least one live feed. Your tier is reviewed against your active store count and adjusts as your portfolio crosses a boundary. Nebula XDP covers software and data connectivity only. aKillion AI employees and campaign services are scoped and priced separately.

One family

Nebula is the data spine.
What you build on it is up to you.

FAQ

What buyers ask first.

No. Neither core feed is required. A store can run a DMS feed only, a CRM feed only, or both, chosen store by store. You can add the second feed later and billing for it starts when it activates.

A store is active once it has at least one live feed: a DMS feed, a CRM feed, or both. Your tier is set by the total number of active stores across your portfolio and adjusts as you cross a tier boundary.

DMS feeds sync daily. CRM feeds sync at least weekly, and faster sync is available case by case. Website pixel data is ingested in real time.

In full, at the customer level. Every customer has one consent record that covers every channel: text, email, web chat, voice and rich media. An opt in or opt out captured at any location, or in any connected tool, updates that record, and every location and every AI employee checks it before anything sends.

No. Each feed is bound to one store and every store gets its own dedicated data environment. Data is never pooled or cross queried between stores, groups or clients, MFA is enforced per storefront, and every query and download is logged.

Yes. Assign stores to groups and regions, and reporting rolls up at store, group, region and portfolio level. Every query and download behind those reports is logged in a tamper evident audit trail.

Yes. Solutions built on Nebula XDP can pursue certification on public marketplaces such as CDK Fortellis, DealerVault, DriveCentric and more. Talk to your aKillion contact about the path for each marketplace.

aKillion is responsible to you for pipeline architecture, data normalization and quality assurance across every integrated feed. Failed pulls are retried, failures are attributed to the location they belong to, and every record is traceable to its source.

Both. Reporting reads. Where you turn it on, approved changes such as fees, hold state and advertised price are written back to the system of record. Anything that touches price or outreach waits for a human approval, and every change carries its lineage.

No. Nebula XDP runs underneath the tools each store already uses. Store staff keep working in their DMS and CRM.

Yes. Like every aKillion product, Nebula XDP can be private labeled. You set your own retail price on top of the platform fee and the per store feeds.

A primary point of contact, credentials and system access for each store's feeds (DMS access within 5 business days of that store's kickoff), and UAT approvals within 5 business days of notification.

Something else? Email sales@akillion.us.

Let's build

See every location in one feed.

Book a walkthrough. Bring your store list and the systems each store runs, and we will show you the feed, the rollups and exactly what it costs.

We don't build AI tools. We build AI companies.

Copyright © 2026 All Rights Reserved by aKillion

Experience a Fully Unified AI Operation

Copyright © 2026 All Rights Reserved by aKillion