It's not easy to give a clear reply to this as it depends on multiple factors:
What we can confirm is that beyond some low infrastructure costs, integration costs (whether internal or from third parties that provide IT services) and potential communication costs to the general public and users, there should be no additional costs (for example, no additional personnel should be required to manage the solution)
As a quick way to obtain an estimate of the required integration effort, we recommend analyzing the available example, since it not only lets you understand the API in a few minutes, but also provides up to 20 tokens for free which should be more than adequate for any proof of concept implementation.
The only requirement is that the user has a smartphone (Apple or Android) available in order to run the app that will handle the tokens.
The enrollment process offers multiple variants in order to be as simple as possible and adaptable to the specific needs of both the organization and its users.
Yes. To ensure maximum flexibility for different use cases, there are several alternatives for the app that can be used.
If the organization already has an application for its users, we recommend integrating the ZofToken SDK into this application, thereby minimizing friction with the users and leveraging any previous adoption efforts and costs.
Simply contact us. You can also start testing ZofToken by using ZaaS for free.
ZofToken's security and development teams are constantly analyzing any reports of vulnerabilities for components in which the solution is based, as well as looking for new features that allow for even greater flexibility and adaptation to specific use cases.
This is the main reason why ZofToken is offered as a subscription model, thereby ensuring that every client always has immediate access to the latest available version.
Each time a new version of ZofToken Server is released, all clients receive a both a communication and guidelines regarding what changes were made, their impact and if there is any need to implement the new version as soon as possible (however, given that all central security functions are based on proven and robust technologies, we do not expect to have to release "urgent" updates).
In parallel to any updates to the core solution, ZofToken's team releases optional components (usually in the form of open source public repositories) to make it easier to integrate ZofToken with other existing tools or processes.
Since any app can implement ZofToken SDK, your organization can distribute a ZofToken implementation in any language you prefer.
That being said, the main components of the solution (logs and internal messages in ZofToken Server, the user interface of ZaaS, ZofToken Universal App and the technical integration documents) are currently available in English and Spanish.