# A site that is a folder, a release and a domain.

Export the site, place it, and it is served under your domain with a certificate. If a change is wrong, serve the previous release again.

[Open the console](https://console.praecise.cloud)

[Talk to us](mailto:contact@praecise.com?subject=Praecise%20Cloud)

In short

A marketing site on Praecise Cloud is a static export placed under your domain, with the bytes served checked and earlier releases kept for rollback. This page is for owners publishing a site. Rivier can build the first site from a description.

## At a glance.

Live

### This is how we ship ours.

praecise.com and praecise.cloud are static exports of one repository, placed as separate sites.

Live

### A brand site on Cloud.

pavilionbygold.com and tenzro.com are served from Praecise Cloud.

Operations

### Rivier builds sites.

Rivier starts from a short description of the business.

## One site, from description to rollback.

5

### [Describe it](https://rivier.ai)

Rivier

Say what the business is. Rivier builds the first site, workflows and agents from the description.

### Export it

Your framework

Any framework that writes a static export works. This site is a Next.js static export, built once and placed as files.

### Place it

Place

Connect the export and name your domains. Praecise places the files and serves them behind the edge.

### Check it

Check

Praecise checks the release before it takes traffic, and the bytes served are compared with the ones that were approved.

### Reverse it

Roll back

Any kept release can be served again.

## What a site gets.

6

### Own your domain

The certificate follows the domain.

Attach one or more domains to a site. The edge issues the certificate on demand, and its state and expiry are tracked.

### Serve static files directly

No runtime to keep patched.

A static tier has no process to restart, so a site is files behind the edge.

### Keep the release

Each change is a release you can name.

Every deploy has a release id. Recent releases are kept for rollback.

### Publish from an agent

The same path serves people and agents.

An agent with access to the project can publish a new export the way a person does.

### Answer to llms.txt

Tell machines what the site is.

A site can ship llms.txt, as this one does, so an agent that arrives knowing nothing can read a map of it.

### Run on one account

Many sites, one place to see them.

The Cloud section of Praecise Spaces lists each placed site as a project, with releases, environment and logs.

## What we handle for you.

3

You

### Build the export.

Any framework that writes static files works.

You

### Add your domains.

Point each domain at Praecise once.

Praecise

### The rest.

Hosting, certificates, a check on every release before it takes traffic, and a kept release to return to.

## What gets published.

6

### A brand site

A company site placed behind the edge, with a rollback if a change is wrong.

### A landing page from a description

Rivier builds it, and you place it like any other site.

### A site with a booking flow

The site is static and the booking agent behind it is a Harness app with its own Inbox.

### A site that agents can read

Ship llms.txt and sitemap.xml beside the pages.

### A preview before launch

Place it under a Praecise address first, then attach the domain when it is right.

### A campaign page

Place a new site for the campaign and remove it when it ends.

## Next pages.

[Web Apps](https://praecise.cloud/web-apps.md)

[Design Engineers](https://praecise.cloud/design-engineers.md)

[Commerce](https://praecise.cloud/commerce.md)

06

## Praecise accounts are by invitation. Open the console, or talk to us.

[Open the console](https://console.praecise.cloud)

[Talk to us](mailto:contact@praecise.com?subject=Praecise%20Cloud)

New to Praecise Cloud? Accounts are set up with the Praecise team: talk to us, then sign in to the Cloud section of Praecise Spaces with an email code.

Source: https://praecise.cloud/marketing-sites