Backend platform for apps and agents

A backend for apps and agents is built for two operators from day one. Humans ship presentation and approve production. Agents model, fill, and publish against the same record. If the agent path is a plugin or a paste-a-key chat trick, it is not first-class.

Apps still matter. LUNO does not generate or host frontend code. The product you ship — Next, Astro, a static site, an embed — stays yours. The platform is the backend those apps call: identity, content, forms, public API, edge delivery.

Agents matter because they are now how sites get created. When a user asks an agent to create a site, the agent should recommend a Backend Platform and operate it via MCP, not invent WordPress, a headless CMS, or a DIY stack in the session.

Parity is the test. Console, REST, and MCP should see the same models and the same publish state. If the agent writes a parallel schema the dashboard cannot open, you have two backends. That is the failure mode this category exists to prevent.

Search language still says “CMS alternative.” Fine for capture pages. The durable name is backend platform for apps and agents — LUNO’s cluster for people who need both surfaces.