The questions people ask before they hire anyone
What things cost, what breaks at scale, and which decisions are expensive to reverse. Written from projects we actually shipped, with the numbers left in. No gated PDFs and no "it depends" as a whole answer.
Game infrastructure
Multiplayer backends, scale limits, and the engine decision.
Game backend: build or buy?
Photon, Nakama, PlayFab or your own. Buy until your logic has to run inside the authoritative loop — that is the line, and it is not a concurrency number.
Read →How much does a multiplayer game backend cost?
A backend for a few hundred concurrent players is a different product from one that holds 50,000, and the price gap is bigger than most studios budget for. What actually drives the number.
Read →Autoscaling game servers on connections, not CPU
A session server at 30% CPU can be full, and CPU gets the scale-down decision actively wrong. KEDA on a per-pod connection gauge, headroom for pod start time, and preStop draining.
Read →Game backend architecture for 50,000 concurrent players
The architecture behind 62 ms median latency and 99.98% uptime at 50,000+ CCU — and the four things that break first on the way there.
Read →Unity or Unreal Engine 5 for a multiplayer game?
The engine decides less about your netcode than you think, and more about your hiring. An honest comparison, including where each one is the wrong choice.
Read →AI products
Cost, architecture, and the decision people get wrong first.
How much does it cost to build an AI SaaS product?
$40,000 to $120,000, and the spread is almost entirely about your data rather than your model. A breakdown of where the money goes.
Read →RAG or fine-tuning: which does your product need?
Almost always RAG, and the exceptions are narrower than the marketing suggests. The test that tells you which one you are looking at.
Read →Web3 in games: what actually belongs on-chain
Ownership belongs on-chain. Gameplay does not. The line between them is where most Web3 game projects lose a year.
Read →SaaS engineering
Written from a product we run ourselves, so the claims point at something you can open.
What building a multi-tenant SaaS actually takes
Tenancy belongs in the schema, conflicts belong in constraints, and compliance belongs in the architecture. The ArendaOS build, decision by decision — including the three that would have been expensive to reverse.
Read →Preventing double bookings in PostgreSQL
The validator cannot be made correct — it is racy even where it is present. The exclusion constraint that can is eight lines of SQL, and three details in it decide whether back-to-back bookings still work.
Read →Have a question none of these answer?
Book a free 30-minute discovery call. We will give you the honest read on scope, cost, and timeline — including when the answer is that you do not need us.
Message received
We’ll review your enquiry and respond within one business day.