Approved text fields
Configure product labels, sign-in guidance, support information, footer content, and legal copy rendered as text.
Customer-specific presentation
Put your brand around the IBM i application you already deliver.
Each isolated PristineScreen400 deployment can define a controlled Brand Kit for sign-in, navigation, support, legal copy, logos, and approved colors. Branding works with an entirely Classic terminal or alongside optional screen templates.
Direct answer
What can a white-label IBM i portal change?
PristineScreen400 can change the product name, short name, tagline, login instructions, support and legal text, logo, favicon, and a bounded color palette for one isolated deployment. It does not let a browser or administrator alter the IBM i target, credential policy, connector behavior, or authorization boundary.
Product evidence
A branded entry before the managed host session.
The customer sees the approved application identity. IBM i credentials and target controls stay server-managed.
Controlled customization
Enough flexibility to establish identity without creating an extension platform.
Sanitized PNG files
Logo and favicon uploads are decoded, dimension-checked, re-encoded, stripped of metadata, and served from the same origin.
Bounded color tokens
Apply reviewed accent, header, page, panel, text, muted-text, and line colors with accessibility review.
Frequently asked questions
Brand Kit boundaries to confirm
Can branding add custom HTML, JavaScript, CSS, SVG, or remote fonts?
No. The Brand Kit is a closed configuration of approved text, hexadecimal colors, and sanitized same-origin PNG assets.
Does white-labeling require modernized host screens?
No. Branding and screen templates are independent. A deployment can keep every IBM i screen in Classic view.
Can different customers share one target selector?
No. The commercial model uses isolated customer deployments. The browser cannot choose an IBM i target.
Bring your identity requirements
Review your product identity and IBM i workflow together.
A branded-deployment discussion covers the browser entry, user grants, private host boundary, and any selected presentation profiles.
Discuss a branded deployment