Open source and standards
The foundations are open. We take part in them.
Most of what a regulated engineering estate runs on is open source, and the standards that will govern AI on top of it are being written in the open as well. iTmethods is a member of the bodies where that work happens, operates the open source estate for the institutions it serves, and builds Reign on those open interfaces rather than around them.
Membership is participation. It is not endorsement, and none of these organizations has expressed a view on Reign.
FINOS and the Agentic AI Foundation are Linux Foundation bodies. One lineage, three seats.
Membership
Where we are members.
Three bodies, one reason. The infrastructure underneath governed AI should be readable by the institutions that have to depend on it.
The Linux Foundation
The home of the open infrastructure most enterprise systems already rest on, from the kernel upward. iTmethods is a Silver Member, and the other two memberships sit under it.
How much of your estate traces back to it?
FINOS
The Fintech Open Source Foundation, part of the Linux Foundation, where financial institutions and their suppliers build open standards for AI governance, cloud controls and shared infrastructure. iTmethods is a member.
Whose standard are your controls written against?
Agentic AI Foundation
The Linux Foundation body for open agent standards, including the Model Context Protocol that tool calling is settling on. iTmethods is a Silver Member.
Which protocol do your agents speak today?
The Linux Foundation and FINOS are trademarks of The Linux Foundation. Agentic AI Foundation is a trademark of the Agentic AI Foundation.
Areas of engagement
Four places it changes what we run.
Membership is only interesting where it reaches the work. These are the four places it does.
AI governance standards
The FINOS AI Governance Framework describes the controls institutions are being asked about, in the open, with the institutions in the room. Reign is designed against it, so the record it produces arrives in a shape a reviewer already reads. Alignment is not compliance, and the determination stays with your risk function.
Whose language does your evidence arrive in?
Managed Fluxnova
Fluxnova is the FINOS distribution of the Camunda 7 engine, Apache 2.0 and community maintained. Reign Ops operates it in a single-tenant dedicated instance, and we follow the community that maintains it rather than forking away from it and carrying the difference ourselves.
What happens to your process engine when the project moves?
Open agent standards
Tool calling is settling on the Model Context Protocol, and the Agentic AI Foundation is where that work is governed. Reign Ops runs MCP servers and tool registries on those interfaces, and the model calls behind them cross Reign Gateway like every other one.
Who registered the tools your agents can reach?
Open cloud controls
The FINOS Common Cloud Controls work describes cloud controls in terms several institutions can share, rather than each one writing its own and comparing them later. It is the reference we watch for the deployment options where the environment is the hard part.
Whose control language do your deployments answer in?
Why open matters here
Three properties an institution can test.
None of these is a preference about software licensing. Each one is something your own people can check rather than take on trust.
You can leave
Open interfaces mean the model, the engine and the tool registry can be replaced without replacing the control point above them. Portability is a property you can test rather than a promise in a contract.
What would it take to move off what you run now?
The evidence reads elsewhere
Where controls are designed against published frameworks, the record they produce is in a shape reviewers outside iTmethods already read. Evidence that only makes sense inside one supplier is worth less to the people who have to act on it.
Who has to read your record after you do?
You can see what it is made of
Open source in the estate can be inspected, patched and answered for. When a component changes, the institutions depending on it can read the change rather than wait to be told about it.
Could you list the components you depend on today?
Where this shows up
Where the open-source work is described.
This page states the position. These say what we run, where it runs and what stays yours.
The open source estate
Agents and interfaces
How it is governed
The company behind it
Next step
Discuss our open-source participation.
Bring the parts of your estate that rest on other people's software, and we will tell you which communities we sit in, what we run of theirs today, and where we would not claim more than membership.