Deploy a static site
Deploy your first static site to Quant and get it live on a global CDN. Choose the path that works best for you:
| Method | Time | GitHub required | Best for |
|---|---|---|---|
| Start from a template | ~2 min | Yes | New projects — get a working site instantly |
| Import from GitHub | ~3 min | Yes | Existing repos — auto-detects your framework |
| Deploy with the CLI | ~5 min | No | Manual control or no GitHub |
| Manual project setup | ~10 min | Optional | Custom CI/CD pipelines |
Start from a template
Section titled “Start from a template”Create a new site from a ready-to-deploy template. Quant creates a GitHub repository, configures the project, and deploys it for you.
- Log into the Quant Dashboard
- Go to Projects → New Project → Start from a template
- Choose a framework (Astro, Next.js, Hugo, Nuxt, Gatsby, Eleventy, and more)
- Connect GitHub if prompted, name your repo, and click Create
- Watch the wizard create your repo, set up secrets, and trigger the first deployment
Your site is live in about 2 minutes. Push changes to your new repo to redeploy automatically.
Import from GitHub
Section titled “Import from GitHub”Already have a static site in a GitHub repository? The import wizard auto-detects your framework and creates a PR with a deployment workflow.
- Go to Projects → New Project → Import from GitHub
- Select your GitHub installation and choose a repository
- Review the auto-detected framework, build command, and output directory
- Click Create — the wizard sets up secrets and opens a PR in your repo
- Merge the PR to trigger your first deployment
Supports Next.js, Nuxt, Gatsby, Hugo, Jekyll, Astro, Eleventy, VitePress, MkDocs, Docusaurus, and Vite.
Deploy with the CLI
Section titled “Deploy with the CLI”Deploy from your terminal without GitHub. Good for quick tests or projects that don’t use Git.
Prerequisites
Section titled “Prerequisites”- Node.js 20 or later installed
- A static site ready to deploy (HTML, CSS, JS files in a folder)
- A free Quant account
Step 1: Create a project
Section titled “Step 1: Create a project”- Log into the Quant Dashboard
- Click New Project in the sidebar
- Select Static as the project type
- Enter a project name (e.g.,
my-website) - Click Create
Note your Organisation ID (shown in the URL) and Project name.
Step 2: Get your API token
Section titled “Step 2: Get your API token”- With your project selected, go to Integrations in the sidebar
- Copy your Project Token — you’ll need this to deploy
Step 3: Install the Quant CLI
Section titled “Step 3: Install the Quant CLI”npm install -g @quantcdn/quant-cliVerify the installation:
quant --versionStep 4: Initialise and deploy
Section titled “Step 4: Initialise and deploy”Navigate to your project folder and run:
quant initYou’ll be prompted for your organisation ID, project name, token, and build output directory. Then deploy:
quant deployYour site is now live at https://your-project.quantcdn.io.
Quick reference
Section titled “Quick reference”# Install CLInpm install -g @quantcdn/quant-cli
# Initialise (interactive)quant init
# Deployquant deploy
# Deploy with revision tracking (faster subsequent deploys)quant deploy --revision-log .quant-revisionManual project setup
Section titled “Manual project setup”For custom CI/CD pipelines or advanced setups, create a project in the dashboard and configure your own GitHub Actions workflow.
- Create a project in the Quant dashboard
- Get your deployment credentials from Integrations
- Set up GitHub secrets manually
- Write a GitHub Actions workflow using the
quantcdn/deploy-action
Next steps
Section titled “Next steps”- Add a custom domain — Use your own domain instead of the preview URL
- Configure WAF — Protect your site from attacks
- Framework guides — Astro, Next.js, and more
- Connecting GitHub — Learn how the GitHub integration works
Troubleshooting
Section titled “Troubleshooting””Command not found: quant”
Section titled “”Command not found: quant””The CLI isn’t in your PATH. Try:
npx @quantcdn/quant-cli --versionOr reinstall with npm install -g @quantcdn/quant-cli.
”Invalid token” error
Section titled “”Invalid token” error”Double-check you copied the full token from the dashboard. Tokens are long strings — make sure you didn’t miss any characters.
Files not appearing on preview domain
Section titled “Files not appearing on preview domain”Allow 30 seconds for changes to propagate. If files still don’t appear, check that your build directory path is correct in quant.json.