Technologies
What we build with
A short list, chosen because it covers the work and because engineers can be found who know it. Each page says what we build with the technology, why we choose it, and the patterns we use.
Application
Application
- Next.jsWe build production applications on Next.js, choosing a rendering strategy per route so marketing pages stay static and application screens stay interactive.
- ReactWe build interface layers in React, keeping state where it belongs and rendering dense operational screens that stay responsive with real data volumes.
- TypeScriptWe write TypeScript across the stack so the shape of a record is checked at the boundary and a rename cannot quietly break a screen three modules away.
- Node.jsWe build services, workers and integration adapters on Node.js, where the workload is mostly waiting on other systems and concurrency is the point.
- Vanilla JS and PWAsWe write plain JavaScript where a framework would be overhead: canvas games, embedded widgets, and progressive web apps that must stay small and start instantly.
Data
Data
- PostgreSQLWe design PostgreSQL schemas where the database refuses invalid states, rather than hoping the application remembers to check.
- PrismaWe use Prisma where a typed schema and a managed migration history earn their place, and drop to SQL where the query is the interesting part.
- SupabaseWe build on Supabase where a managed PostgreSQL with authentication, storage and realtime removes weeks of undifferentiated work.
- NeonWe use Neon where serverless PostgreSQL with branching fits: preview environments with their own data, and workloads that idle between bursts.
AI and automation
AI and automation
- Groq and LLM IntegrationWe integrate language models through Groq where inference speed changes what the interface can do, with typed tools, grounded retrieval and measured evaluation.
- n8nWe build and host n8n workflows for cross system automation, with retries, run history and controls, and we say when code would be the better answer.
- ResendWe send transactional email through Resend, with authenticated domains, typed templates, idempotent sending and delivery events written back to the record.
Cloud and commerce
Cloud and commerce
- VercelWe deploy Next.js applications to Vercel in accounts you own, with preview environments per change, edge delivery and a one step rollback.
- RailwayWe deploy long running services, workers and databases on Railway where a process needs to stay alive rather than start per request.
- WordPressWe build and integrate WordPress where the editing experience matters, often headless with a separately rendered front end for speed and control.
- WooCommerceWe extend and integrate WooCommerce stores, and build headless front ends over them where speed and checkout control matter.
- StripeWe integrate Stripe for one off payments, subscriptions and marketplace payouts, keeping card data out of your systems and orders driven by verified webhooks.
- PrintfulWe integrate print on demand fulfilment so an order placed in your store becomes a submitted job with tracking, without anyone touching a spreadsheet.
Let’s talk about the system you need.
Tell us where the current process breaks down. We can map the workflow, examine the integration requirements and define a practical scope for the build.
- A mutual NDA is signed before project details are shared.
- Scope is fixed in writing before any build starts.
- You own the source code, the IP and the documentation at delivery.
- Support plans are available and tailored on a discovery or technical call.