Chamaileon vs Weavour: Features, Pricing and Usage

Chamaileon vs Weavour is a choice about how much of the email-creation workflow your team wants to assemble. Chamaileon SDK provides modular editor and API tools; Weavour combines an embedded editor with hosted templates, drafts and images for $50 per month per domain.

For SaaS teams evaluating a Chamaileon alternative, the useful question is what happens after the first successful embed: where work is saved, how assets are shared and which usage measures change the bill.

Published by Weavour. This comparison uses public vendor documentation checked October 30, 2026; it is not an independent benchmark. Prices below are monthly USD amounts. Confirm current terms before purchasing.

Chamaileon vs Weavour: the feature comparison

Both products put email creation inside your application. Your product continues to own recipients, send approval and delivery. Compare the editing and content workflow against the requirements your customers actually have.

Area	Chamaileon SDK	Weavour
Integration	Modular plugins and generation APIs	Hosted iframe, JavaScript/TypeScript SDK and React wrapper
Editable content	Email JSON with host save hooks	Versioned JSON, hosted drafts and 30-day draft history
Reusable content	Block libraries, components and block locking	Organization blocks and shared templates; insertion creates independent copies
Dynamic content	Conditions, loops and dynamic images	Merge tags and host-defined layout conditions
Images	Gallery plugin wired through integration hooks	Hosted organization and personal libraries
Appearance	Locale, theme colors, fonts and branding hooks	English, French and Spanish; configurable light/dark themes
AI	Assistant UI connected through a host hook	Managed text, image and editable-email generation, or customer OpenAI keys

Chamaileon’s editor reference documents the save hooks, components and advanced elements above. Its customization guide covers locale, colors and fonts. Verify commercial entitlement for the add-ons you need; a documented setting does not establish its availability on every plan. Weavour’s documentation explains its embedding and content model.

Reusable content deserves a separate acceptance test. A product that must update an existing component everywhere has a different requirement from one that should preserve each author’s independent copy. Write the expected outcome before testing either editor.

Pricing: monthly active users versus domains

Here are the public Chamaileon SDK plans checked on October 30, 2026:

Plan	Monthly price	Included monthly active users	Included generator calls
Starter	Free	10	100
Standard	From $200	200	500
Scale	From $600	1,000	15,000
Enterprise	Custom	Contract-specific	Contract-specific
Weavour	$50 per domain	Unlimited users and editors	Subscription billed by domain

Chamaileon counts a unique user who opens the editor during the month; repeat sessions count once. Its pricing page describes each HTML export as a generator call. The SDK terms allow a plan adjustment after continued excess for two consecutive months; they do not publish a universal per-call overage rate.

Weavour charges per registrable domain within a customer workspace, including its subdomains. Two separate domains cost $100 per month. Template and image storage and bandwidth are unlimited, with no storage or bandwidth overage charges. AI has a separate credit allowance: 2,000 managed credits per paid domain per month, or customer-key usage billed by OpenAI. Unlimited users does not mean unlimited AI.

Consider a hypothetical application on one domain, with 180 monthly editor users and 400 HTML generations. The published Standard allowances cover those counts, starting at $200; Weavour’s domain subscription is $50. At 1,000 users and 12,000 generations, Scale covers the counts from $600, while the same Weavour domain remains $50.

These are subscription examples, not equivalent-feature quotes or total ownership estimates. Add your required add-ons, provider usage, implementation and storage arrangements. If your application uses several production domains, include every billable domain in the Weavour calculation.

Integration: choose where responsibilities live

The Chamaileon v2 quickstart requires a secret API key kept on your server. Your backend exchanges it for an access token; the frontend obtains that token through your endpoint and supplies a refresh function. Your application also connects save events to its persistence layer.

Its HTML generator guide recommends backend generation from stored JSON and documents Handlebars, Liquid, Mustache, Mailchimp and Adobe Campaign Classic output options. That is useful when generation belongs in an existing backend workflow. Do not assume that using a browser export method removes commercial usage limits.

Weavour mounts with a public editorKey, a supplied userId and an optional organizationId, without a customer token endpoint. These IDs are namespaces within your Weavour workspace, not verified identities. Your application must supply the correct context and control access to its own interface. Multiple editors can share an organization’s image library within that workspace.

Plan the handoff to your sender explicitly. Keep the editable source and identify the revision approved for sending. Check merge tags and conditional content with your own sample values. Our guide to editing and email delivery explains that boundary.

Everyday usage: assets, drafts and AI

A realistic pilot starts with an unfinished email. Ask an author to find a starting template, change an image, leave the page and resume later. Then repeat the task for a second organization. This reveals ownership and recovery requirements that a drag-and-drop demonstration misses.

Chamaileon’s gallery plugin supports folders, image selection and basic editing through integration hooks. Establish who supplies asset storage, upload handling and retention for your chosen arrangement. Weavour hosts organization and personal libraries alongside drafts and templates, giving teams a ready content workflow. A shared template library still needs clear naming and ownership rules.

Both products provide AI assistance. Chamaileon’s documented assistant calls onAiAssistant, with a backend implementation example. Weavour includes managed credits and supports customer keys during active trial or paid access. Test the actual task: translate text, preserve placeholders, review the suggestion and continue editing. Do not compare providers’ credit units as if they bought identical work.

Which email editor fits your SaaS?

Choose Chamaileon SDK when your team wants modular plugins, an existing persistence architecture or specific generator templating options. Its linked components and loops merit evaluation when those behaviors are central requirements. For procurement needs, ask about its advertised enterprise residency, SSO and SLA options and obtain the exact scope in writing.

Choose Weavour when you want hosted libraries, recoverable drafts and predictable domain-based pricing as more customers use email editing. It suits a SaaS product that already handles sending and wants its engineering team focused on the host application.

Give both candidates the same pilot: one difficult real template, two organizations, a failed save, a reopened draft and a send through your supported mail clients. Record what your team must build and what the service supplies. Only Weavour’s embedding SDK is open source; the hosted editor and services are private.

To evaluate that workflow, start Weavour’s one-month production trial. No credit card is required. Local development is free; the production trial includes 200 managed AI credits per domain for the entire trial, and paid activation is explicit.