---
title: Several sites in one deployment
description: Serve more than one site from one Hollware, with their own collections, tokens and people.
section: guides
order: 4
---

# Several sites in one deployment

One Hollware serves every site of its database. Each site has its own collections, entries, tokens and members; nothing crosses from one to another.

## Add a site

In the admin, under **Site**, make a new site: its key, its locales and a preset to start from. You are its owner, and it is served at once; switch to it from the header to shape it. An agent with `schema:admin` does the same with `create_site`. From the command line, `init` adds a site to the owner of the database and prints a token of it:

```sh
npx hollware init --site docs --preset docs --remote
```

A site you no longer need goes to the trash from the same page: it is served no more, its tokens stop working, and nothing is deleted. Bring it back from another site you own.

## Tokens and grants

A token belongs to one site and acts on it alone, whatever it asks for. An agent that writes to two sites has two tokens, or two OAuth grants. A site that reads over the service binding names its site in each call.

## People

A person is one across the deployment, with one passkey. Their role is per site: an author of the blog can be an editor of the docs.

::callout{type="note"}
An invitation always makes a new person for now. Someone who is already a member of one site and is invited to another sets up a second passkey for it.
::

This site is one: hollware.com reads its docs from the same Hollware as the demo blog.