Keila

Key features

• Visual block editor plus Markdown: compose campaigns in a block-based editor or write in Markdown, reusing saved layouts across campaigns so repeat sends keep a consistent look.[1]

• Reusable layouts and personalization: shared designs carry campaign content with subscriber-specific personalization from stored contact data, which suits teams sending tailored variants of one newsletter.[1]

• Segmentation with tags: filter contacts into targeted groups on attributes and tags before sending, so announcements and digests reach only the readers they concern.[1]

• Signup forms with double opt-in: embed forms that take direct or confirmed subscriptions, with confirmation gating delivery on double opt-in lists for cleaner consent records.[1]

• A/B testing for campaigns: compare variants to decide which subject or content performs better instead of guessing from a single send.[1]

• Per-campaign analytics: read opens, clicks, and bounces per campaign, with documented attention to privacy-friendly measurement that fits the product's GDPR positioning.[1]

• Marketing automation journeys: trigger multi-step flows from contact events with actions that run the follow-up, covering welcome sequences and routine nurturing without manual sends.[1]

• API for sending and integration: send campaigns programmatically and connect signup and contact operations to an existing stack, which is the path for developers embedding newsletters in a product.[1]

Who will love it

• EU senders needing GDPR-aligned tooling: privacy-friendly positioning, EU-based operation, and subscriber data that stays on infrastructure you choose matter most where consent records and data location are scrutinized.[1]

• Small teams leaving per-contact SaaS pricing: the Solo Cloud plan bundles 10,000 contacts with unlimited projects and emails instead of charging per send, which changes the budgeting question from list size to a flat fee.[1]

• Developers embedding newsletters in a product: the API plus embeddable forms expose signup, contact, and sending operations to custom stacks, so the newsletter becomes part of the product rather than a separate silo.[1]

Who should avoid it

• Teams wanting zero server operations: self-hosting means running the service and owning upgrades, sender setup, and the reputation that decides inboxing, and that work does not disappear behind the open-source price of zero.[1]

• Marketers needing a large template marketplace: Keila offers reusable layouts, not the large template library a mass-market SaaS provides, so teams that start from ready-made designs will feel the smaller gallery.[1]

• Operators planning to resell hosted sending: AGPLv3 network copyleft attaches source-sharing obligations to hosted use, so get compliance advice before offering it to others.[1]

Alternatives and compatibility