Your recruitment system, your HR system and your policy documents are connected once in the gateway. After that HR asks in its own words, and you have an answer on the AI Act before anyone asks the question.
One account is fine for one person. The difference shows up when a whole team uses AI, and when somebody asks what it cost or where the data went.
Everyone signs up separately. Nobody knows what it costs, who has access, or what has been shared.
One way in to every model. One login, one invoice, and you can see what is actually happening.
Claude today, something else next year. With Walma you use all of them and switch when it suits you, without redoing the work.
We have done the groundwork: ready-made connections to the tools you already use, with proven skills and instructions, so the team actually gets going instead of just trying it out.
If you want visibility, you get it: everything the agent does is visible, you get feedback on how the work could be better, and you can put a stop to things it should not do.
Walma AI Hub is a layer between your tools and the models. Here is what that means in practice.
IT approves an MCP server once. After that the tool appears for the people who should have it, with the right permissions. Nobody on the team touches an API key.
Teamtailorofficial
HiBobbetaClaude, GPT, Gemini and the open models all reach the same connections. You pick the model per task instead of locking yourself in, and if you switch next year the tools come along.
When the off-the-shelf tools run out, we build. RAG over your own material, bespoke agent flows, and narrow MCP servers for systems the vendor has not covered, all running inside the same gateway and the same log.
HR systems are where the MCP landscape moves fastest. We write down which ones have an official server and which ones we build the connection to.
The vendor's own server. Switched on and running the same day.
TeamtailorofficialHiBobbetaCommunity-built. We review the tool descriptions and pin the version before approving.
BambooHRcommunityThese we build ourselves, as narrow read-only servers in your tenant. Tell us which you need first.
Workdayin progress
Deelin progressIncluded in every rollout.
Questions HR already asks, minus the spreadsheet export first.
The gateway runs in your own Azure tenant in an EU region. Every call is logged with user, tool and arguments. That is the answer when your data protection officer asks where the data goes.
Built for European requirements from day one. Details, subprocessors and policies live in our Trust Center.
Open the Trust CenterIt depends entirely on what the AI does. Annex III names AI that ranks candidates, influences promotion or dismissal, or monitors employees as high-risk. HR staff using AI as a working tool, to summarise, draft or search policy documents, is not high-risk. We help you keep the two apart, and our walkthrough of Annex III covers where it is easy to get the classification wrong.
Only what you open up, and only for the people who should see it. Permissions are set per role in the gateway and follow what the HR system already allows. HiBob's server also works through service accounts rather than personal logins, which narrows the reach further.
Teamtailor has an official server, enabled by your Company Admin. HiBob has one in beta for employee data, absence and tasks. BambooHR and Personio have community-built servers that we review before approving. For Workday and Deel we build our own connection inside your tenant.
Then we build one. Usually a narrow, read-only server covering just the fields you need, running in your own tenant, so the AI can answer questions without the whole employee register being exposed.
Yes. Every call is logged with person, tool, arguments and timestamp, and the log can be exported. It is the same record you need the day someone requests their data or an audit comes around.
Twenty minutes with an engineer. We go through your HR systems, what can be connected today, and where the line runs against the AI Act.