FAQs

I) How much does it cost?

DNABolt does not publish its list pricing since we are open to negotiating the best value for your organization. It doesn’t make any real sense for us to say, ‘It will cost X amount per user.’ since the scale slides based on volume. DNABolt solutions are built with scalability and large corporate entities in mind. The more customers you have, the less you pay.

Our entry level pricing is based on a minimum 1,000 users so if you are a small startup your initial purchase would cover up to 1,000 users.

DNABolt does not have any ‘per cpu’ charges. You simply pay for the number of users you anticipate and we will monitor the server usage over time. If the number of users is less than anticipated you pay less, if it is more...good for you since your per license cost will decline.

II) What about hidden fees?

All pricing includes access to maintenance and upgrades during the term of the license.

III) How many servers can I use and where can they be located?

If you find you desire extreme availability and want to add 10 virtual servers spread throughout the globe to handle your authentication needs, go for it! DNABolt does not care how many servers you use. The DNABolt server can be hosted anywhere you wish, although it is commonly found behind a corporate firewall. As the authentication module operates over http/https there are no additional ports required than those you probably already have open.

IV) How secure is your product?

Our product has undergone extensive penetration testing. The plugins themselves, as well as all communications between the plugin and server, are encrypted and keyed with session IDs. In some cases items are double or triple encrypted and hashed. Simply put, if you are going to hack a website protected with DNABolt, there are likely easier exploits than attempting such an endeavor. Social engineered viruses for example, would probably take you much farther. Preventing social engineered attacks, however, is beyond the scope of DNABolt. DNABolt relies on the security of the underlying software and website Our mantra at DNABolt is, “Don’t put a steel door on a glass house.” What does that mean? Simply put, if you install DNABolt to harden your access to the system, but leave URL hacking possibilities or if you leave SQL injection vulnerabilities in your site, access to and misuse of data may still be possible. A security audit is recommended if you are serious about obtaining the highest level of security. Security is a product of the functions of all systems and communications involved.

V) What is Bolt for Zimbra and how does it work in comparison to standard DNABolt?

Bolt for Zimbra was developed as a showcase for DNABolt’s technology to demonstrate what can be done with DNABolt’s API and SDK. At DNABolt we often struggle to explain what DNABolt is and Bolt for Zimbra provides one of the best demonstrations of how a company can leverage DNABolt. Bolt for Zimbra reflects what a completed DNABolt deployment can look like. DNABolt itself comes as an SDK with code samples and API that can be used to integrate it into your own systems. DNABolt requires access to the source code for integration which makes products like Zimbra ideal. Products such as OWA (Outlook Web Access) are not suitable for integration as source code is not available.