Case Studies

Case studies with the numbers left in

Eight projects, four published under their real names. Metacritic 63 on Switch, 650,000 downloads on a crossplay VR shooter, 52,000 concurrent players at 62 ms, $2.4M in first-month marketplace volume, 87% less manual processing — each with the constraint it was built against and the measurement it was judged by.

A town square in King’s Bounty II: guards, market stalls and a lit portal under heavy foliage
A first-person view of an X8 match: heroes trading fire across an orange-and-white arena under an evening sky
Three Metarun heroes racing down a lamplit street, each ringed by a speed trail
The ArendaOS dashboard: cars on rent, fleet utilisation, customer debt, and today's returns, overdue payments and service due

The four named projects. Screenshots from the games’ own store listings: King’s Bounty II — 1C Entertainment / Prime Matter (Nintendo eShop); X8 — Thirdverse (Steam); Metarun — Encore Games (Google Play). ArendaOS is our own product, rendered from its live markup.

Featured case studies

Eight examples of the kind of delivery work Yarvixo handles. Four are named — King's Bounty II, a retail console game you can buy today; X8, a free VR shooter live on three storefronts; Metarun, a client game named with permission; and ArendaOS, our own product. The other four are anonymised: three are client work, and one describes three local businesses of our own, unnamed by choice. X8 is the one where the storefronts credit the publisher rather than us, and its own page opens by saying so.

A town square in King’s Bounty II: guards, market stalls and a lit portal under heavy foliage
Nintendo eShop screenshot. 1C Entertainment / Prime Matter.

King's Bounty II — Nintendo Switch Port

A named retail console title, on sale in the eShop: a 7 GB Unreal Engine 4 open world moved onto a 4 GB handheld, from 6–8 fps to a 30 fps target, shipped day and date with PC, PS4 and Xbox One.

GameConsole portNamed
Read case study →
A first-person view of an X8 match: heroes trading fire across an orange-and-white arena under an evening sky
Steam screenshot. X8 — Thirdverse.

X8 — 5v5 Crossplay VR Hero Shooter

A named client game, free on Steam, Meta Quest and Pico: every engineering system in an Unreal Engine 5 5v5 VR shooter where a standalone headset and a GTX 1080 share one match. Four engineers, eighteen months — the design, art and rendering were the client's.

GameVRUnreal Engine 5Named
Read case study →
Three Metarun heroes racing down a lamplit street, each ringed by a speed trail
Google Play screenshot. Metarun — Encore Games.

Metarun — 1v1v1 Web3 Mobile Runner

A named client game, live on Google Play: server-authoritative 1v1v1 races, MMR matchmaking, anti-cheat and hero ownership on BNB Chain, peaking at 39,000 concurrent players at 60 ms.

GameWeb3Named
Read case study →
The ArendaOS dashboard: cars on rent, fleet utilisation, customer debt, and today's returns, overdue payments and service due
Our own product, rendered from its live markup.

ArendaOS — Fleet Rental SaaS

Our own product, live at arendaos.com: a multi-tenant B2B subscription system for car-rental fleets, with booking conflicts blocked in the database.

SaaSMulti-tenantNamed
Read case study →

Enterprise AI Analytics Platform

An AI SaaS platform for a logistics operation: 14 data sources, 5 languages, custom RAG workflows and ERP integration. Manual processing fell 87%, at 99.2% extraction accuracy measured by a harness built to measure it.

AI SaaSRAGERP Integration
Read case study →

AI Automation for Three Local Businesses

Our own electronics buyback, device repair service and car tuning workshop: leads into a CRM and Telegram, article drafts from a local model, analytics AI agents can only read, and a person on every publish. No names and no figures, by choice.

AI automationAI agentsLocal LLM
Read case study →

Decentralized NFT Marketplace

A Polygon marketplace for a gaming studio: gas-optimised contracts, real-time indexing, and $2.4M in first-month trading volume.

Web3PolygonMarketplace
Read case study →

Multiplayer Game Backend

An authoritative backend in Go: 52,000 peak concurrent players at 62 ms average round-trip and 99.98% uptime, with matchmaking, autoscaling and live ops.

GameDevGoKubernetes
Read case study →

What each case study covers

Useful context for founders, CTOs, and product leaders evaluating delivery partners.

Project context

The client situation, technical constraints, and the specific business problem that had to be solved first.

Delivery approach

The implementation path, architecture decisions, and how the team reduced risk while shipping on a deadline.

Measured outcome

The metrics that mattered after launch - efficiency gains, speed, platform reliability, and product traction.

Need a team that can ship something similar?

Bring your product brief or technical scope. We will review it, identify the main delivery risks, and propose a practical plan.

  1. 1 business dayWe review your enquiry and reply.
  2. 48 hoursAfter the call: a written scope, with a fixed price against it.

Message received

We’ll review your enquiry and respond within one business day.

Related services