Skip to content

Services

What we do, and where you can see us having done it.

  • Web Applications

    React, Angular, Svelte or Laravel — chosen for the project and for the team who will live with it. Server-rendered by default, fast because of how it is built rather than what was bolted on afterwards, and structured so the second year of changes costs about what the first did.

    • React
    • Angular
    • Svelte
    • TanStack Start
    • AnalogJS
    • Laravel
    • Tailwind

  • Mobile Applications

    Apps for iOS and Android — and the same product on desktop when it earns its place. Built cross-platform with Expo and React Native, Flutter, NativeScript or Tauri, sharing the logic underneath rather than rebuilding each platform by hand. Native where native matters, shared everywhere it doesn't.

    • Expo
    • React Native
    • Flutter
    • NativeScript
    • Tauri
    • Rust

  • SaaS Product Development

    Nought to one, with the unglamorous parts done properly. Customer accounts and permissions that hold up under real teams, billing that reconciles, audit trails from day one rather than year two, and an admin panel the business can genuinely run itself from.

    • Multi-tenancy
    • Billing
    • RBAC
    • Postgres
    • MySQL
    • MongoDB
    • Redis

  • Legacy Modernisation & Platform Care

    Inheriting a system that already has users, and moving it forward without taking it down. Framework upgrades across major versions, server and database migrations, performance work on code we did not write, and the ongoing care afterwards. There is rarely a maintenance window long enough to rewrite in, so we do not plan for one.

    • Laravel
    • PHP
    • Version upgrades
    • Server migration
    • Performance
    • MySQL

  • Cloudflare Edge Platform Engineering

    Workers, D1, R2, Queues, and Durable Objects architected as a platform rather than accumulated as a pile of bindings. We write the cost model and the migration path down before the first deploy, because both get expensive precisely when you stop being able to change them.

    • Workers
    • D1
    • R2
    • Queues
    • Durable Objects
    • Workflows
    • Hyperdrive

  • Design Systems & UI Engineering

    Figma to a component library you own outright: design tokens, light and dark themes, every state of every control accounted for, and documentation that keeps its value long after handover.

    • Design tokens
    • Tailwind v4
    • Spartan UI
    • Storybook
    • Figma

  • AI & Agent Engineering

    We build the AI features that still have to work when the demo is over — assistants, search that understands meaning, and integrations that let AI tools operate your product safely. Underneath: MCP servers, retrieval pipelines with real evaluation, and designs that assume the model will sometimes be slow, wrong, or down.

    • MCP
    • RAG
    • Evals
    • Agent tooling
    • Vector search
    • Workers AI