Web applications. Software for messy data with real consequences.

Arqé creative platform interface
Arqé
IOScomps commercial property exchange
Client Story
"Micky took our design brief and built it out end-to-end, paying real attention to the details that usually slip — accessibility, compliance, performance. The process was calm, the iterations fast, and what we shipped held up under real users."
Ena.Supply
Product Team
how I work

I build the architecture underneath, not just the screens on top. One person across the whole stack, so nothing is lost in the handover.

From the schema up to the screens people use.

Arqé creative platform interface
Architecture and build
The whole application, from the schema up. You work directly with the person writing it, so the data model and the interface are decided together rather than handed between teams.
Talk it through
DC Atlas, a data-centre intelligence platform
Pipelines and integrations
Most of the work in a data product is getting the data usable and keeping it that way. Ingest from APIs, exports and databases, then cleaning, reconciliation and scheduled refreshes.
Talk it through
IOScomps commercial property exchange
Accounts, billing and access
The parts that turn a build into a product people pay for: authentication, permissions, team accounts, subscriptions and payments.
Talk it through
Internal tooling built for the Harcourts real-estate network
Deployment and upkeep
Shipping it and keeping it standing without a platform team behind it: deployment, monitoring, and maintenance you can hand to someone else later.
Talk it through
Every project follows the same path. Scope first, data second, and nothing built before both are understood.
01
Scope
What the product has to do, who uses it, and what it has to integrate with. We agree on it before anything is built.
02
Data review
A real sample of the data, and an honest read on the state of it. The work underneath is visible before it is quoted.
03
Build
Architecture and interface built together, in working increments you can use. Something real early, refined from there.
04
Handover
Deployment, documentation and monitoring that runs without me. You own the product.
The stack. Picked per project, for the data and the budget.
Front end
  • TypeScript
    Across the whole stack, so the data model has one shape end to end.
  • React and Astro
    React for application screens, Astro for fast content sites.
Backend and data
  • Supabase and Postgres
    Database, auth, row-level security and APIs.
  • Cloudflare D1
    SQLite at the edge, for lighter data that sits close to the user.
Hosting
  • Cloudflare Workers
    APIs and server logic at the edge, with no servers to run.
  • DigitalOcean
    Servers for long-running jobs, pipelines and anything that needs a box.
Work with me

Start the conversation

Send the project, a link to anything already built,
and a sample of the data if you have one.

Have a map in mind?