---
title: Websites
description: "A website is the top-level container for design surfaces, objects, settings, files, and access. Everything on a website is pure-schema-driven: the same models and editors power every site, with no hidden per-site logic, so behavior stays consistent and recreation (from templates or exports) stays faithful. New websites start in preview mode until a subscription is active."
---

## Templates

A new website can start from a catalog template or blank. Templates are pure schema seeds: they copy object types, pages, roles, and related starting structure into your site. They do not hold bespoke or hidden logic, behavior comes only from the shared, schema-driven platform features you configure afterward, so recreation stays consistent.

[Browse templates](/en/getting-started/templates)

## Create a website

You can create a website from the admin panel, the REST API, or MCP. All three use the same platform account.

### Admin panel

Sign in to the admin panel, open your websites list, and create a site with a name, locales, and a template (or blank).

[Admin panel](/en/interfaces/admin-panel)

### API

POST an authorized request to the websites collection.

```
POST /api/v1/en/websites
```

Use the following request body shape:

```json
{
  "name": "My site",
  "templateId": "blank",
  "primaryLocale": "en-US",
  "enabledLocales": ["en-US"]
}
```

Authorization uses a Bearer token from the login endpoint. Details are in the API interface guide.

[API](/en/interfaces/api)

### AI Agents (MCP)

Call list_templates / get_template first, then create_website with a template id or blank. See the MCP interface guide for auth.

```
list_templates
get_template
create_website
```

[AI Agents (MCP)](/en/interfaces/mcp)

## Website features

Each website exposes the same feature areas. The short notes below link to the dedicated docs sections.

### Design

Page, header, footer, email, and component editors: the block catalog and shared decoration/visibility rules.

[Design](/en/design)

### Objects

Object types, entries, permissions, components, user roles, lifecycles, and picker-built calculated fields for structured app data.

[Objects](/en/objects)

### Website settings

Identity, favicon and install-as-app, member web push, locales, domains, email delivery, external linking, and privacy-aware web integrations (GTM, analytics, verification tags).

[Website settings](/en/settings)

### Access

Platform roles and platform users who can administer the website.

[Access](/en/access)

### Files

Uploaded files and directories used by pages, objects, and email.

[Files](/en/files)

### Theme & layout

Theme tokens and layout settings that keep the site visually consistent.

[Theme](/en/theme)

### Insights

Statistics and reports for traffic and operational visibility.

[Statistics](/en/statistics)