Question 1

Does JoN require an agent on every JBoss instance?

Accepted Answer

No. JoN's core management uses JBoss-native management APIs and does not require an intrusive agent on each node.

Question 2

Can JoN run fully air-gapped?

Accepted Answer

Yes. JoN supports fully air-gapped on-premise deployments, which is the default for most regulated banking customers.

Question 3

Which JBoss versions are supported?

Accepted Answer

Red Hat JBoss EAP 6, 7, and 8, and equivalent WildFly releases. JoN explicitly supports heterogeneous fleets with mixed versions.

Question 4

Is JoN a replacement for our APM tool?

Accepted Answer

JoN focuses on JBoss platform operations, configuration governance, and JBoss-specific intelligence. It complements general-purpose APM tools but replaces JBoss-specific tooling such as legacy JON / RHQ.

Question 5

How quickly can we see value?

Accepted Answer

Most customers complete a proof-of-concept deployment within 30 days, including AD/MFA integration and the first set of dashboards.

Question 6

Who builds JoN?

Accepted Answer

JoN is built by Metisoft Labs (https://metisoft.in), an enterprise infrastructure software company focused on banking and BFSI customers in APAC and the Middle East.

Question 7

Does JoN help with regulatory compliance for banks?

Accepted Answer

Yes. JoN generates evidence-grade reports for SSL certificates, configuration drift, access, and change history, aligned with RBI, MAS, SAMA, and PCI-DSS audit requirements.

Question 8

How does JoN reduce JBoss incident time?

Accepted Answer

JoN's AI-powered RCA correlates GC, heap, thread, and log signals across the fleet, helping BFSI teams cut mean time to resolution on JBoss incidents by up to 70 percent.

Proven on Mission-Critical BFSI Stacks

Slashing JBoss incident response time across 200+ instances

Consolidating three monitoring tools into one unified dashboard

Preventing production incidents with configuration drift detection