Compatibility before implementation
Know the technical boundary before planning deployment.
Use these current specifications to decide whether a representative IBM i workflow belongs in a compatibility review. IBM i release, application behavior, certificates, networking, and capacity are confirmed for the environment before work begins.
Direct answer
What should a technical buyer confirm first?
Confirm that the representative workflow uses compatible 24 by 80 5250 presentation, that a private network path reaches the IBM i target, that certificate-validated TLS services are available, and that the required concurrency, printer, SSO, and management-tool needs fit the reviewed deployment.
Current facts
Product and deployment specification.
| Terminal presentation | Interactive 24 by 80 5250 screen with protected/editable fields, keyboard state, screen sequencing, and browser zoom. Current validation does not include 27 by 132 presentation or printer emulation. |
|---|---|
| Terminal input | Printable single-line input, bounded paste, field navigation, Enter, Field Exit, F1 through F24, Page Up, Page Down, Help, and Reset. Input is serialized and stale-screen-aware. |
| Browser identity | Dedicated PristineScreen400 email and password account. The current identity model does not provide SSO or magic links. |
| IBM i identities | Administrator-managed profiles with encrypted server-side passwords and exact grants to application users. Stored password values are not redisplayed. |
| Public application access | Supported customer access terminates over HTTPS at reviewed PristineScreen400 ingress. IBM i targets, credentials, terminal connections, and capability execution remain behind the application boundary. |
| IBM i transport | Allow-listed private target with certificate and endpoint validation. TN5250 normally uses TLS port 992; secure IBM i host services normally use ports 9470 through 9476. Plaintext services are unsupported. |
| Deployment isolation | One operator-managed customer deployment, database, Brand Kit, and active configured IBM i target. The browser cannot select a host or deployment. |
| Current validation capacity | The current reviewed prototype profile validates up to four concurrent workspaces. Commercial sizing is confirmed during deployment review rather than inferred from this prototype limit. |
| Management panels | System, Jobs, Messages, Spooled Output, IFS, Db2, Objects, Data Queue, registered workflows, Security, and Activity, subject to deployment and grant policy. |
| Capability controls | Compiled allow-list, deployment risk ceiling, exact grant assignment, approvals, resource scopes, typed requests, bounded results, timeouts, and sanitized activity. |
| Brand Kit | Approved text, HTTPS support link, bounded color tokens, and sanitized same-origin PNG logo and favicon. No custom HTML, CSS, JavaScript, SVG, remote image, or external font fields. |
| Presentation Profiles | Six terminal theme presets and up to 50 deterministic screen recipes per profile. Draft, publish, rollback, import/export, default, and exact grant assignment workflows include Classic fallback. |
| Browser API boundary | No browser-selected host, port, TLS mode, IBM i user name, password, arbitrary command, arbitrary SQL, JTOpen object, connector object, or public MCP endpoint. |
| Commercial terms | Managed deployment, implementation, customization, support, and access are quoted after technical review. No public fixed pricing or universal compatibility claim is published. |
Compatibility review
Bring evidence from the workflow, not credentials.
Useful review inputs
- IBM i release and application ownership context
- Representative redacted 24 by 80 screens and required keys
- Expected users and concurrent workspaces
- Private network and certificate deployment model
- Required tools, scopes, approvals, branding, and templates
Never send in a demo request
- IBM i or application passwords
- Credential-encryption keys
- Trust-store passwords or private keys
- Unredacted customer or production data
- Live database or configuration files
Frequently asked questions
Requirements to confirm
Which IBM i releases are supported?
A universal public release matrix is not claimed. Compatibility depends on the target services, certificates, 5250 behavior, and requested capabilities, so the specific environment is reviewed before deployment.
Is public browser access supported?
Yes. The product is sold with supported public HTTPS ingress to the PristineScreen400 application while IBM i connectivity and credentials remain controlled behind it.
Is pricing per user?
No fixed public pricing model is claimed. Deployment, implementation, concurrency, support, branding, and template requirements are reviewed for a custom managed-service quote.
Turn facts into a fit decision
Confirm fit before planning implementation.
A technical review turns these general specifications into an environment-specific deployment decision.
Start a compatibility review