Modernize AS/400 without disrupting the systems that run your business
Give IBM i teams one modernization path from browser-based 5250 access and daily operations to RPG/DSPF analysis, governed APIs, code conversion, and OAuth2-secured modern front ends.
How it works
1. Access and operate
Start with browser-based 5250 terminal access, printer and spool integration, managed users, session recording, SQL, jobs, libraries, program calls, and FTP over JT400/DB400.
2. Analyze and plan
Explore RPG and DSPF source, preview maps, import JT400 and DB400 metadata, test Hub assets, and understand what should be exposed, converted, or left in place.
3. Expose and modernize
Turn IBM i programs, DB400 data, and terminal screen flows into governed Hub APIs, convert RPGLE screen and RPC programs to runnable Groovy, and secure new experiences with OAuth2/JWT.
Three modernization challenges, one connected path
Stop stitching point tools together
Unify terminal access, code exploration, RPG analysis, API exposure, data connectivity, and app authentication across the OpenLegacy IBM i portfolio.
Reduce green-screen dependency
Keep live 5250 operations available while replaying screen flows, exposing program and data operations, and giving teams a practical bridge to modern interfaces.
Modernize RPG and DSPF with context
Inventory and analyze source before conversion so teams can move RPGLE screen and RPC programs into testable, runnable Groovy with DB400 access management.
Expose IBM i safely
Publish REST and Hub APIs for programs, DB400 data, ETL, DB Poller, and Screens Flow methods while supporting modern-app authentication against AS/400 security.
Build your AS/400 modernization path
Start where you are: browser access, RPG analysis, API enablement, code conversion, or secure modern front ends.