Documentation

Deployment guide

A practical guide to publishing static sites, preparing framework builds, connecting domains, and updating projects on DeployPages.

React deploymentNext.js exportDNS lookupSSL checkMeta generator

Quick start

Deployment means turning local site files into a URL people can open. DeployPages is built for static output, so the first publish can start with a folder instead of a server setup.

Option 1: Drag-and-drop deployment

The fastest path for static projects. If the site is already HTML, CSS, JavaScript, or a finished build folder, you can upload it directly.

Good fit for

Landing pages, personal sites, resumes, prototypes, static documentation, and other browser-native frontend output.
  • 1
    Prepare the project folder

    Your deployable folder should include an index.html file at the root plus any styles, scripts, or image assets the page depends on.

    Example folder structure
    my-site/├── index.html├── styles.css├── script.js└── images/    ├── logo.png    └── hero.jpg

    Common mistake

    If index.html is missing or buried inside a subfolder, the site will not resolve correctly after upload.
  • 2
    Open the upload area

    Use the upload area on DeployPages. You can publish a temporary project first, then sign in later if you want to keep it.

  • 3
    Upload the folder

    Drag the full folder into the upload area or choose it from the file picker. For frameworks, upload the build output folder rather than the source tree.

  • 4
    Open the generated URL

    When the upload completes, DeployPages returns a live URL that you can use immediately for testing or sharing.

Option 2: CLI workflow

Useful when the same build ships repeatedly and deployment belongs in a script, CI job, or release checklist.

Use this when the project has become repeatable

Drag-and-drop is better for one-off previews. A CLI flow makes sense when a team needs the same output folder published the same way every time.

Install the CLI

Use your package manager of choice to install the CLI globally.

npm install -g @deploypages/cli

Authenticate

Run the login command and complete the browser-based authorization step.

deploypages login

Deploy the current folder

Run the deploy command from the build output directory.

deploypages deploy

Framework build guide

Modern frameworks need a build step before upload. The goal is always the same: generate plain static files that the browser can open directly.

What “build” means

A build converts framework source files into deployable HTML, CSS, JavaScript, and assets.

React / Vue / Vite

Command:npm run build
Output:dist/

Upload the dist folder itself, not the project root.

Next.js static export

Command:npm run build
Output:out/

Set output: 'export' in next.config.js before building.

Plain HTML

Command:No build step required
Output:Your existing folder

Just keep index.html at the root.

Hugo / Hexo

Command:hugo or hexo generate
Output:public/

Upload the generated public folder.

Next.js export example

next.config.js
/** @type {import('next').NextConfig} */const nextConfig = {  output: 'export',  images: { unoptimized: true },};
module.exports = nextConfig;

Static export limits

Server-rendered features such as API routes, server-side props, and middleware are not available in a static export build.

Custom domains

DeployPages can attach your own domain after the first deployment so the project can move from a system URL to a branded production address.

What counts as a domain?

Any domain you manage through a registrar can work, as long as you can edit its DNS records.

Step 1: Add the domain in the console

Go to project settings, open the domains tab, and add the hostname you want to connect.

Step 2: Configure DNS

DeployPages will provide the DNS targets you need for ownership verification and traffic routing.

Step 3: Wait for verification

When DNS has propagated, the domain status turns healthy and HTTPS provisioning can complete.

TypeHostValuePurpose
CNAMEwwwcname.deploypages.sitePoint traffic to the platform
TXT_deploypages-challengedeploypages-verify=...Verify domain ownership

Choosing the host record

  • Use www when connecting www.example.com.
  • Use @ when connecting the root domain example.com.
  • Use a subdomain label such as blog when connecting blog.example.com.

Updating a site

Same workflow, new version

Updating a project uses the same logic as the first deployment: build the latest output, upload it, and let the platform replace the live version.
  • 1
    Edit the source files

    Change copy, styles, media, or assets locally.

  • 2
    Rebuild when needed

    If the project uses a framework, generate a fresh build output directory first.

  • 3
    Open the project console

    Go back to the project page in DeployPages.

  • 4
    Upload the new version

    Replace the previous build with the latest folder. Deployment history keeps the newer release traceable.

Once the upload completes, the new build becomes live and the previous versions remain available for rollback.

Frequently asked questions

Can non-developers use DeployPages?
Yes. If the site is already exported as static files, drag-and-drop deployment is enough.
Why am I seeing a 404 after deployment?
The most common reason is a missing or misplaced index.html file. Make sure the deployable entry file sits at the root of the uploaded folder.
What if React or Vue routes break on refresh?
DeployPages supports SPA fallback behavior for common static frontend setups, but the build still needs to be exported correctly.
Can I upload videos or larger assets?
Yes, but performance is better when very large media is optimized or hosted through the right specialized delivery channel.
Can I password-protect a site?
Yes on plans that include password protection. Use it for previews, internal docs, or staged launches.
Go to Explore