Know what data you have,
where it came from, and what it means
Most dealer groups have terabytes of data they can't use because they don't know what's in it. Orbee's data catalog documents every column, every table, every source — with AI-generated metadata, field provenance, and a searchable dictionary your analysts, marketers, and AI agents all rely on.
Real data, no longer locked behind missing documentation
Every column, table, and source ingested into the platform shows up here — described, classified, and connected to the rest of the model.
Every native object and every ingested table.
Customers, Vehicles, Service Orders, Inventory, Web Events — documented field-by-field. Raw vendor tables keep their original schema alongside the mapping to Orbee's model.
- Type, source, and population rules
- Original vendor schema preserved
- CDK, Reynolds, VinSolutions & more
Field provenance and cross-source joins.
Every column carries a documented source — which vendor system, which table, which API endpoint, on what schedule. Every documented join path is searchable.
- Trace a wrong value to its origin
- Documented join paths between tables
- Calculated fields with visible formulas
Description candidates where vendors provide none.
Where source vendors don't document their columns, Orbee's AI tooling generates description candidates — reviewed by our team and validated against actual data.
- Reviewed and validated metadata
- Structured field descriptions
- Made available to your whole team
A catalog that can't fall out of sync
because it's generated from the live schema service.
The data catalog sits on top of Lattice, Orbee's database service — the same schema service that's running your audiences and reports.
Definitions & metadata
Lattice manages native object definitions, property definitions, source schemas, and the metadata layer behind the catalog.
Background schema changes
Adding, altering, or deleting columns flows through Lattice's automated background processes — no manual SQL modifications.
Never stale
Catalogs disconnected from the data infrastructure fall out of sync. This one is generated from the schema service itself.
Stop hunting for data you already have
The catalog isn't a documentation site. It's the substrate that makes Studio, AI tooling, schema evolution, and compliance reporting actually work.
Search by column or concept
Find email_address across every table — or every column related to "finance" or "lease maturity" across every source.
Drill into a record
Open any customer profile in Explorer and click any field to see what populates it, from where, on what schedule.
ProvenanceTrace a join path
Ask the catalog how to get from one table to another and see the documented path the Pathfinder engine will follow at query time.
PathfinderDocument your own work
Add notes, tags, and team conventions to columns and tables. Build organizational knowledge inside the platform, not a separate wiki.
Team knowledge
Somewhere in the CDK customer table is the column
your marketing team has asked for for years.
Nobody knows it exists. Nobody knows what its values mean. Multiply that by the 200+ tables across DMS, CRM, web, call, ad, and offline sources and you get the dealer industry's quiet productivity tax. The data catalog is Orbee's answer.
Turn terabytes of raw ingestion into a usable asset.
Live walkthrough of the catalog populated with your actual sources.
AI-generated metadata · Audit-ready documentation