KLXM Studio – Home
Get in touch

Why KLXM Studio

Not a website builder. Your own system.

Websites built from structured content, maintained on your own installation – with open code, open formats and security by default.

Why not a builder

Not a website builder. A foundation.

Your own installation, your own data, a clear structure – and open to whatever comes next.

Typical website builder

  • Hosting, templates and data stay with the provider
  • Drag and drop, page by page
  • Content as layout – hard to reuse
  • Extensions only as far as the provider allows
  • Moving means rebuilding

KLXM Studio

  • Your own installation, your own data – SQLite or MySQL/MariaDB: your database
  • Kits as code, with budgets and accessibility built in
  • Structured content: blocks with fields, data tables, stable links
  • Extensible via block builder, REST API and MCP
  • MIT licence: no lock-in, free to use – including commercially; ordinary PHP hosting

Who is it for?

One system, four perspectives.

  1. Developer

    Framework-free PHP 8.4, REST API (OpenAPI 3.1), MCP server and command line. Kits and blocks as code – or in the block builder without PHP.

    Tech stack & extensions: Developer

  2. Agencies

    Many websites from one installation: network admin with single sign-on, media pools, shared tables, landing domains, support and knowledge base, team chat, feature scope and app icon per website.

    For agencies: Agencies

  3. Marketing

    Landing pages with their own domain, SEO fields and JSON-LD, KLXM Ai for copy, translation and SEO, fast pages thanks to budgets – and cookie-free out of the box: consent only once you add services such as analytics (Consent Kit).

    For marketing: Marketing

  4. Editors

    Edit right on the page, drafts and versions, review queue “Submitted”, assistant, media library with alt texts and captions – plus video tutorials here on the website and as text in every installation’s help.

    For editors: Editors

Principles

Open where it connects. Closed where it protects.

  1. Open to sources

    Content enters the system through documented channels.

    • External sources: RSS, Atom, JSON, XML and OpenImmo 1.2 into data tables
    • REST API with OpenAPI 3.1
    • MCP server for AI assistants
    • Data tables with 23 field types and public forms
    • Optionally for review: changes via API and MCP land in “Submitted”

  2. Open to the outside

    Open licence, open formats – nothing is locked in.

    • Open source under the MIT licence
    • JSON via the REST API
    • sitemap.xml per domain
    • Structured data as JSON-LD (schema.org)

  3. Secure inside and out

    Security is a default, not an add-on.

    • Passkeys and two-factor sign-in, mandatory per role
    • Roles and permissions, data rights per table
    • Content Security Policy without inline scripts
    • No external CDNs

Encryption is part of the DNA.

  1. Form requests are encrypted on submission – the private key is never stored on the server.
  2. The mail password is stored encrypted; API tokens only as a hash.
  3. Uploaded images are re-encoded without EXIF/GPS data; maps and video thumbnails come through our own proxy.

Your data

What you own.

  • Your database

    Every website has its own database – SQLite (one file) or MySQL/MariaDB – and its own media folder.

  • Backup with one command

    php bin/console site:backup saves database and media – site:restore brings them back, e.g. on staging.

  • Stable links

    Links point to pages, entries and files – not to addresses. Renaming breaks nothing.

  • Interfaces, not a silo

    REST API and MCP read and write with the same rules as the admin.

Contact

Talk to KLXM Crossmedia.

A demo, use in your agency or technical questions – we answer personally.

Get in touchCall us
KLXM Crossmedia GmbH
Am Schürmannshütt 40g
47441 Moers
Germany