The right stack for each build
KAMRS is a content-heavy B2B site whose job is to rank and convert, so it's built with Astro and served as
static HTML — fast, fully indexable, and nothing to keep patched on a server.
BatteryCompany and SamToolkit run on the .NET/Blazor stack we use for most client work, and both ended up on opposite hosting
models for reasons specific to what they needed — BatteryCompany on Blazor Server for a catalogue-heavy
storefront that benefits from server-rendered pages, SamToolkit on Blazor WebAssembly because its entire premise
depends on nothing being sent to a server. Same tools, different tradeoffs, chosen deliberately rather than by
default — more on how that reasoning plays out on the services page.
Why only a few
We don't publish every project we've touched — a lot of client work is internal tooling or maintenance on
systems we didn't design from scratch, which doesn't make for much of a case study. What's here is work we built
end to end and can talk about honestly: what the actual problem was, what we chose to build, and why.
Between them, they cover most of what we actually do — a B2B website built to win search traffic and
enquiries, a real e-commerce build under real operational constraints, and a product shipped with no client at
all, built purely because we wanted it to exist. As that list grows, so will this page.
