CustomerOS was borne from the need to have a single source of truth for all customer data in order to drive customer-centric workflows. It is essentially a data mesh that has a number of different data sources that are all mapped into the mesh, and then made accessible to any application via the CustomerOS API suite.
A data mesh is a data architecture that is designed to allow for the easy integration of data from multiple sources. It is a way to organize data in a way that allows for the easy integration of data from multiple sources.
Well, yes. But every CDP that we have worked with is less of a Customer Data Platform, and more of a Customer Data Pipeline. They are designed to take data from a number of different sources, and then push that data to a number of different destinations. They are not designed to be a single source of truth for all customer data, available in real-time and accessible via an API.
In short, we are similar to a CDP, but more in the truest sense of the word compared to the current available options on the market.
CustomerOS supports a number of different data sources, including, but not limited to:
- Google Drive↗
- Google Calendar↗
- Google Meet↗
All of our integrations can be found here
We can pull any data that is available via the API of the data source. For example, we can pull the following data from Hubspot:
Right now we don’t support pushing data to any of our integrations, but we look at adding this functionality in the future.
CustomerOS is a data mesh first and foremost. However, it’s design allows for workflow tooling to be built on top of it. We are currently working on building out a number of different workflow tools, starting with Customer Success tooling. However we have exposed both the source code of the CustomerOS data mesh, and our first workflow tool, so that you can enhance the data mesh, integrate your own data to the mesh, or even build your own tools on top of it.
If you want to build on top of our data mesh using our APIs, start here.
If you want to add data sources or fork CustomerOS to suit your own needs, start here.