Deployment Overview
Welcome to the Pixelflare deployment guide. This section will walk you through getting your own instance up and running on Cloudflare's infrastructure.
Prerequisites
Before you begin, make sure you have:
- Cloudflare account with a domain added
- GitHub account (for OAuth and optional CI/CD)
- Basic command-line knowledge
- ~30-45 minutes for first-time setup
Deployment Options
Quick Start (Recommended)
The fastest way to get started using Terraform and automated scripts.
Manual Setup
Step-by-step manual configuration if you prefer more control.
GitHub Actions
Automated CI/CD deployment using GitHub Actions.
What Gets Deployed
Your Pixelflare deployment includes:
- API Worker - Hono-based REST API
- Frontend - SvelteKit web application
- Gateway Worker - Single-domain routing (optional)
- R2 Bucket - Object storage for images
- D1 Database - SQLite database at the edge
- KV Namespace - Caching layer
- Cloudflare Access - Authentication (optional)
- DNS Records - Automatic domain configuration
Cost Estimate
Most personal deployments fit entirely within Cloudflare's free tier:
| Service | Free Tier | Typical Usage |
|---|---|---|
| Workers | 100,000 req/day | ~10-50k/day |
| R2 | 10GB storage | ~5-10GB |
| D1 | 5GB storage | <100MB |
| KV | 100,000 reads/day | ~1-5k/day |
| Pages | Unlimited | ✓ |
Next Steps
- Review the Quick Start guide
- Set up your environment variables
- Deploy using Terraform or manually
- Configure optional features