# Place the app. Keep the machine, the certificate and the rollback.

Connect a folder or repository. Praecise builds it, places the release behind the edge on a machine it operates, checks it is healthy, and keeps earlier releases so you can serve one again.

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

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

In short

Web Apps are placed from a folder or repository behind the edge with a domain and certificate, settings kept outside the release, and any recent release can be served again. This page is for owners and engineers hosting a Node app. Start with the Cloud section of Praecise Spaces.

## At a glance.

Live

### Cloud section of Spaces runs this way.

The Cloud section of Praecise Spaces is deployed on this platform.

Live

### A site from source.

pavilionbygold.com is deployed from source.

Open

### The base is public.

Praecise Cloud runs on Furcate, the open base, which is Apache-2.0.

## From source to a served release.

3

Build

### Give it a folder.

Praecise detects what the folder is. A static export is served as files, a Node app is run, and an app that ships as a container image is run from the image.

Place

### Name it once.

With domains it is served on them. Without, Praecise gives it an address of its own, so a first release needs no DNS work. Certificates are issued on demand.

Operate

### Keep it reversible.

Each deploy is a release. A rollback serves a kept release again and is gated on health like a deploy.

## What the platform does for a web app.

7

### Detect the type

No build configuration to write.

Praecise reads the folder and works out what it is, for example static files served as a static site.

### Place behind the edge

Routing and certificates are done.

Domains, certificates and routing sit in front of every workload, and certificate state and expiry are tracked.

### Check the release

Check what is served is what you approved.

Praecise checks the release before it takes traffic, and compares the bytes served with the release.

### Keep settings out of releases

A redeploy does not disturb credentials.

Environment settings are kept beside the site, outside every release, and survive a redeploy.

### Gate on health

A bad release does not take traffic.

A deploy and a rollback both wait for the site to be healthy before it serves.

### Roll back by release

Return to a known state.

Recent releases are kept and any one can be served again. Older ones are pruned.

### Deploy from a repository

Push a branch, place a site.

A registered repository and branch can be placed from the Deploy button in the Cloud section of Praecise Spaces. A project without a registered source has the button disabled and says so.

## What we handle for you.

3

You

### Connect a folder or repository.

Register the source for a project in the Cloud section of Praecise Spaces and deploy from there. The Cloud section of Praecise Spaces shows releases, environment and logs for each project.

You

### Add your domains.

Point each domain at Praecise once.

Praecise

### The rest.

Servers, certificates, routing, the health check before a release takes traffic, and a kept release to return to.

## What runs this way.

5

### A hospitality site with bookings

pavilionbygold.com is deployed and rolled back by release on Praecise Cloud.

### An operator console

The Cloud section of Praecise Spaces is deployed on this platform, with per-project access.

### A site with a database beside it

SQL, document, vector and time-series stores are provisioned next to the workload that uses them.

### An app in a container

An app that ships as a container image is run from the image on the platform.

### A Harness app

A Node app that is also a chat page, a REST API and an MCP endpoint.

## Next pages.

[Platform](https://praecise.cloud/platform.md)

[Tools](https://praecise.cloud/tools.md)

[Marketing Sites](https://praecise.cloud/marketing-sites.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/web-apps