The Challenge
Voodoo is the world's third-largest mobile publisher by downloads, behind only Google and Meta: 7 billion downloads, more than 150 million monthly active users, and a consumer app portfolio that includes BeReal. Behind the games, around 1,200 employees work across studios and business units that each run their own way, and six people in IT serve all of them. At Voodoo, IT also owns the business side of the stack: the SaaS tools, licenses and workspace accounts that most companies leave to infrastructure.
The company had outgrown its tooling. Around ten ticketing tools coexisted, roughly one per department, so getting help meant knowing which door to knock on. A request for GitHub access filed with IT would be bounced to a Slack channel run by another team. Requests filed as "software access" often turned out to be something else: extra credits on a tool, an API key.
Access requests alone run at around fifty a week, and climbing, across a hundred applications with different owners, approval rules and budgets. Every one of them needed a person to read it, route it and act on it. Nothing resolved without IT, and an employee could wait a full working day to get a tool.
"Every department had its own tool. Now everything runs on Siit, and each team keeps its own way of working."
Adil Fartout, IT Manager, Voodoo
Why Siit
The brief was automation first. Voodoo wanted onboarding, offboarding and access to run with as little manual work as possible, across every department, without forcing any of them into a single process.
Siit won on two things. Automation is built into the product: workflows connect to the identity provider, the HRIS and the rest of the stack, so an approval becomes a provisioned account with nobody in between. And the platform is open. APIs, custom API calls inside workflows and an MCP server let the team plug its own tooling in exactly where it wants. When a native feature does not cover a case yet, the team builds the missing piece and keeps going.
That openness fits how Voodoo is organized. The company works like a federation of independent teams, and Siit lets each one run its own inbox and its own rules while IT keeps the full picture. The rollout started with IT, then HR, then legal, infrastructure and Publishing joined with their own queues. Around 70 admins across the company now work in Siit, and adoption needed no internal campaign: new hires meet the service desk in their first-day onboarding video, and the request forms do the rest.
"We didn't pick Siit for ticketing. We picked it for automation."
Adil Fartout, IT Manager, Voodoo
What Changed
App Access is where the change is most visible. Voodoo had already cataloged its approved applications in Siit, each with an owner, so the team synced its Okta groups into roles, cleaned them up and put around a hundred applications behind App Access roles. Each role carries its own approver. Requests from external studios on GitHub are approved automatically. For tools billed back to business units, the unit's budget owner approves access for their own people, with IT out of the loop. The time for an employee to get an app went from eight hours to one.
Employees no longer need to know who handles what. They ask from a form, from Slack or from the Voodoo Shop, an internal app store wired to Siit, and the request finds its owner. Ten ticketing tools are converging on two: one for employees, one for players. For the requests that do not fit a role, a custom API call hands them to an AI Voodoo runs on Claude. It reads the request, provisions standard licenses through Okta and closes them, and sends anything that needs judgment, extra usage or an API key, to the right person. One form and one model absorb the ambiguity that would otherwise take a role for every variant. Close to 1,900 requests now move through Siit every month, carried by more than 6,500 workflow actions, and 35% of them are resolved without IT touching them, up from zero.
The win the team did not plan for came from the MCP. Connected to Siit, Claude reads the week's requests, spots the recurring ones and suggests the automations not yet wired, with a clear view of what Voodoo's environment can and cannot do. For two years, IT had no reliable way to surface that kind of feedback. Now it is one question away.
"Between Siit's integrations and what we plugged in with Claude, most access requests are handled without IT touching them."
Adil Fartout, IT Manager, Voodoo
Voodoo kept every team's way of working and put all of it on one service desk. That is what lets six people in IT decide, app by app, how much of it runs on its own.
