Put a print-ready editor inside your product.

The embeddable design SDK and the headless PDF API are in private beta — design partners wanted. If your app needs a "design this flyer, label, or sign" surface, let's build the launch integration together.

Vertical B2B SaaS and web-to-print platforms whosenon-designer end users produce output for a commercial press. You know the pain: support tickets and reprint refunds every time a file gets rejected at press.

• Web-to-print platforms and print-shop customer portals
• Vertical SaaS with collateral output — real estate, franchise brand portals, restaurant menus, events and signage, labels
• Headless-only dev teams that want server-side JSON in, press-ready PDF out, with no editor UI at all

Evaluate through docs and a working quickstart — not a sales call.

Canva sunset its embeddable Button API in December 2025, orphaning products that had embedded it. Teams that relied on it now have no self-serve path to a print-ready "design this" surface inside their own product.

Building it in-house is a multi-year detour — canvas editor, color management, PDF generation — for a feature that isn't your product.

The remaining option with genuine prepress CMYK is IMG.LY's CE.SDK — enterprise-priced and sales-gated. That price and process gap is where we're building.

Everything below is shipped code, not a roadmap slide. It is also allbeta: the surface is not frozen until general availability and can change without notice.

• Embeddable SDK — beta. Distributed as a private beta tarball, not published to npm. Ships with a working vanilla-JS example host and a quickstart doc.
• Embed session issuance — beta. POST /v1/embed/sessionsissues tokens for hosting the editor inside your app.
• Headless render API — beta. POST /v1/renders(PDF/X-1a, PNG, JPG) and GET /v1/renders/:id.
• API-key auth, per-key rate limiting, origin allowlisting.

POST /v1/renders        → { id, status }
GET  /v1/renders/:id    → { id, status, url }
X-CMYKCanvas-Api-Status: beta

No design partner has a live integration running yet — this is distribution-ready code, not a proven third-party embed.

A direct line to the team, hands-on integration help, roadmap input before general availability, and launch-partner positioning when the SDK ships publicly.

No pricing, no SLAs, no date commitments — an early working relationship, not a sales contract.