Who it's for
For practices, partners, and enterprise teams.
Three shapes of TRIRIGA team. One tool that lifts all three: implementation practices, IBM Services and Business Partners, and enterprise teams running TRIRIGA in-house.
The three shapes
Same constraint, three different business contexts.
TRIRIGA implementation practices
Specialist TRIRIGA practices range from a handful of consultants to global outfits with hundreds of active engagements. The shape changes with scale, the constraint does not: senior SME availability is the binding bottleneck on growth.
Force multiplier on the people you cannot hire fast enough.
IBM Services and IBM Business Partners
TRIRIGA work flows through IBM Services and a global network of IBM Business Partners. Every project burns the same expensive senior architects on the same recurring investigation patterns. Forge formalises those patterns and gives mid-level developers the answers in seconds.
Ships into IBM environments cleanly. Compatible with watsonx Code Assistant via MCP.
Enterprise TRIRIGA teams in-house
Global FM operators, large banks, pharma, public-sector estates, defence, universities. Internal teams running TRIRIGA as the system of record for a few thousand to a few million assets. Onboarding new developers takes 6+ months under the current toolchain.
New starters productive in days, not quarters.
For TRIRIGA implementation practices
Same headcount. More output. Higher margin.
Every TRIRIGA practice has the same shape on its P&L: a small number of senior architects who can do anything, a larger number of mid-level developers who need them constantly, and a backlog of client work that grows faster than you can hire seniors. Forge rewires that ratio.
- Mid-level developers ship work that previously needed a senior. The senior reviews, not produces.
- Onboarding cycle drops from quarters to weeks. New consultants are billable on real client work in their first sprint.
- Investigation work (record diagnostics, workflow tracing, log analysis) collapses from hours to minutes. More change requests through the same team.
- Client deliverables stop waiting on a single senior's calendar. SLAs hold even when the senior is on a flight.
For IBM Services and IBM Business Partners
Built to drop into IBM engagements.
TRIRIGA work routes through IBM Services and a global network of IBM Business Partners. The product is built to fit how those teams actually deliver, not to compete with the ecosystem they sit inside.
watsonx Code Assistant compatible
MCP layer is the standard interface. Plug Forge into watsonx Code Assistant the same way you plug in any MCP source.
Uses TRIRIGA's own auth
No parallel security model, no shadow accounts. Org and geo filtering are honoured. IBM Support is not on the hook for our tooling.
Two JARs, fully reversible
Drop in, drop out. Nothing IBM upgrades will collide with. No database changes, no infrastructure to operate.
Compatible with the IBM roadmap
TRIRIGA Platform 3.x to 5.x today. TAS 11.x today. MREF on MAS 9.1+ in active validation. Same servlet shape across all three.
Forge is an independent product. We are not affiliated with IBM, and we route our co-sell conversations through the partner channel that fits each engagement. If you are an IBM Services lead or BP principal, talk to us.
For enterprise TRIRIGA teams
For global FM operators, banks, pharma, and public-sector estates.
If TRIRIGA is the system of record for your portfolio, the constraint is rarely the platform. It is the queue of one-line questions sitting on the inbox of two senior architects, and the six-month onboarding curve for every new developer who joins the team.
- New developers productive in their first sprint, not their second quarter.
- FM operations and audit teams answer their own TRIRIGA questions instead of opening tickets.
- Sessions, log errors, and orphaned records are visible in one place, not scattered across admin consoles.
- Senior architects spend their week on architecture, not on triage.
Why one tool covers all three
The bottleneck is the same. The product fits all three.
Three shapes, one tool
Implementation practice, IBM Services or BP, internal enterprise team. The product fits all three because the bottleneck is identical: senior SMEs are the constraint, and the pattern of questions is repeatable.
Built into the IBM ecosystem
MCP layer plugs into watsonx Code Assistant, Claude Desktop, VS Code, or any MCP client. Servlet uses TRIRIGA's own auth and security. Nothing parallel, nothing IBM Support has to debug for you.
Globally deployable
Two JAR files, no infrastructure dependencies. Drop into TRIRIGA in any region, any cloud, any on-premise data centre. AI inference can run in the AWS region of your choice or via your own AI client.
Margin and capacity at the same time
Practices: same revenue, fewer hours billed against an SME, higher margin per engagement. Internal teams: same headcount, more change throughput, less backlog.
Want a 30-minute conversation?
We will look at the shape of your TRIRIGA work, the size of your team, and where the senior bottlenecks are. Then we will tell you, honestly, where Forge moves the needle and where it does not.