Host a website

Websites are the simplest way to get a site online: pick a stack and a plan, upload your files, and it's live on a free bitqate.pro subdomain. Add your own domain and HTTPS whenever you're ready.

Create the website

1. Go to New deployment and pick Websites.
2. Choose a stack:
   • Static Site: HTML, CSS, JavaScript and images, served by Nginx.
   • PHP App: a PHP application with a built-in web server.
   • Node.js Service: a Node.js app or API.
3. Pick a Plan (Starter, Pro or Ultra) and a Name.
4. Optionally enter a Custom domain. Leave it empty to use only the free bitqate.pro subdomain. You can add domains later.
5. Check the order summary and press and hold Hold to deploy website.

Upload your site

Open the website and go to Files. Upload your files, or create and edit them in the browser. For a static site, the entry page is index.html.

The Overview tab shows the Live URL. Open it to see your site.

Use your own domain

1. On the Domains tab, add your domain (for example www.example.com). The free address is listed there as Auto.
2. At your DNS provider, create a CNAME record pointing your domain to the website's bitqate.pro address shown under Domains.
   • A bare domain (example.com, no www) can't have a normal CNAME. Use your provider's ALIAS/ANAME record or CNAME flattening; Cloudflare does this automatically.
   • On Cloudflare, set the record to DNS only (grey cloud) at least until your certificate is issued.
3. Wait for DNS to update. This usually takes a few minutes but can take longer. Check with dig +short www.example.com.

Turn on HTTPS

On the SSL tab, click Provision certificate. Issuing it takes a couple of minutes, and your domain must already point at the website. If it fails, check the DNS record and try again.

Other tabs

• Nginx: edit the Nginx configuration, for redirects, caching headers, or try_files for single-page apps. Saving reloads Nginx.
• Logs: the website's recent logs.

Single-page apps (React, Vue, Svelte…)

Upload the built output (for example dist/), not the source. If deep links like /settings return 404, add this to the location / block on the Nginx tab:

try_files $uri $uri/ /index.html;