Static
Static site hosting
Send the files, point MAIN at index.html and publish: the application answers on the port declared in PORT, on a vertraweb.app subdomain with a certificate issued by the platform. There is no runtime to version.
Who designed HTML
Tim Berners-Lee, at CERN, proposed a hypertext system in 1989 and by 1990 had the first browser and the first server. Public HTML appears in 1991: documents linked by URL, the server only delivers the file. Håkon Wium Lie proposed style sheets in 1994; with Bert Bos at the W3C, CSS 1 became a recommendation in 1996. Content in one file, appearance in another — the browser interprets both.
Tim Berners-Lee
Paul Clarke · CC BY-SA 4.0
Håkon Wium Lie
Franco Folini · CC BY-SA 2.0
Bert Bos
Martin Alvarez Espinar · CC BY 2.0
Hypertext, not a program
Berners-Lee’s web is document linked to document by URL. There is no application process: the page is the file the server delivers.
Structure on one side, form on the other
HTML describes what the page is. CSS, Lie and Bos’s thesis, describes how it looks. That split is what makes the static web different from a binary that paints the screen.
The browser does the work
The server only sends text. What assembles the page is the client — the opposite of PHP, which generates HTML on the server, and the opposite of a compiled app.
What the platform does for a static site
The essentials come configured on every static application here; the features that depend on your plan are flagged in the card.
No version to choose
There is no versioned runtime here: the content is HTML, CSS and JavaScript served as it is. vertracloud.config only keeps MAIN, PORT, MEMORY and, if the plan allows it, SUBDOMAIN — the VERSION key does not apply.
Subdomain with automatic TLS
Once published, the application answers on vertraweb.app with a certificate issued and renewed by the platform, and HTTP traffic is redirected to HTTPS. The exposed port is the one declared in PORT.
Your own domain by CNAME
From the Intermediary plan on, point a CNAME record at the address shown in the dashboard. SSL is provisioned after DNS validation. It is 1 custom domain per application.
Deploy by zip or GitHub
Send a package of up to 100 MB through the dashboard or connect a repository, private ones included. Updating the site means deploying again, and the dashboard terminal shows the process from start to end.
What people publish as a static site
Finished content: the files reach the server exactly as they left your machine.
Landing and company pages
A product, event or company page, with an address of its own and HTTPS from the very first deploy.
Documentation and portfolios
Content that changes little and has to stay up: a manual, a changelog, a portfolio. Each update is a new upload.
The output of a generator
If the site is already generated on your machine, send the output folder: the files are served as they are, with no compilation step on the server.
A front-end next to your API
Deploy the site and the API as separate applications in the same account: each one has its own container, its own subdomain and its own RAM ceiling.
The whole configuration
vertracloud.config is an optional INI file at the root of the project. MAIN points at the entry file; PORT=80 exposes the site; MEMORY sets the RAM ceiling; SUBDOMAIN picks the address name, from the Scale plan on.
NAME=meu-site
MAIN=index.html
PORT=80
MEMORY=512
SUBDOMAIN=meu-siteA plan for every stage of the project
Memory and storage change with the plan; the language does not. Compare what each plan unlocks and pick the one that fits the project today.
Compare plansAlso runs here
Same platform, same deploy, a different stack.
Frequently asked questions about static sites
Publishing, domains and certificates: what gets asked about static sites.
Do I have to choose a runtime version?
No. Static sites have no versioning on the platform: it is HTML, CSS and JavaScript. The VERSION key in vertracloud.config does not apply — what matters is MAIN pointing at the entry file and PORT declaring the exposed port.
What does it take for the site to be reachable?
Publishing the application. Web publishing is available from the Pro plan on and requires 512 MB of allocated RAM — with less than that the call is refused. Choosing the subdomain name requires the Scale plan; below it the platform draws a name for you.
Can I use my own domain?
Yes, from the Intermediary plan on: set a CNAME pointing at the address shown in the dashboard and SSL arrives automatically after DNS validation. Each application accepts 1 custom domain.
What happens if I unpublish the site?
The container is recreated with no exposed port and the application restarts. The subdomain is released right away — there is no reservation, and somebody else can register it later. The custom domain is removed as well.
Do I have to take care of the SSL certificate?
No. Every published site gets an automatic certificate, renewed before expiration, with HTTP to HTTPS redirection on by default. Custom domains also get automatic SSL.
Publish your site today
Create the account, send the files in a zip or connect the GitHub repository, and publish it to get the subdomain with TLS.
Create account