A data management system built around joined records.

dPivot is designed around the idea that business data should connect cleanly across the platform. Products, brands, accounts, categories, imports, images, files, and custom systems all live in the same model so data can be reused instead of copied, then returned through APIs for client websites, applications, and front-end components to consume.

How the platform works

  • Accounts give users access to the records and tools they need, including products, images, files, and imports.
  • Products can belong to many brands, carry multiple images and files, and participate in categories, groupings, and custom product types.
  • Imports can read XML, XLS, JSON, and other files from uploads, SFTP, or S3 to bring external data into the platform.
  • Images and files can be joined to products, including support for multiple images, 360 variants, watermarks, manuals, and automatic thumbnails.
Contact dPivot
dPivot admin interface

A joined data model

The core of dPivot is the ability to join data across the system. Products, accounts, images, files, categories, brands, and custom types are not isolated modules. They can relate to each other so your data behaves like a connected model instead of a collection of separate tools.

Imports built for real-world source data

Imports are designed to ingest business data from the places teams already use. Source files can be uploaded directly or read from SFTP and S3. XML, XLS, JSON, and similar structured files can be pulled into the system and organized for downstream use.

Custom systems without losing the product context

dPivot also supports custom development on top of the base platform. That includes systems like warranty management and registrations, where product specifications, account data, serial numbers, and ownership records all stay connected instead of being duplicated across unrelated applications, websites, or support tools.