Browser-native 5250 terminal
Your IBM i application. In the browser.
Start with the green-screen application you already use. PristineScreen400 adds managed sign-on, exact profile grants, scoped permissions, and secure browser access without requiring a rewrite or screen template.
- Existing 5250 applications work now
- IBM i credentials stay server-side
- White-labeling and templates are optional
Works today. The existing 5250 application runs without a screen template.
Ready for tomorrow. Apply a template to selected screens while Classic view remains available.
Managed access before the host sign-on
Give each person the right IBM i doorway.
The person entering the browser and the IBM i identity doing the work are managed separately. Users see only their assigned grants. PristineScreen400 resolves the protected host credential and opens the live terminal.
- 01Sign in
Authenticate with an application account from an approved browser.
- 02Choose a grant
Select only from assigned IBM i profiles and approved access.
- 03Start working
Open the existing 5250 application without entering its password.
The daily workspace
The live terminal stays at the center.
Operators work in the existing application while approved IBM i tools and observable activity sit beside it. The browser never receives raw hosts, credentials, connector objects, or an unrestricted system API.
Administration that understands IBM i
Control access around the application, not inside it.
Manage application users, protected IBM i profiles, exact grants, and the capabilities surrounding each terminal. Changes to access revoke affected workspaces without requiring changes to the host application.
- Exact grantsApplication user to IBM i profile
- Protected credentialsEncrypted and retained server-side
- Bounded capabilitiesRisk ceilings, approvals, and resource scopes
- Immediate revocationAccess changes close affected workspaces
Optional presentation
Brand the entry. Modernize only the screens that benefit.
White-labeling and screen templates are independent, opt-in layers. Keep the entire application Classic, apply your brand without changing host screens, or template exact workflows while the RPG program and Db2 state remain authoritative.
Brand Kit
Make the doorway yours.
Apply your product identity without changing the host application or requiring a screen template.
- Product name, logo, and favicon
- Login heading and instructions
- Approved color palette
- Support and legal content
- Assignment to exact user and IBM i grants
NORTHSTAR DISTRIBUTION
ORDER INQUIRY
- Order . . . .
- 10482
- Customer . .
- HARTWELL INDUSTRIAL
- Status . . .
- READY TO POST
- Value . . . .
- $18,420.00
- Lines . . . .
- 03
F3=Exit F5=Refresh F10=Post
#10482
Supported public ingress, private host boundary
Open the right terminal without exposing the system behind it.
The browser reaches PristineScreen400 over HTTPS. IBM i targets, credentials, the live 5250 session, and capability execution remain server-controlled inside the isolated deployment boundary.
Explore the security and public access modelBring the IBM i application you already run
Start with managed Classic access. Add optional layers where they help.
We will connect PristineScreen400 to a reviewed environment, demonstrate the live browser terminal, and evaluate branding or selected screen templates only if they fit your users.
Request a demo