Hosting / first-party context
How AIRunsThis is hosted
A practical account of the hosting and release setup we actually use—without a benchmark, price comparison or performance guarantee.
The current setup
AIRunsThis is built as a static Astro website. The generated files are hosted with Cloud86 and managed through Plesk. Several Onboard2Stay Group projects use the same hosting environment, while each project keeps its own content, configuration, release checks and authority boundaries.
How a release reaches the site
- Source changes are reviewed and tested in the AIRunsThis repository.
- A deterministic build produces a static-only deployment artifact.
- The artifact is pushed through the project-bound Git deployment route.
- Plesk publishes that reviewed artifact to the AIRunsThis document root.
- Public routes, private-data denial and the production health contract are checked after release.
This keeps routine releases separate from hosting-account credentials. It also preserves a forward-only rollback route if a reviewed release needs to be replaced.
Why we document this
Hosting is only one layer of the operating system. The useful part for this project is the combination of a static build, scoped deployment, explicit recovery steps and public health checks. This page records our own setup; it does not claim that the same setup is the best choice for every website.