PlayFab CloudScript and Azure Functions for Unity games
Some game logic should never run on the player's device. I move it to the server with PlayFab CloudScript and Azure Functions, so rewards, validation and third party integrations stay secure and work on every platform, including Unity WebGL. I have shipped this in production for client games and built the same patterns into PlayFab Hub, my PlayFab toolkit on the Unity Asset Store.
What I build on the server
CloudScript handlers
Server side functions your Unity client calls through PlayFab, with clear inputs, outputs and error handling.
Azure Functions for PlayFab
C# Azure Functions registered with PlayFab for logic that needs more than legacy CloudScript, from external APIs to heavier processing.
Secure rewards and validation
Grants, currency changes and match results decided on the server, so a modified client cannot award itself items.
Third party APIs from WebGL
Calls that the browser sandbox blocks, such as social login flows, routed through the server and returned to the game.
Scheduled and event driven tasks
Logic that runs on PlayFab events or on a schedule, such as daily rewards, season resets and cleanup jobs.
Review of existing server code
An audit of current CloudScript or Functions for security holes, wasted calls and error handling, with a written list of fixes.
Typical engagements
One server feature
A single function or flow, scoped and delivered with tests and a short handover note.
Backend hardening
Moving trust sensitive logic off the client before launch or after a cheating problem.
WebGL unblock
Getting a blocked browser feature working by moving the call to the server.
Ongoing support
A monthly arrangement for new server features, monitoring and fixes.
Server side PlayFab work with real clients
Production problems I solved on the server, and the toolkit that grew out of that work.

Twitter login for a Unity WebGL game with PlayFab and Azure Functions
Invision needed PlayFab leaderboards and sign in with both email and Twitter for a Unity WebGL game. Twitter login could not run on the WebGL client side, so I moved it to the server with an Azure serverless function invoked through PlayFab CloudScript.
Read the case study →
PlayFab Hub, a PlayFab toolkit for Unity on the Asset Store
After years of building PlayFab backends for client games, I turned the tools and patterns I use with clients into a product. PlayFab Hub is a Unity package published by my studio, Mind Invaders Games, on the Unity Asset Store in October 2026.
Read the case study →
PlayFab backend for a Unity WebGL game, ready for beta launch
A Unity WebGL game needed a production backend before its beta launch. I integrated PlayFab for email authentication with verification and password reset, analytics on player behaviour, and secure cloud storage of user data.
Read the case study →
Language learning games for a Rutgers University research project
A series of Unity WebGL games for language and education research at Rutgers University in New Jersey, USA. I built the games, integrated PlayFab for accounts, saved data and analytics, and deployed them with Firebase Hosting. The client has come back for repeat projects.
Read the case study →Clear scope, weekly progress
- 01
Scoping call
We go through the game, the current code and what success looks like for you.
- 02
Written plan
You get the scope, milestones and an estimate in writing before any work starts.
- 03
Weekly builds
Progress lands in your repository every week with builds your team can play and test.
- 04
Clean handover
Documented code and a walkthrough, so your team fully owns what was built.
Questions studios ask
Should I use CloudScript or Azure Functions?
Legacy CloudScript is quick for small, self contained logic. Azure Functions suit anything that needs external APIs, more compute or full C#. I will look at what your game needs and recommend the simplest option that holds up.
Can server code fix a feature that does not work in WebGL?
Often yes. For Invision I moved Twitter login, which could not run in the WebGL client, into an Azure function called through PlayFab CloudScript, and it worked in the browser build.
Will this stop players from cheating?
Server side validation removes the easiest cheats, because the client can no longer decide rewards or results on its own. I will tell you honestly which risks remain.
Do you also build the Unity side?
Yes. I am a Unity developer first, so the client calls, UI and error states are covered too.
How do you price this kind of work?
Fixed scope work is quoted per milestone after a short scoping call. Ongoing work is billed monthly. Share your budget range in the form and I will tell you honestly what it can cover.
Where are you based and when are you available?
I am based in Cairo (UTC+2) and work remotely with teams in Europe, the US and the Gulf. My working day overlaps the full European workday and the US East Coast morning, and I reply within one business day.
Need logic you can trust on the server?
Tell me what your game needs to run server side and where it is stuck. I reply within one business day.