Building atomic24.com: a foundry needs a storefront

You’re reading the result of this post. Here’s how the site got built.

A foundry that builds and runs products needs a place that says what it is — to itself as much as to anyone visiting. atomic24.com is that place. We treated it like any other atom: ship the smallest thing that does the job, run it cheaply, iterate.

Static by default

The site is Hugo — a static site generator — built and deployed through GitHub Actions. No database, no server to babysit, no monthly platform bill. A static site is the most “always-on” thing there is: nothing to crash at 3am, near-zero hosting cost, and it loads instantly. For a presence site, anything heavier would be working against the brief.

The site that says “lean, always on” should itself be lean and always on. Anything else is a credibility leak.

The brand, wired into the build

The look isn’t a theme we downloaded — it’s a small custom system:

• Type: Space Grotesk for headlines, Hanken Grotesk for reading, Space Mono for the technical labels and numbers.
• Color: a single confident accent — Reactor Violet (#6A4DF0) — against near-black and off-white.
• Motif: the atom mark, and a quiet grid that runs under the hero and the dark bands.

The content is data-driven: the product types, principles, build process, and the agent fleet all live in small data files, so the copy can change without touching layout. That separation is what makes a copy pass like this one cheap to ship.

Launching lean, on purpose

The honest part: the first build came with seven sample blog posts and a few placeholder numbers. We’re not launching with those. Generic filler undercuts the exact thing the site is trying to earn — credibility. So the blog launches with a small number of real build logs (this is one of them), and every claim on the site has to be one we can stand behind.

That’s the whole philosophy in one decision: a few real things beat a lot of hollow ones. The site practices what it sells.

What’s next

Wire the contact form to a real handler, fill in the founder details, and keep the build log going as the portfolio grows. The site isn’t “done” — atoms don’t get done, they get run. This one’s now running.