31–40 of 47 posts
Would love some docs on migrating from Customer.io. Looks really cool. Congrats on the launch!
I've been in this space for 15+ years now, worked with most of the main players that have on-prem and SaaS solutions, and deployed and run solutions at scale at a few of the largest companies in BigCo land for multiple years now.
I would be cautious on focusing too heavily on the 'developer as the customer' here. Most buying decisions in this space are not made by IT, they are made by CMOs, CXOs, CDOs, etc as that is who owns the budget (and results) tied to this type of solution.
At almost any scale, when you look at total cost of ownership, licensing from one of the main solution providers is usually quite a bit cheaper than building out a whole proprietary stack that one then has to maintain in house via their IT org that likely is not an expert at this kind of stuff.
You guys have some intriguing ideas here. I've been in this space for 15+ years now, worked with most of the main players that have on-prem and SaaS solutions, and deployed and run solutions at scale at a few of the largest companies in BigCo land for multiple years now. I would be cautious on focusing too heavily on the 'developer as the customer' here. Most buying decisions in this space are not made by IT, they ar…
Re-"developer as the customer", the mismatch between who makes the buying decisions for this kind of tech (CMO's etc.), and the devs who do much of the heavy lifting to make it work, is a real challenge.
Also, your point re the economies of scale of self-hosting vs using saas is valid. For small to mid sized orgs, using a cloud offering can be more economical.
However, we've observed that larger orgs often migrate off of saas to use open-source or build software in-house. This occurs for a number of reasons:
- They will have more engineering resources to allocate, in this case to marketing / growth.
- At their scale, the fixed costs of allocating engineers to implementing solutions are often exceeded by the variable costs of saas products, which commonly have volume based pricing.
- They often have more unique requirements that are not served by any particular saas product, and closed source saas is not extensible.
Some recent examples of this:
- Several large orgs are migrating off datadog in favor of open source observability tooling.
- Airbnb recently implemented the equivalent of Dittofeed internally (they responded in this thread).
Still, you raise legitimate concerns, and we're still figuring things out. Would love to get in touch, to better understand your perspective if you have time!
Amazing! Our team at Airbnb built something similar for internal users: https://medium.com/airbnb-engineering/journey-platform-a-low... Very cool how we both use Temporal for workflow orchestration. Love the git idea, Wish you the best!
Thanks for the kind words :) Temporal is a great technology for this use case. Wow, our DSL even looks similar! Your app has beautiful design, which I guess shouldn't come as a surprise given that it's Airbnb. Would love to chat to discuss further. max@dittofeed.com
Earlier quoted context omitted.
Thanks for the kind words :) Temporal is a great technology for this use case. Wow, our DSL even looks similar! Your app has beautiful design, which I guess shouldn't come as a surprise given that it's Airbnb. Would love to chat to discuss further. max@dittofeed.com
Are you using Temporal Cloud?
Would love some docs on migrating from Customer.io. Looks really cool. Congrats on the launch!
Thanks! Definitely, migration guides are coming. In the meantime, feel free to ping us on our community slack and we'll walk you through a migration process.
You guys have some intriguing ideas here. I've been in this space for 15+ years now, worked with most of the main players that have on-prem and SaaS solutions, and deployed and run solutions at scale at a few of the largest companies in BigCo land for multiple years now. I would be cautious on focusing too heavily on the 'developer as the customer' here. Most buying decisions in this space are not made by IT, they ar…
Personally I can see exactly where this product fits in and provides a valuable alternative to the incumbents, and I’m really happy to see a self-hosted open source solution in this space.
The ability to have total ownership and control of the customer data (when needed) is great.
The balance between a friendly UI and a well thought out developer/integration experience seems especially good to me.
The TCO is going to vary wildly based on the org’s scale and state of development. And yes, skillset. Your reservations might be slightly skewed by your experience in “BigCo” land? :)
You guys have some intriguing ideas here. I've been in this space for 15+ years now, worked with most of the main players that have on-prem and SaaS solutions, and deployed and run solutions at scale at a few of the largest companies in BigCo land for multiple years now. I would be cautious on focusing too heavily on the 'developer as the customer' here. Most buying decisions in this space are not made by IT, they ar…
Marketing (via email, push, ad, whatever channel) should be an extension of their product experience and it can be owned by the product/engineering team. I have seen instances where growth-marketing reports to prod/eng.
Makes sense to have more right-brain activities (brand marketing, ads etc) to not come under engineering but growth marketing is often very analytical.