What we build with.

Our default for anything on the web. Pages render on the server, so search engines and link previews see real content rather than an empty shell.

Every interface we build is React underneath — including the one project that predates Next.js in our stack.

Strict mode, on every project that allows it. A whole class of mistake is caught while writing the code instead of by a customer.

Where our Next.js sites deploy. Every change gets its own preview link before it goes anywhere near the live site.

Styling written alongside the markup and driven by design tokens, so a colour or spacing change is made once and lands everywhere.

Accessible building blocks we copy into the project and restyle to the brand — owned by the project, not rented from a library.

Restrained motion that explains what changed — and switches itself off for anyone whose device asks for reduced motion.

For heavier, timeline-driven sequences that Framer Motion is not built for.

Behind the NCA Staff Portal, where a dense, familiar internal interface mattered more than a bespoke one.

Served from our own domain rather than Google's, so a page never waits on a third party to show its text.

Database, sign-in, file storage and server functions in one place. Our default backend, locked down with security rules from day one.

Checks every piece of data at the door — a form submission, an API response — so bad input is stopped before it is stored.

A small, predictable store for what the interface needs to remember — filters, open panels, progress through a form.

Sortable, filterable tables for admin screens that hold a lot of rows, and data fetching that caches sensibly.

Keeps public endpoints from being hammered — each visitor gets a fair allowance and no more.

Taking payments through a provider built for it, rather than handling card details ourselves.

The editor course authors write in on the NCA LMS — formatted content, without anyone touching code.

Reordering lessons and content blocks in the NCA LMS course builder by dragging them into place.

Press Ctrl+K, type what you want, go there. For platforms with more screens than a menu can hold.

Articles written in plain text that can still embed live components — a chart or a demo inside the prose.

The editor from VS Code, running in the browser, for tools where people read or write code.

Interactive maps — on Nobility Care's site, showing the areas the service covers.

Clear, responsive charts for dashboards and statistics pages.

When no chart library has the shape we need — tournament brackets and standings built from the data up.

Real-time 3D in the browser, used where depth adds something rather than as decoration.

Fast automated tests for the logic underneath the interface.

Drives a real browser — to test a site end to end, or to automate work that would otherwise be clicked through by hand.

What we reach for first, across the range — Haiku, Sonnet, Opus and Fable, each for a different size of task. Knowing which one a job needs is most of the skill.

The second option, for work that does not need Claude or when it is not available.

Runs models on our own hardware — for work where the material should never leave the building.

The other local runtime, which most of the language models in The Lab run on.

Node-based image pipelines. Every image in The Lab came out of one — with the workflow kept, so a set can be extended later and still match.