Questions about Kaleta.

An open-source CMS for business websites. It comes with a visual builder, a design system, collections, online booking, forms with an enquiry inbox, Google and CRM connections, EU compliance tools and statistics – and Claude can build the site and help run it, as drafts you approve.

Yes. Kaleta is licensed under GPL-2.0-or-later, with no paid tiers or per-site licences. Development is supported by voluntary contributions through Buy Me a Coffee.

Companies, tradespeople, consultants, clinics, local services and the agencies and freelancers who build their websites. It is not an online shop, a membership platform or a course system.

Since Kaleta 3.0, yes – as add-ons. An add-on is a folder in extensions/ that hooks in through a versioned extension API; an administrator switches it on under Administration → Features → Add-ons after confirming they trust the code, and one that fails switches itself off. Most sites need none: news, forms, booking, newsletter, statistics, redirects, language versions and the Claude connection are built-in features you switch on and off under Features, tested together.

The admin is in English, Czech and German. A site can be in around forty languages, including regional versions such as British English or Brazilian Portuguese, and have several language versions. Visitor texts (buttons, forms, dates) are translated into 12 languages: Czech, English, German, French, Spanish, Italian, Polish, Slovak, Portuguese, Chinese (simplified and traditional) and Arabic, which reads right to left. German comes with the formal Sie or the informal du. Other languages fall back to English with dates in their own format.

Yes. The site export packs everything – pages, news, collections, components, site parts, the look and the media – in an open format, and another Kaleta installation imports it in a few clicks.

No. The builder, design system and everything else work without AI. Claude and the writing assistant (your own key) are optional.

New installations have the Claude connection on, and connecting Claude is the first of the First steps on the dashboard. Add your site’s /mcp address as a connector in the Claude app, sign in on your own site and choose what the connection may do: drafts only (where a new connection starts), everything your account may, or read only. Claude Code connects the same way.

Within your account’s permissions and the connection’s access, it builds pages, the header and footer, collections and the look, uploads media, writes news and works through the requests staff send through Ask Claude. Pages and news are drafts until you publish them; a drafts-only connection can also save hidden collection items, proposed exceptions to the opening hours and triage suggestions, which a person applies. Guardrails in Claude settings can limit changes per hour, protect pages and rule out deleting. It cannot change the site e-mail, webhooks, mail, backups or security settings.

Claude sends a signed preview link to each draft, and everything that waits for a person shows up in Waiting for you on the dashboard. Every change it makes is in the change log with its reason, and Claude settings → Claude sessions undoes everything one session changed in one step.

Yes, with a routine in the Claude app or Claude Code: the site keeps the schedules (weekly review, monthly report, enquiry triage, staff requests) and the routine does what is due, as drafts. A missed run raises an alert.

Buttons in the builder and in news that create a section from a description, rewrite text, suggest titles and SEO descriptions or translate. It uses your own API key for Anthropic Claude, OpenAI, Google Gemini or Mistral, and text is sent only when you click an assistant button.

Any hosting with PHP 8.3 or newer and MySQL 8 or MariaDB 10.6+. Upload the files over FTP, create an empty database and open /install.php – it takes about ten minutes. The download page lists the PHP extensions.

Updates are signed and checked before they install. After an update the site checks itself and puts the previous files back if something fails. Security releases can install themselves. In Settings → Backups and updates you choose the channel: Latest (the default, a new minor every week) or Stable (security fixes and a new minor about once a month).

Yes. Kaleta backs up the database automatically every day something changed. Add an FTPS or S3 target in Settings → Backups and updates and the backups are copied off the server, together with the media.

Pages are clean HTML with CSS only for the elements used on them. Every release checks each starter site in Lighthouse on the test server: 100 for accessibility, best practices and SEO, and at least 90 for performance.

Yes. Each site is its own installation; a fleet console shows all paired sites on one screen with health, uptime and staged updates, and a shared design kit sends tokens, classes and components to them as drafts.

Yes. Importers bring WordPress, Ghost, Blogger, Joomla, Drupal and Webflow content with images and 301 redirects from the old addresses – from WordPress also WooCommerce products and Polylang or WPML language versions. Any other site comes in by its address, a migration report checks every old address before you switch, and Claude reworks the layout. See the migration guides.

The built-in statistics measure visits without cookies. If you add analytics or marketing codes, the built-in cookie bar holds them back until the visitor agrees and keeps an anonymous record of the consent; a cookie scanner lists what the site sets. Maps load only after a click.

On your own hosting, in your database. Content leaves it only through features you set up yourself – the writing assistant, the Claude connection, integrations with Google or your CRM, an enquiry webhook or off-server backups.

Submitted forms are stored in the enquiry inbox and deleted or anonymised automatically after a set number of months – 24 by default. Personal data requests let you find, export or erase everything about one e-mail address.

Kaleta gives you templates – a privacy policy draft, a record of processing and an accessibility statement from the audit – as starting points only. You are responsible for the legal texts on your site and should adapt them to your situation and your country’s rules.