The first system we shipped is the one you are reading.
A studio that sells production engineering should hand over something inspectable before asking for trust. This page is the spec sheet of the site itself; everything on it can be verified from your browser.
What this is
A static site, pre-rendered by Astro, served from a CDN. No backend, no database, no cookies, no trackers, no consent banner because there is nothing to consent to. Fonts are self-hosted and subset. The eager JavaScript, everything that loads before you interact, is under fifteen kilobytes compressed: one hand-written interactions module, no framework on the critical path. Measure it in your network tab; the number should hold.
The rocket
The particle field behind the homepage is a three.js scene of up to 130,000 particles that morphs through six formations, one per section: assembled, launchpad, exploded systems, ignition, launch, orbit. It is decorative by contract: the page reads complete with it disabled, and it earns its keep only if it never costs you smoothness.
- It downloads only after your device passes a capability check; phones on Data Saver or weak GPUs never fetch it and get the calm void instead.
- A live frame-rate governor steps quality down before you can feel a stutter: resolution first, then particle count, then the scene retires itself entirely.
- Reduced-motion preferences render a calm still frame; the browser setting is respected everywhere, no toggle needed.
The details a diligence pass checks
- Security headers shipped from the edge; run this domain through a headers scanner and it should hold its own.
- Structured data as one connected graph: organization, founder, services, FAQs, so machines reading this site get the same story humans do.
- A hand-maintained machine brief at /llms.txt and /llms-full.txt for the AI assistants founders increasingly ask first.
- Real 404s, canonical URLs, a sitemap, and print styles on the one-page brief so it travels as PDF.
- Accessible by intent: keyboard navigable, skip link, visible focus, AA contrast over a live WebGL background, which is harder than it sounds.
Why it matters to your project
None of this is the product. It is the residue of how the studio works: budgets respected, failure modes handled, the invisible parts done properly because they are the parts that break at 2am. The systems we build for clients, described on the work page, get this same standard, in a repository you own from the first commit.
Fair questions
Why does an agency site have a colophon?
Because "we ship production systems" is a claim, and this page is the cheapest way to make it checkable. The site is the first system the studio shipped; the standard it is built to is the standard your system gets.
What runs when I visit?
Static HTML from a CDN, three self-hosted font files, and under fifteen kilobytes of compressed JavaScript for the interactions. The WebGL rocket only downloads after your device proves it can afford it. No cookies, no trackers, no consent banner needed.
Can I look at the code?
View source is welcome, and the machine-readable brief at /llms.txt is hand-maintained. If you are the technical friend a founder forwarded this to: the console has a note for you.
This is the standard your system gets.
If the craft here reads like what your operation is missing, the conversation is thirty minutes and costs nothing.
or write to hello@kalpavision.com