Skip to main content
A
//COLOPHON

How this site
is built.

We sell engineering, so our own website has to survive inspection. This page documents the stack, the hosting, and the choices — the same write-up a client system gets.

01> cat colophon.json

The stack, on the record.

"framework"Angular 20 · standalone components · signals · zoneless

Server-side rendered, every static route prerendered at build time.

"styling"Tailwind CSS v4 · design tokens in @theme

One gold (#D4AF37), one black, hard edges — the whole system is ~20 tokens.

"motion"motion.dev springs · CSS keyframes

Every page carries its own hand-built decor animation. Nothing is stock, all of it respects prefers-reduced-motion.

"type"Inter · JetBrains Mono

Editorial weight up top, monospace where the site talks like a terminal.

"quality"Vitest unit suite · Playwright e2e

Both gates run before every merge — the same discipline we sell.

"hosting"Self-hosted · Docker · Dokploy

Runs on our own hardware behind our own edge. No one else’s cloud bill, no one else’s outage.

"monitoring"Uptime Kuma · self-hosted

The uptime figures in the footer are read live from it. Type `uptime` in the About terminal.

02> WHY PUBLISH THIS

Dogfood, documented.

Most agency sites are a brochure hosted somewhere the agency has never seen. This one is a production system we operate end to end: we wrote the rendering pipeline, we own the deploy target, and we watch the same monitoring dashboards our clients' systems report to.

If we can't run our own site to that standard, you shouldn't trust us with yours. That's the whole argument. The footer below is live evidence.

altacee --receipts
> rendering · SSR + full prerender
> deploys · docker image, own registry
> monitoring · live in the footer ↓
> source of truth · one git history

Want yours built like this?

Same stack discipline, same operational ownership — pointed at your system instead of ours.