Hosting Options

Pagesmith includes hosting, but you can deploy anywhere that supports static sites or Node.js.

Built-in Hosting

Pagesmith hosting is included:

• Global edge network — Fast worldwide
• Automatic SSL — HTTPS included
• Custom domains — Your domain, our infrastructure
• Instant deploys — Publish in seconds
• Rollbacks — Restore any previous version

For most users, built-in hosting is the best choice.

Self-Hosting Options

Export your project and host elsewhere:

Vercel

Best for: Teams already using Vercel

1. Export project from Pagesmith
2. Push to GitHub
3. Import in Vercel dashboard
4. Deploy with default Astro settings

# Framework: Astro
# Build: npm run build
# Output: dist

Netlify

Best for: Simple static hosting

1. Export project from Pagesmith
2. Push to GitHub
3. Connect repo in Netlify
4. Deploy with:

# netlify.toml
[build]
  command = "npm run build"
  publish = "dist"

Cloudflare Pages

Best for: Edge performance

1. Export project from Pagesmith
2. Push to GitHub
3. Create Pages project
4. Configure:

Build command: npm run build
Output directory: dist

AWS / S3 + CloudFront

Best for: AWS infrastructure

1. Build locally: npm run build
2. Upload dist/ to S3 bucket
3. Configure CloudFront distribution
4. Set up custom domain

Any Static Host

The output is standard static files:

1. Run npm run build
2. Upload contents of dist/ folder
3. Configure for SPA routing if needed

SSR Hosting

If your site uses SSR features (database, server routes):

Cloudflare Workers

Astro has native Cloudflare adapter:

// astro.config.mjs
import cloudflare from '@astrojs/cloudflare';

export default defineConfig({
  adapter: cloudflare(),
});

Vercel Edge

Use the Vercel adapter:

import vercel from '@astrojs/vercel/edge';

export default defineConfig({
  adapter: vercel(),
});

Node.js Server

For traditional Node hosting:

import node from '@astrojs/node';

export default defineConfig({
  adapter: node({ mode: 'standalone' }),
});

Domain Configuration

When self-hosting:

1. Add your domain to the hosting provider
2. Update DNS records:
   • A record → Provider's IP
   • CNAME → Provider's URL
3. Enable SSL (usually automatic)

When to Self-Host

Use built-in hosting when:

• Getting started
• Don't need special infrastructure
• Want simplest setup
• Using database features

Self-host when:

• Corporate infrastructure requirements
• Need specific provider features
• Part of larger deployment pipeline
• Cost optimization at scale

Related Docs

• Export — Download your project
• GitHub Integration — Sync to GitHub
• Custom Domains — Domain setup