The Tools Behind the Work
Every tool was chosen for a reason. Here is what we build with and why.
The Stack
This is our go-to stack for most projects: the tools we know inside out and reach for by default. Other frameworks and languages are an option when the project calls for it.
SvelteKit
Fast, lean, and built to get the best of both worlds. SvelteKit uses SSR (server-side rendering) for a fast first load and strong Core Web Vitals scores, then the client takes over to navigate subsequent pages as a SPA (single page application). No unnecessary JavaScript, no full page reloads, no compromises between performance and user experience. We use it for public websites, internal tools, and everything in between.
Payload CMS
A headless CMS built by developers, for developers. The entire content schema lives in TypeScript files checked into git. No GUI-only configuration that disappears when you lose access. Content editors get a clean, well-organized admin interface. We get full control over the data model.
Python and FastAPI
When we build automations, data pipelines, or integration backends, Python is the tool. Pragmatic, broad library coverage, and readable a year later. FastAPI adds structure for production APIs without the boilerplate. This powers the work that often runs invisibly: syncing systems, processing webhooks, and replacing manual workflows.
Vercel
For company websites and CMS projects, Vercel handles hosting. Automatic preview deployments on every branch, global edge caching out of the box, and zero infrastructure to configure. It is the right fit for content-driven sites where fast delivery and reliable uptime are what matter.
PostgreSQL
The database behind every project that stores structured data. Reliable, battle-tested, and capable of handling anything from simple content tables to complex relational queries. For applications with higher usage, we run PostgreSQL on a dedicated server alongside PgBouncer for connection pooling, keeping performance predictable under load.