Small beginnings, end-to-end builds.
Remiam started in 2014 — a university project between two best friends, building applications for medical research. A decade later it's a UK innovation studio shipping bespoke systems, interactive products, and operational software end-to-end for clients across Europe, the Americas, Asia, and Australia.
How it started.
2014. Two best friends at university, building things off-the-shelf software couldn't reach. The first projects weren't client work — they were research applications. Tools that ran inside breast-cancer studies and personalised-medicine research, written between lectures and exams.
2014 — 2018. Healthcare research stayed as the through-line, but client projects picked up around it. Brand work, web platforms, early mobile apps — first locally, then across the UK, then internationally. The studio operated as a partnership through several rebrands and a steady widening of the practice.
2018. The partnership split. The other half went on to do his own thing; Remiam continued under Liam's direction, keeping the same operating philosophy: small team, in-house, end-to-end.
2018 — now. What started as a research-tool builder now ships across live broadcast, brand installations, hardware integrations, AI tooling, and the studio's own products. The team is bigger and the brief is wider, but the operating philosophy hasn't moved: build things off-the-shelf software can't reach, ship them honestly, keep them running.
Bespoke, end-to-end.
Every system is built for the brief in front of us. Web platforms in Nuxt, Vue, or React. APIs and services in Node, Laravel, or Nitro. Native mobile through NativeScript, Capacitor, or platform SDKs. Data layered across Postgres, MySQL, MongoDB, Redis, or Supabase — whichever fits the shape of the problem.
When the brief reaches off the screen, we bring it into hardware. Raspberry Pi for kiosks and edge compute. Arduino and ESP32 for microcontroller logic. Computer vision pipelines, projection systems, NFC, RFID, sensors — whatever the build needs to read the real world.
The point isn't the stack. Off-the-shelf works when it works; when it doesn't, we design the layer in between. We build and design to make things work.
Four principles, kept honestly.
- 01
Engineered, not assembled.
Every system is built from first principles for the brief in front of us. We pick the stack, write the code, and own the operations — no agency middle layer translating between you and the build.
- 02
End-to-end.
Strategy, design, software, hardware, and ongoing operations under one roof. The studio ships what it scopes; the engineer who designs the system is usually the engineer who ships it.
- 03
Quietly premium.
The work has to read as considered. Type, motion, structure, and silence all carry weight. We treat polish as a deliverable, not a nice-to-have.
- 04
Operational by default.
Every product we ship is designed to run with as little human intervention as possible — and to be debuggable when something inevitably breaks.