Launch HN: Unlayer (YC W22) – Add email and document builders to your app

**Unlayer** (YC W22) launched on Hacker News with a pitch to embed visual builders for email, pages, popups, and documents inside other apps. The product is framed as something you drop into your own product rather than a standalone design tool your users leave for. The public face of the launch sits at welcome.email.

The mechanics are embed-first: instead of shipping users to an external editor, you host **email**, **page**, **popup**, and **document** builders inside your UI. That implies an SDK or iframe-style integration surface, a shared canvas/component model across those four surface types, and export or serialization so the host app can store and send the resulting content. The four builders share the same “visual builder” category, which usually means drag-and-drop layout, reusable blocks, and a structured output (HTML or a document model) the host controls.

For engineers building SaaS that needs templated communication or in-product design, this cuts a common build-vs-buy fork. Teams that otherwise write custom editors, block systems, and mobile-safe HTML pipelines can treat layout and preview as an embedded service and keep auth, storage, sending, and branding in their own stack. The value is less “another design app” and more “stop owning the editor surface if it is not your core product.”

The market is crowded with email template tools and no-code page builders, but most of them own the end-user experience end-to-end. Unlayer’s differentiator in this launch is the embed-in-your-app framing: the customer is a product team, not only a marketer opening a separate workspace. That puts it next to white-label and embeddable editor vendors rather than pure campaign tools, and the YC W22 pedigree signals a product-company trajectory rather than a one-off agency widget.

What to watch next is how deep the embed goes in practice: which surfaces ship first for integrators (email is the obvious default), how host apps own data and branding, and whether the multi-builder pitch (email plus page, popup, and document) stays one integration or fragments into separate products. If you are evaluating it, the practical check is simple—can your app mount the builder, round-trip the output into your send/store path, and keep users inside your product without a parallel design login.