A real manufacturing storefront where every drawing, cut file, and render in the catalog is generated from a single spec file — deployed on GCP infrastructure from the first commit, with no legacy platform to migrate off of.
Bold Coast Metal Fabrication LLC, based in Trescott, Maine, cuts steel truss plates and brackets to order on an xTool 1200W fiber laser. Rather than photographing and hand-writing a product page per size and pitch, the entire catalog is driven by two source files: catalog.json for pricing, checkout links, and shop structure, and geometry.json for each plate's shape — leg lengths, strap widths, hole layouts, timber sizes and pitches.
A Python and Blender pipeline reads that geometry and generates everything a buyer needs to see: dimensioned technical drawings, an installed-assembly rendering, a labeled flat-lay rendering, and a draft DXF cut file — for every plate, in every pitch and size variant. Change a dimension in one file and the whole catalog regenerates, cached by content hash so unchanged renders aren't redone.
The site itself is static HTML/CSS with a little JS, built from Jinja-free Python (stdlib only) — no server runtime to patch or scale, just files regenerated on demand and committed so the output previews without a build step.
Unlike a migration, this storefront never ran anywhere else. It launched straight onto a public GCS bucket behind a global HTTPS load balancer, with a Google-managed TLS certificate and Cloud CDN in front — the same architecture pattern TekMage runs its own site on, in the same tekmage-sites GCP project. The load balancer also handles every domain variant at the edge: boldcoastmetalfab.me redirects to the primary .com, and boldcoastmetalfab.shop redirects straight into /shop/ — all without a line of application code. DNS stays where the client already manages it, in Route 53; Terraform never touches it, so there's nothing to hand over or relearn.
GitHub Actions deploys the site to GCS and invalidates the CDN on every push to main, authenticated entirely through Workload Identity Federation — no service-account JSON keys sitting in repo secrets. Only commits to main of this specific repository can deploy, which is the same no-stored-keys discipline TekMage applies to its own CI.
Standard-size orders check out through Square-hosted payment links, so the site never touches card data directly. Custom and heavy-gauge orders route to a quote request instead, handled by a small Cloud Function that emails the shop over Gmail SMTP — the identical pattern, down to the honeypot and timing checks, that handles TekMage's own contact form.
The site is in soft launch now — taking deposits, with a default ship-by of mid-January 2027 for the first production run. No traffic claims here; this one's early. What's verifiable today is the architecture itself: a small manufacturer with a genuinely generative product catalog, running on infrastructure that didn't need a single migration to get right.