# What Kywi is

URL: https://kywi-docs-production.up.railway.app/start/what-kywi-is
Type: docPage

Kywi is a CMS engine your Next app mounts, whose pages, audiences and experiments are edited by people and by agents against one API.

`@kywi-software/core` is the engine: schema, REST API, admin components, content scope. `next` is a peer dependency of it — only the `@kywi-software/core/next` adapter imports from Next itself; everything else in core is framework-decoupled. What `create-kywi-app` generates for you is a thin Next host — config files, session wiring, and one catch-all page that mounts the whole admin — that stays yours to edit, while the render path itself lives in the package and upgrades with it.

## One app, one database, several sites

A Kywi install is not one site per deployment. Each site is a config entry, matched to a request by its `Host` header and reconciled into its own database row at boot — so adding a site is a config edit and a layer entry, not a second app. See [One config, several sites](/developing/one-config-several-sites/).

## Three ways the same content gets edited

The admin edits any page through the Site Tree and the layout editor. The front-of-site overlay (`?kywi-edit=1`) edits a published page in place, without leaving it. An agent edits the same content over MCP or REST. All three write through the one API — nothing about a page's shape depends on which door it was edited through. See [Turning on edit mode](/editing/turning-on-edit-mode/) and [Two servers, two jobs](/agent/two-servers-two-jobs/).

## What is actually unusual here

Targeting is part of the page model, not a plugin bolted onto one. Wrap a section in a variant container and it becomes a set of arms — a default plus whatever audiences or experiment variants you add — and one fixed precedence decides which arm a given visitor is served. See [Regions, sections, columns and modules](/authoring/regions-sections-columns-and-modules/) and [Which version of a page a visitor gets](/targeting/which-version-of-a-page-a-visitor-gets/).

## What Kywi is not

## No hosting, no backups, no CORS

Kywi does not host your app — you deploy the Next build yourself. It does not back up your database. And core sends no CORS headers, so a browser on another origin is never a supported caller of the API; a decoupled frontend has to talk to it server-side. See [Backups: what Kywi does not do for you](/operating/backups-what-kywi-does-not-do-for-you/) and [Topologies that work, and the cross-origin wall](/integrating/topologies-that-work--and-the-cross-origin-wall/).

Next: [Install and scaffold](/start/install-and-scaffold/).
