LastClass
A campus platform covering attendance, groups, library, notes and alumni networking — one deployment serving many institutions that must never see each other's data.
Every claim on this site is backed by something in here. These are not case studies written after the fact — they are products we designed, built, shipped and still operate, with our own money on the line.
An open hybrid operating layer that gives every workload a deliberate home across owned hardware and public cloud, without changing how developers ship.
Explore Lyka ↗Dev environments, preview builds, CI runners and model inference are steady, predictable load. Renting all of it by the hour meant our own iteration speed was being priced rather than engineered — and that is before data residency rules push a workload somewhere specific.
The usual answer is to pick a side: all public cloud and accept the bill, or run your own metal and accept a worse developer experience. Lyka exists because that trade should not be necessary.
Fimyd runs on it in production. When we talk about cloud cost, hybrid placement or private AI in an engagement, we are describing something we operate daily rather than something we read about.
Shop from trusted local sellers near you. Paste a link, photograph a product or scan a barcode, then compare real offers from sellers who actually have it.
Visit Fimyd ↗Local sellers hold real stock and cannot be found online. Buyers search a national marketplace, wait for delivery, and never learn the shop two streets away had it today. The gap is not supply — it is discovery.
Closing it means resolving a product from whatever a person happens to have: a link, a photo, a barcode. That turns a shopping app into a matching problem.
Fimyd is the reason Lyka exists. It is also the proof that we can take a consumer product with real transactional weight from nothing to production — and keep it running while building the infrastructure underneath it.
Visit Fimyd ↗
Two platforms built in 2024. We are not selling them today, and we are not going to dress them up as current products. They belong here because the engineering they forced is the engineering we now do for other people.
A campus platform covering attendance, groups, library, notes and alumni networking — one deployment serving many institutions that must never see each other's data.
Photography end to end — booking photographers, renting gear, portfolios and client hubs, with a heavy media pipeline carrying all of it.
Most engineering firms ask you to trust a list of clients whose systems you will never see. We would rather hand you the software and let you form your own view.
Open Lyka and read the architecture. Open Fimyd and try to find something near you. If the work does not hold up, no case study we wrote about it would have either.
That is what we build when the customer is us. What we build for other teams is on the Solutions page.
See what we do for other teams ↗The team that built everything on this page is the team you would work with. There is nobody in between.