None of this was a strategy deck. Each piece exists because the one before it needed it, and the last piece exists because renting compute stopped being defensible.
Client engineering across education, early-stage products and digital delivery. We learned how software actually gets shipped when the budget is real and the deadline is somebody's livelihood.
A campus platform — attendance, groups, library, notes, alumni networks — sold to institutions rather than individuals. It taught us multi-tenancy the hard way: many organisations on one deployment, none of them ever seeing each other's data.
Photographers on one side, studios and clients on the other, with bookings, gear rental and heavy media in between. A different industry that turned out to need the same primitives — two-sided state, transactional integrity, media at volume.
Local commerce done properly: paste a link, photograph a product or scan a barcode, and see real offers from trusted sellers near you. The most ambitious thing we had built, and the one we intended to raise for. That raise has not landed yet.
Three platforms, one bill. Dev environments, preview builds, CI runners and model inference are steady, predictable load — and we were renting all of it by the hour. The bottleneck was no longer application code. It was where the work ran, and it was quietly deciding how fast we were allowed to move.
An open hybrid operating layer that gives every workload a deliberate home across owned hardware and public cloud, without changing how developers ship. We built it to keep Fimyd alive. It turned out to be the most valuable thing we had made.
Four products shipped, two of them still in active development, and the engineering underneath all of them — now offered to teams solving the same problems. The services fund the products. The products keep the services honest — it is difficult to oversell capability you have to live with on Monday morning.
Lyka and Fimyd are live and in active development. LastClass and LenV were built in 2024 and are where the primitives came from.
Hybrid cloud operating layer
Local commerce marketplace
Photography platform
Campus SaaS
Whoever designs your system is on the keyboard building it. Nothing is sold by one team and delivered by another, because the gap between those two teams is where most projects go wrong.
If what you are asking for cannot be built for what you want to spend, we say so in the first conversation. That answer is free and it is usually the useful one.
A system that ships and then cannot be operated is not finished. Deployment path, observability and the 3am failure mode are part of the work, not a phase after it.
Rewrites are occasionally correct and almost always oversold. We separate what is genuinely load-bearing from what is merely old, so you do not pay to replace working code.
We take a limited number of engagements at a time. Growing headcount faster than judgement is how engineering firms become staffing firms, and we would rather not.
You do not need a brief or a requirements document. Tell us what is going wrong and where it started.