How this site runs
Written by an AI. Claude, Anthropic's AI model, wrote this page,
working with athinktank in Claude Code, from the code that runs the site. Status: the
cost table is estimated from AWS's published prices; last month's real bill appears
below it once the monthly report has run.
Skunk Yard is plain HTML files in a private storage bucket, behind a content delivery network, on its own domain. There's no server and no database. It costs about $0.50 a month to host.
The rules
- No servers. Nothing runs all the time.
- No databases. If an experiment has to store data, it writes files to S3.
- Static first. Pages are HTML, served from storage. Work that can't happen in the browser or at deploy time runs in a short-lived function.
- Free tiers first, and only ones that allow commercial use. The free API catalog came out of this rule.
What happens when you open a page
- DNS. Route 53 answers for
skunkyard.comand points it at CloudFront. - CDN. CloudFront serves the page from an edge location near you,
over HTTP/2 or HTTP/3, on IPv4 or IPv6. A small CloudFront Function turns
/guides/into/guides/index.html, so addresses don't need.html. - Headers. CloudFront adds the security headers to every response, including a Content Security Policy.
- Storage. The files live in a private S3 bucket that only CloudFront can read. A missing page gets the not-found page with a real 404 status.
- In your browser. Search runs here, from a static index. Analytics loads through Tag Manager, with cookies off by default in the EEA, the UK, and Switzerland; see the privacy page.
What happens when a change ships
- Work happens on
dev. Each push runs the checks: lint, tests, the infrastructure tests, and the W3C HTML checker. - A pull request previews the change. A read-only role runs
pulumi previewand comments what would change in AWS. See Preview infrastructure changes in a pull request. - A push to
maindeploys. GitHub Actions checks that the same commit passed ondev, signs in to AWS with short-lived credentials, and runs Pulumi to update the infrastructure. - Then it publishes. It builds the search index, uploads the files, clears the CDN's cache, and tells search engines which pages changed.
Nothing deploys from a laptop, so every change has a log.
What it costs
| Piece | Monthly cost |
|---|---|
| Route 53 hosted zone (DNS) | $0.50 |
| Route 53 queries for the site | Free: they point at CloudFront |
| S3 storage and CloudFront delivery | Cents at this traffic |
| HTTPS certificate (AWS Certificate Manager) | Free |
| Pulumi | Free; its state is a file in S3 |
| GitHub Actions | Free minutes |
| Mail (Purelymail, shared with other domains) | About $0.83 ($10 a year) |
Not counted: the domain's yearly registration.
Last month's AWS bill
Not available yet. On the 3rd of each month, a scheduled AWS Lambda function reads the last month's costs for everything tagged as part of this site, split by experiment, and writes them here. Most experiments are static pages that share the hosting, so only those with their own AWS resources get their own row. The hosted zone isn't in that bill: it was created before the tags, outside Pulumi, so its $0.50 shows only in the table above.
The code
- Start your own: the aws-static-site starter in the open-source repository is the same setup, written for an LLM to follow.
- The walkthrough: An LLM built you a website. Now what? covers it step by step, with the problems hit along the way.
- The pieces: Pulumi, security headers, pull request previews, and search.