AJAEXPlatform

Products for IBM TRIRIGA

AI-powered developer tools and operational intelligence for IBM TRIRIGA.

Our TRIRIGA tools now have their own home at tririgatools.com. Forge connects your TRIRIGA to any AI assistant, so your team can understand it, build in it, and change it safely in plain language. TRIRIGA Insights watches your environments so problems surface before your users do.

IBM TRIRIGA is powerful, and painfully hard to see into and change. AJAEX closes that gap with two products: Forge, an AI-native assistant that connects the whole platform to any MCP client so you can understand it, author real configuration, and change it safely in plain language; and AJAEX IBM TRIRIGA Insights, which monitors your environments so problems surface before your users do.

A thin component runs inside your existing TRIRIGA and exposes only narrow platform primitives; the intelligence lives in a managed cloud gateway, so new capabilities reach every environment without shipping new code onto your servers. Forge works across IBM Db2, Oracle, and Microsoft SQL Server. The full detail, pricing, and a live demo request live at tririgatools.com.

See it work

Ask in plain language. It runs the tools and answers.

Point any MCP client at a TRIRIGA instance and ask. Forge composes the read calls, traces the model, and returns a grounded answer, with no SQL and no clicking through five separate builders.

MCP session
forge
What breaks if I change the triCost field on triPurchaseOrder?
> forge.model.whereUsed({ field: 'triCost', bo: 'triPurchaseOrder' })
> forge.impact.analyze('triPurchaseOrder.triCost')

14 references across 3 subsystems. Two are high risk:

  • triPOApprovalRouting branches on triCost thresholds (over 25k routes to a senior approver). Change the field type and the comparison breaks.
  • 3 active reports aggregate on triCost; a rename orphans their columns.
  • 2 Web API mappings expose triCost outbound; downstream systems still expect the current name.

Everything else is display-only and safe. Full risk-ranked list attached, before you touch the field.

Representative MCP session. Tool names and outputs are illustrative.

Why teams trust AJAEX

Lightweight, native, reversible.

Read-first by design

Over 80% of the tools are read-only. Every write is off by default and needs an explicit, per-environment admin grant.

Signed and audited

Every request into your TRIRIGA is cryptographically signed and rejected if it isn't, and every action lands in a searchable audit trail.

Any database, one answer

One dialect-aware layer runs unchanged on IBM Db2, Oracle, and Microsoft SQL Server, so the same question returns the same answer.

Native and reversible

It runs inside your existing TRIRIGA as a thin component, with the platform's own security applied to everything it reads. Remove it and restart, and it's gone.

Ready to see it on your TRIRIGA?

Watch Forge orient itself in an unfamiliar environment, trace the blast radius of a real change, and author a working workflow, live and in plain language. Everything about the tools, including pricing, lives at tririgatools.com.