What are they: Currently -Frames, and soon (this summer) headless reaction components. An easy way to add features such as template editors, travel/workflows, broadcasts, segments, and anything to send messages to any channel and send automatic messages and send messages automatically. Why are they useful: -cas, and especially vertical sauces, often repeatedly reform these features. Embeded ingredients allow the entire sauce industry to stop restoration. -Gening teams take an average of 6-12 months to implement messaging features. Ambeds take seconds to implement the ingredients. -You are a health care sauce for you, and you want to allow them to send a message to your patients. You are limited and cautious of cloud offerings. With embedded ingredients, you have the option of self -host! Where we are: A limit of early adoptions successfully uses embedded ingredients (self -hosted and in our cloud) in production successfully. Their users are loving them. Engineering manager is very happy with us. Where we are going to: Headless reaction components for 100 style control. -All resources (templates, user classes, etc.) are represented as conference files that LLM can easily manipulate. Although we are an open source company supporting party party for reverse ETL and our base product is free, embedded components are a paid feature. If you are interested, arrive at the Admin API key to support@dittofeed.com, or DM me at PH. If you just want to use our MIT licensed base product as an alternative to cloud, capable, mail champ, etc. You can find it here:
Whatever your opinion you like!