My Serverless Portfolio Website is Live

Spent a weekend putting my portfolio website into production on a fully serverless stack. AWS Lambda, API Gateway, S3, CloudFront. No servers to manage, no EC2 instances to patch, no monthly bill surprises from idle compute.

The whole thing costs almost nothing to run. Lambda charges per request, and a personal portfolio doesn't exactly get millions of hits. Most months the bill rounds down to zero. That was the appeal — build it once, deploy it, and forget about infrastructure.

The trade-off is cold starts. First visit after a period of inactivity takes a noticeable beat longer. For a portfolio site that's fine. For a production API, you'd want to think harder about provisioned concurrency. But for this use case, serverless is close to the perfect fit.