Menu
Log in

A home for your website.

Start with a simple website

Add your business, services and contact details in your workspace to create a private preview. No website files or code are needed. Edit your details, review the result, then choose hosting and connect your domain when you’re ready.

Create a website

Hosting for a new Benchlight design

Hosting for a website rebuilt by Benchlight is free for the first 60 days, then $9 a month or $99 a year. Start it from your workspace when you approve the website. You add one record at your domain (a CNAME for www), and we serve the website, keep it secure and check it every day. Your email is not touched.

Bring a website you already have

Connect GitHub to choose your website files. For supported npm/Vite browser websites, Benchlight can build the files for you. You can also check a Netlify site’s connected GitHub files or upload a built website ZIP.

For an eligible browser website you bring, Benchlight hosting starts with a 60-day free trial. A payment card is required to start; after that, hosting costs $9 a month or $99 a year. You do not pay the $249 rebuild price for files you bring. Domain registration is separate.

Review the private preview first. Publishing, hosting plans and domain connection are separate steps, shown in your dashboard before your current hosting changes.

Applications, databases, WordPress and stores need their working services transferred too. Add your website to see its transfer requirements; these are not universal one-click imports yet.

Keep your websites in view

Your dashboard brings together website status, connected activity, domains, orders and billing. Monitor alerts appear for websites with active monitoring.

Bring my website Open my dashboard

Or host it yourself

These guides are for people who choose to install their purchased website files themselves. Back up your existing site and DNS, then test on a temporary address before switching your domain.

Preserve email MX, SPF, DKIM and DMARC records. A website upload does not require changing email services.

Cloudflare Pages

  1. Open Workers & Pages, then Create application, Pages and Direct Upload.
  2. Name the project and upload the ZIP or extracted folder.
  3. Test the pages.dev address, including a controlled real form or booking test.
  4. Add your domain through the project's Custom domains. A root domain requires Cloudflare DNS; a subdomain may use a CNAME.
  5. Keep the prior deployment for rollback. Direct Upload projects cannot switch to Git integration without a new project.

Official upload guide · Domain guide

Netlify

  1. Extract the ZIP into a folder containing index.html.
  2. Use manual deployment and drag the folder into Netlify's deploy area.
  3. Test the netlify.app preview.
  4. Add your domain through Domain management and apply the displayed website DNS records, preserving email records.
  5. Keep the old deploy for rollback.

Official deployment guide

Vercel

  1. Extract the ZIP.
  2. Deploy that folder through Vercel's CLI, or put it in your own Git repository and import the repository.
  3. For static files, choose Other as framework, no build command and the folder containing index.html as output.
  4. Test the deployment URL, then add your domain in project settings and follow the displayed DNS steps.
  5. Retain the old deployment and DNS values for rollback.

Official deployment guide

cPanel, SFTP and standard web hosting

  1. Back up the current document root, redirects and server configuration.
  2. Upload the extracted files to a staging folder or subdomain first.
  3. Test all pages and contact functions. Static files do not replace a server-side form handler.
  4. Place the tested files in the document root, retaining the old files outside the public folder.
  5. Restore the backup if anything fails after switching.

WordPress, Wix, Squarespace and other builders

A static ZIP generally cannot replace a builder theme directly. Ask us to assess separate static hosting on your domain or scope a builder-native version before buying. Form and booking preservation must be resolved first.

Before you switch

Check business facts, images and prices; every page at phone and desktop sizes; real forms, bookings, phone and email links; HTTPS, redirects and email DNS. Keep the prior deployment and DNS values. Restore them if an important function fails.