MyCena is deployed with high-availability architecture. The platform operates with SLA commitments aligned to enterprise requirements. In the event of a service interruption, a secure offline mode allows access to systems within the configured continuity policy — administrators define which systems are accessible during offline periods and under what conditions.
The continuity architecture is reviewed and agreed during deployment. For environments with specific resilience requirements — critical national infrastructure, healthcare, financial services — enhanced availability configurations are available. These are discussed during the pre-deployment assessment.
No meaningful retraining is required. The employee experience changes in one way: instead of typing a password to access a system, they click to connect. For most employees, this is a simplification rather than a complication — they access more systems with less friction.
A brief onboarding communication — typically one page explaining that the change means they will no longer need to remember or type passwords — is sufficient. The MyCena team provides this communication template as part of deployment. Administrators receive one half-day of platform training. No other training budget is required.
The POV is a two-week deployment on a defined scope — typically 50–200 users across one or two systems. It includes full deployment of the credential generation, injection, and revocation architecture, a live revocation demonstration (one-command, all-systems, timed), audit trail generation and review, and a measurement session at day 9 capturing the operational data (helpdesk tickets, offboarding events, access events) that forms the business case for full deployment.
At the end of two weeks, you have: verified the deployment works in your environment, seen instant revocation demonstrated live, captured the data to build the ROI case, and have timestamped audit evidence of the POV period ready for regulatory or insurer submission. The POV costs nothing beyond a commitment of IT time during deployment.
Two weeks is the standard deployment timeline for organisations with a typical enterprise IT environment. It includes: pre-deployment assessment (systems in scope, protocol mapping, integration points), client software installation across endpoints, credential migration (existing accounts are reprovisioned under MyCena governance — users do not need to take any action), administrator training, and go-live validation.
The two-week timeline is possible because MyCena installs as a software overlay. There are no network changes, no server changes, no Active Directory schema modifications, and no application reconfiguration. The systems employees access are unchanged. The credential generation and injection layer is added above them.
For organisations with a complex legacy estate, or large-scale deployments above 5,000 users, the timeline may extend to three to four weeks. The proof of value (POV) process covers a defined scope in two weeks and demonstrates full functionality before commitment to full deployment.
This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.
Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.
Ce site utilise Google Analytics pour collecter des informations anonymes telles que le nombre de visiteurs du site et les pages les plus populaires.
Garder ce cookie activé nous aide à améliorer notre site Web.