11–20 of 43 posts
Thanks for checking us out! Co-founder here, happy to answer any questions. There is so much to do in this space, but we’re excited to be getting started. No engineer wakes up in the morning excited to sync data to Marketo, so we started there - `npm install` and so you can get back to building the core product. We make data self-serve for your non-technical colleagues and we handle all the exhausting integration stu…
Thanks for checking us out! Co-founder here, happy to answer any questions. There is so much to do in this space, but we’re excited to be getting started. No engineer wakes up in the morning excited to sync data to Marketo, so we started there - `npm install` and so you can get back to building the core product. We make data self-serve for your non-technical colleagues and we handle all the exhausting integration stu…
Thanks for checking us out! Co-founder here, happy to answer any questions. There is so much to do in this space, but we’re excited to be getting started. No engineer wakes up in the morning excited to sync data to Marketo, so we started there - `npm install` and so you can get back to building the core product. We make data self-serve for your non-technical colleagues and we handle all the exhausting integration stu…
Thanks for checking us out! Co-founder here, happy to answer any questions. There is so much to do in this space, but we’re excited to be getting started. No engineer wakes up in the morning excited to sync data to Marketo, so we started there - `npm install` and so you can get back to building the core product. We make data self-serve for your non-technical colleagues and we handle all the exhausting integration stu…
So, what's informed your making this open source?
In the past, you needed a large, focused SaaS vendor to be able to store a million users and their properties/events. AWS and friends have caught up and now it's easy. Because of that, we can take that data into your own environment and use it to increase control, customization, privacy, and compliance. The cost is significantly better, too.
Open source is a good way to do that because you know what you are running and can fit it to your needs. Engineers tend to like open source and we've seen interest in extending it. There are thousands of things to connect with, both inside your infra and outside with vendors, and open source makes that possible.
Does it have an API to access the user profile and group data ad-hoc?
Can you stream data in?
Can it trigger a destination sync when the underlying data changes?
Can it do profile merging (visitor -> known customer stitching)?
How can you do reporting/analytics?
Oh wow, this reminds of Hightouch ( https://hightouch.io ) and Rudder ( https://rudderstack.com ). It's interesting that all of these are positioned around data warehouses, which is generally very messy to deal with.
We've built an e2e marketing automation platform on top of your data warehouse. Marketers can interactively explore their customer base, run targeted campaigns in downstream email/ad/etc tools, and analyze results leveraging all the data they have in their warehouse.
RE: "messy data" -- Totally agree with bleonard's point that overall, the trend is towards data enablement. That said, I don't think any of the solutions in the markets (even Looker) suffice. I've attended dozens of calls with Looker users who first say that Looker offers self-service exploration but then fail to retrieve fairly basic information via a Zoom screen-share. The truth is it's really hard to do self-service data exploration generically. I think what's lacking from the "BI market" are more verticalized solutions on top of your warehouse (think UIs like Amplitude's funnel analysis, Intercom or Kustomer's segmentation interface, etc.).
To make our product work, we've built UIs that are super focused on particular tasks as well as a pretty nifty graph-based "modeling layer" that sits above your warehouse (which ideally, you use DBT/Dataform on) to abstract over complex JOINs and such.
This whole space is super fascinating to me. Always happy to exchange notes and talk shop RE: marketing, warehouses, customer data, etc. If you have thoughts, hit me up at tejas [at] hightouch.io.
Oh wow, this reminds of Hightouch ( https://hightouch.io ) and Rudder ( https://rudderstack.com ). It's interesting that all of these are positioned around data warehouses, which is generally very messy to deal with.
Thanks for the links. Overall, there's an interesting organizational dynamic that we've seen around data enablement. Marketing and other operational teams need it and it's often locked in the product space. It's usually not a priority for the eng team because they are focused on the core product, but the data is there. The important stuff (ETL copy of the product db) is usually not a huge mess. We are inspired by war…
As a Rudder and Fivetran user, I can see a very complementary use case for Grouparoo. Where the first two are responsible for unifying events and external data in the DW and Grouparoo to sync user data to other tools.
Two other tools that I saw in this space (not Open Source): https://www.calixa.io/ https://windsor.io/
Thanks for checking us out! Co-founder here, happy to answer any questions. There is so much to do in this space, but we’re excited to be getting started. No engineer wakes up in the morning excited to sync data to Marketo, so we started there - `npm install` and so you can get back to building the core product. We make data self-serve for your non-technical colleagues and we handle all the exhausting integration stu…
How does this differ from something like Stitch (other than being open source)? We are in the planning stages of a data warehouse upgrade and Stitch seems to fit our needs, but your product looks great. I'm curious how it compares.
Stitch looks to be doing ELT in the fivetran-ish space. Their "sources" are lots of tools and their "destinations" are warehouses. Grouparoo can have sources like Mailchimp (did they read the mail), but Mailchimp is more likely to be a "destination" for us.
This is because we are doing more like ETL to those tools. In our current case, the "T" is property and segmentation definitions, often done by end users like marketers. So that notes that our users also include non-engineers. There's less burden on engineers after setting up Grouparoo because the person in charge of Mailchimp are doing those definitions.
Earlier quoted context omitted.
Thanks for the links. Overall, there's an interesting organizational dynamic that we've seen around data enablement. Marketing and other operational teams need it and it's often locked in the product space. It's usually not a priority for the eng team because they are focused on the core product, but the data is there. The important stuff (ETL copy of the product db) is usually not a huge mess. We are inspired by war…
In my experience this scenario is very accurate. Add to it the growing usage of tools like Pipedrive, Pipefy, Airtable, that sometimes prod-eng team is not even aware. As a Rudder and Fivetran user, I can see a very complementary use case for Grouparoo. Where the first two are responsible for unifying events and external data in the DW and Grouparoo to sync user data to other tools. Two other tools that I saw in this…
So I hope there's a place because it's the gap we saw and are hoping to solve and share with the community. Email me if you want to chat more: brian [at] grouparoo.com
Thanks for checking us out! Co-founder here, happy to answer any questions. There is so much to do in this space, but we’re excited to be getting started. No engineer wakes up in the morning excited to sync data to Marketo, so we started there - `npm install` and so you can get back to building the core product. We make data self-serve for your non-technical colleagues and we handle all the exhausting integration stu…
What is your monetization strategy? How are you going to turn Gruparoo into a profitable business?
The philosophy I've heard (maybe from Hashicorp?) is that the core should solve the data problem and the enterprise edition should solve organizational problems. So the source and destination and the syncing data and all that will stay in the core. At some point, we can do single-sign on, change, change management, GDPR support, compliance, etc in the enterprise version.