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.
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.
00
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.
01
From source to a served release.
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.
02
What the platform does for a web app.
- 01
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.
- 02
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.
- 03
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.
- 04
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.
- 05
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.
- 06
Roll back by release
Return to a known state.
Recent releases are kept and any one can be served again. Older ones are pruned.
- 07
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.
03
What we handle for you.
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.
04
What runs this way.
- 01
A hospitality site with bookings
pavilionbygold.com is deployed and rolled back by release on Praecise Cloud.
- 02
An operator console
The Cloud section of Praecise Spaces is deployed on this platform, with per-project access.
- 03
A site with a database beside it
SQL, document, vector and time-series stores are provisioned next to the workload that uses them.
- 04
An app in a container
An app that ships as a container image is run from the image on the platform.
- 05
A Harness app
A Node app that is also a chat page, a REST API and an MCP endpoint.
05
Next pages.
06
Praecise accounts are by invitation. Open the console, or talk to us.
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.