I've built embeddable web components since 2008, mostly quietly. A few weeks ago I finally rebuilt the whole thing as a modern platform and launched it.
The idea is simple. Most widget tools drop your content into an iframe. That keeps it isolated, but the widget never really fits your site, and you usually pay a monthly fee per widget. Mine does the opposite. A widget loads with one script tag and renders as normal DOM in your page. Your own CSS styles it like your own HTML. No iframe, no per-widget subscription.
Your page and the widget share one document, and that cuts both ways. Everything inside a widget uses its own prefixed class names, so its styles never leak out onto your page. Your CSS can reach in, and that is the point. It is how you restyle a widget like your own markup instead of fighting a frame. Each instance also carries its own id, so you can drop the same widget more than once without the copies fighting, whether you embed it with a script tag or a PHP call.
If you run PHP there's an even cleaner path. You download your wgclient.php, include it, and call $wg->get(). One call and you get the whole widget rendered on your server, right in your HTML. Leave the mode empty for everything, or ask for just css, js or php and place each part yourself. It works with JavaScript off and search engines see it.
I'm still figuring out what actually matters to people who'd use this, so I'd rather hear real opinions than pitch. If you've ever embedded a third-party widget and hated how it looked or behaved, tell me what annoyed you.
Here's the link if you want to poke at it. https://widget-storm.de/en?utm_source=indiehackers
What I found interesting is that you're optimizing for a widget to stop feeling like a separate product.
The closer an embedded tool feels like it belongs to the host site instead of coexisting beside it, the more invisible the integration becomes—and that's often where the experience feels strongest.