# From a design export to a URL anyone can open.

Place the export under a name. It is served on an address the platform gives it, with no DNS work, and on your domain when you attach it. Every change is a release.

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

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

In short

Design engineers turn a design export or repository into a live URL, with a release for every change and any earlier release can be served again. This page is for people sharing work for review. Start by connecting the export.

## At a glance.

Address

### A URL without DNS work.

Until you attach a domain, a placed site answers on an address Praecise gives it.

Releases

### A release per change.

Each deploy has a release id, and recent releases are kept.

Live

### Brand sites on Cloud.

pavilionbygold.com is a hospitality brand site deployed and rolled back by release.

## From a file to a URL.

3

Build

### Export.

Export static files from a design tool or build a repository's static output.

Place

### Name it.

Connect the export and name it. With no domain, Praecise gives it an address you can share.

Operate

### Change and compare.

Place the next export under the same name and it becomes the new release. The earlier release stays kept.

## What helps a design review.

6

### Share a link early

The page is real before launch.

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

### Know which release

Each change has an id.

Every deploy has a release id, so a review can name exactly what it looked at.

### Go back

A wrong change is not a crisis.

An earlier release can be served again.

### Check the release

What is served is what you shipped.

Praecise checks the release before it takes traffic.

### Keep fonts and images

The export is served as files.

Static assets are served as they were exported, with the page.

### Hand over to an agent

Routine updates need no person.

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

## What we handle for you.

3

You

### Send the address.

Share the link for review, and publish the next export to replace it.

Praecise

### Checks and keeps.

Each release is checked before it takes traffic, and earlier releases are kept.

You

### Go back if needed.

Ask for an earlier release and Praecise serves it again.

## Design work that fits.

6

### A brand site preview

Share the Praecise address, then attach the domain.

### A prototype in a browser

Place the static export and send the link.

### A launch page with a safe rollback

Keep the previous release and serve it again if needed.

### A component site

Place a static export of a component library.

### A site that an agent updates

An agent places the next export, and a person reviews the release.

### A site built from a description

Start in Rivier, then take over the export.

## Next pages.

[Marketing Sites](https://praecise.cloud/marketing-sites.md)

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

[Tools](https://praecise.cloud/tools.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/design-engineers