Self-Host Keila or Use the Hosted Version? How to Decide

Choose the hosted version if you want to send newsletters without running a server, and self-host if you need full control over where contact data lives or want to modify the application. Both options run the same open-source software, so the deciding factors are operational: who maintains the server, where data is stored, and how much customization you need. Keila is a 100% open-source newsletter tool, made in Germany and hosted in the EU, and its homepage offers two entry points: "Get started" (hosted) and "Try self hosting."

What both options give you

Because the hosted service and a self-hosted instance are the same codebase, the feature set does not change with your choice:

• Email creation in several modes — a visual Block Editor, Markdown (directly or through a Markdown-powered WYSIWYG editor), MJML for full design control, and plain-text sending.
• Base templates designed to render consistently across Gmail, Outlook, Thunderbird, mobile, and desktop.
• Contact list management and personalized campaigns.
• A form builder for sign-up forms with extra checkboxes, text fields, and dropdowns.
• Bot protection through captcha checks and double-opt-in verification.
• Personalization using custom data fields from sign-up forms or external sources such as CMS or CRM systems, represented as a single JSON object per contact and campaign, with Shopify's Liquid template language.
• Analytics with privacy controls, including the option to turn tracking off entirely.

If your decision hinges only on features, there is nothing to weigh — the difference is who operates the instance.

Self-hosting: what you take on

Self-hosting means you install and run Keila on infrastructure you control. In exchange you get:

• Data residency you decide. Contact lists and campaign data stay on your own servers rather than in Keila's EU hosting.
• Customization freedom. As open-source software, the code can be modified to fit your workflow.
• No dependency on a third-party service for uptime or policy changes.

What you accept in return:

• Server maintenance. You handle installation, updates, backups, and monitoring.
• Deliverability work. Sending email at scale involves domain authentication and reputation management; a self-hosted instance does not remove that responsibility.
• Technical capacity. Someone on your side needs to be comfortable running a web application.

Hosted: what you trade away

The hosted version removes the operational burden — you sign up and start sending, with the instance running in the EU. The trade-offs are the mirror image of self-hosting:

• You do not control the physical location or infrastructure of your data beyond what the provider states.
• You cannot modify the application itself.
• Your sending depends on the provider's availability and terms.

How to choose

Pick self-hosting if data sovereignty, code-level customization, or independence from a vendor outweighs the cost of running a server — for example, an organization with strict internal data rules and an existing ops team.

Pick hosted if you want to send newsletters this week without hiring or assigning technical staff, and EU hosting satisfies your compliance needs.

What the homepage does not tell you

The site's pricing page is linked but no figures appear in the available material, so cost cannot be compared here — check https://www.keila.io/pricing directly before deciding. Likewise, the homepage does not state whether the hosted and self-hosted versions differ in sending limits, support, or update cadence. If those matter to you, confirm them with Keila before committing.