Static project releases
Publish the supported HTML, CSS, JavaScript and asset output of your site.
Core Platform
Hosting & Domains
Publish a reviewed static release. Keep the next version reversible.
Vigthoria Hosting publishes supported static websites from your project. Use a preview, a Vigthoria subdomain or a verified custom domain, inspect provisioning and HTTPS status, and keep versioned releases with rollback. Domain ownership and registration remain explicit parts of the workflow.
Explore this product without signing in. Your account is used when you open the application.
CAPABILITIES / FUNKTIONEN
What you can do with it.
Preview and subdomain
Choose a preview or available Vigthoria subdomain for the reviewed project.
Custom domain verification
Follow the displayed DNS instructions and verify ownership before custom-domain provisioning completes.
HTTPS and provisioning status
Inspect the actual deployment and certificate state rather than assuming the first request is already live.
Version history and rollback
Keep saved releases and restore a supported earlier version through the hosting workflow.
IDEA → WORK → REVIEW → RESULT
A clear path through the work.
- 01
Prepare and test the static project output.
- 02
Select preview, subdomain or custom domain.
- 03
Complete required DNS and account setup.
- 04
Check the public URL, HTTPS and saved release status.
What you keep
A public static-site URL, deployment status and saved release history.
Continue across Vigthoria.
Before you start.
Use an authorized project and the required hosting access. Custom domains need control of the DNS zone and any applicable registration purchase.
Questions before the first project?
What can I take into the next step?
A public static-site URL, deployment status and saved release history.
What access do I need?
Use an authorized project and the required hosting access. Custom domains need control of the DNS zone and any applicable registration purchase.
Can this static hosting run my application server?
No. Publish the static frontend here. A database-backed server or other persistent runtime needs a separately supported backend deployment.
Start with a concrete task.
Publish a reviewed static release. Keep the next version reversible.