Guide series
KitePDF: Architecture & Deployment
Multi-part tour of the KitePDF processing stack—how requests become jobs, where data lives, and how to run it from laptop to AWS.
In progress04 / 08 parts50% publishedUpdated 14 Sept 2026
Series progress04 published · 04 ahead
01 / Part spine
Follow the sequence.
01
Part 01 · beginnerAbout this seriesWho this multi-part guide is for, what you need before you start, and the roadmap from architecture to AWS.10 min · Tarique Anowar02Part 02 · intermediateKitePDF system architectureDesign choices behind KitePDF: trust boundaries, Better Auth with JWT and JWKS, authorization, and the async processing plane.28 min · Tarique Anowar03Part 03 · advancedDeploying on real AWSWhy KitePDF runs on one EC2 host with Compose, how Terraform, SSM, Neon, and GitHub Actions fit together, and what breaks in production. 32 min · Tarique Anowar04Part 04 · advancedHTTPS and the Caddy edgeHow we moved from HTTP on a raw EC2 IP to https://kitepdf.pro—why Caddy replaced nginx for TLS, what changed in CORS and auth URLs, and how the deploy workflow toggles automatic HTTPS.24 min · Tarique Anowar
Part 01 · beginnerAbout this seriesWho this multi-part guide is for, what you need before you start, and the roadmap from architecture to AWS.10 min · Tarique Anowar02Part 02 · intermediateKitePDF system architectureDesign choices behind KitePDF: trust boundaries, Better Auth with JWT and JWKS, authorization, and the async processing plane.28 min · Tarique Anowar03Part 03 · advancedDeploying on real AWSWhy KitePDF runs on one EC2 host with Compose, how Terraform, SSM, Neon, and GitHub Actions fit together, and what breaks in production. 32 min · Tarique Anowar04Part 04 · advancedHTTPS and the Caddy edgeHow we moved from HTTP on a raw EC2 IP to https://kitepdf.pro—why Caddy replaced nginx for TLS, what changed in CORS and auth URLs, and how the deploy workflow toggles automatic HTTPS.24 min · Tarique Anowar