Branches and edges have no public address, and opening ports per device makes exposure grow linearly.
Solution detail
Edge & Mobile Trusted Access
Krypeo Client connects mobile and remote endpoints to the unified trusted mesh, while EiBox provides a trusted runtime and employee AI entry with isolated identity domains.
Reality
Why this solution
Employees cross identity boundaries: signing out of one system drops another, and tenant cookies bleed together.
Application entry points are personal bookmarks rather than organizational assets, so domain changes require manual edits.
General AI assistants do not know the current system or page, writes cannot be confirmed, and calls cannot be attributed.
Approach
How we solve it
Krypeo Client connects endpoints to the unified trusted mesh while EiBox provides a trusted runtime and employee AI entry.
Intelligent work entry
EiBox is the intelligent enterprise work capsule and AI assistant, bringing applications, identity, and AI into one bounded workspace for employees.
Trusted endpoint access
Krypeo Client connects mobile and remote endpoints to the trusted mesh with multi-account, network awareness, and diagnostics, without opening inbound ports per device.
Isolation and SSO
One domain owns one identity, session, and certificate trust; OIDC and multi-realm Kerberos enable passwordless login, and untrusted hosts enter a quarantined risk domain.
Portal and bounded AI
Krypeo Portal issues per-user install links; the EiBox portal delivers app lists, and AI writes require confirmation with audit.
Outcomes
What changes after rollout
Trusted endpoint access
Mobile and remote endpoints reach the same mesh through Krypeo Client, with no per-device port exposure.
No identity bleed
Identity boundaries stay isolated, so signing out of one app does not affect another.
Entry points as assets
App lists and configuration are delivered centrally; domain changes no longer require manual edits.
Controlled, auditable AI
Writes require confirmation and tool calls are attributable, bringing AI inside the boundary.
Implementation
From assessment to scale
Map boundaries
Identify identity domains, applications, endpoint types, and network conditions; choose the pilot group.
Pilot one domain
Connect one identity domain and a small app set, proving isolation, SSO, and portal delivery.
Expand apps
Onboard more apps and temporary apps by department, tightening permissions and audit.
Multi-domain rollout
Extend to multi-tenant, contractor, and mobile scenarios with standard endpoint delivery.
Fit
Typical scenarios
Components
EiBox + Krypeo + Krypeo Client
Scope and boundaries
Krypeo provides overlay access and does not replace leased lines or SD-WAN. EiBox is not an operating-system sandbox; endpoint security still needs EDR and network policy, and EiBox does not replace the browser, a zero-trust gateway, or a bastion host. It only consumes enterprise IAM.
Next step
Start with one small scenario
Prove value with one site, one system, or one department, then expand as needed.