Site Hosting
Vertra Cloud offers site hosting with infrastructure optimized for web applications. Each site runs in an isolated container with dedicated resources, automatic SSL and network abuse protection.Site Types
- Static Sites
- Dynamic Sites
Sites composed of HTML, CSS and pure JavaScript. Ideal for landing pages, portfolios, documentation and SPA applications.How to configure:
- Send the folder with your static files as a
.zipin New Project - In Build, the runtime is detected as Static and
index.htmlas the main file - Turn on web publishing in Network
- HTML5, CSS3, JavaScript ES6+
- Web Components
- Service Workers
- Any compiled frontend framework (React, Vue, Svelte, Angular)
Subdomains
Each published application receives a subdomain in the format:Publishing and unpublishing
Web publishing is not decided once and for all at creation. An application created without a subdomain runs privately, and you can turn publishing on later — or off again — from the application’s Network settings, or through the API with Publish Application on the Web.Custom Domains
To connect your own domains (several per application, depending on the plan):1
Add domain
In the application panel, go to Network and add your domain. The
www (or root) companion is added with it and doesn’t count toward the limit.2
Configure DNS
Add the CNAME record pointing to the address provided by the platform. A root domain needs a provider that supports CNAME flattening.
3
Wait for propagation
DNS propagation can take up to 48 hours. SSL will be provisioned automatically after validation.
Custom domains are available starting from the Starter 2 plan.
Platform Protections
Vertra Cloud implements multiple layers of protection to ensure stability, security and service availability.Container Isolation
Each application and database runs in an isolated container with:- Dedicated memory — Hard RAM limits per resource
- Limited CPU — CPU quota proportional to the plan
- Isolated storage — Storage quotas per resource, preventing one from affecting others
Crash Loop Protection
The system detects containers entering restart loops and applies preventive measures:- Intelligent detection — 5 crashes in 10 minutes disables auto-restart for 24 hours
- Exit code filtering — Normal termination (code 0) is not counted
- Cooldown between restarts — Minimum interval of 1 hour between automatic restarts
- Minimum uptime time — The container must be online for at least 60 seconds to count as stable
Automatic SSL/TLS
All website type applications receive SSL certificates automatically:- Automatic certificate provisioning and renewal
- Support for subdomains and custom domains
- HTTP → HTTPS redirection enabled by default
Regional Access Restrictions
Requests to*.vertraweb.app subdomains are blocked from countries under sanctions or regulatory restrictions, and visitors from a short list of other countries must pass a quick browser check first.
Blocked (sanctions or regulatory restrictions):
Browser check (security reasons):
The browser check can only be passed by a person in a browser. API clients, scripts and webhook senders calling your site from one of these countries receive
403 Forbidden. Requests from every other country, including webhooks such as Telegram’s, reach your application normally.Database Certificates
All databases use encrypted connections:- PostgreSQL — Mandatory TLS with client and server certificates
- MongoDB — TLS enabled with platform-signed CA
- Redis — Configurable TLS
- MySQL — Mandatory X509 authentication with auto-generated certificates
Automatic Cleanup (Accounts Without a Plan)
To maintain platform health, projects on an account without an active plan that stay offline for more than 30 days are automatically removed, with a snapshot taken first:- Day 7 — First email notification
- Day 23 — Second warning
- Day 27 — Final warning with reactivation link
- Day 30 — Automatic project deletion
Best Practices
- Set appropriate memory limits to avoid OOM restarts
- Use environment variables for sensitive settings instead of hardcoded
- Configure
.gitignoreto excludenode_modules,venvand temporary files from deployment - Monitor logs regularly to identify errors and bottlenecks
- Use snapshots before making major application changes