Mocana Corporation - Securing Devices, Applications & the Enterprise.
NEWSLETTER  
Newsletter Sign Up contactus



Untitled Document
Sales | Support | Contact | Privacy Policy | FAQs | Site Map | Referral Program
Copyright © 2010 Mocana Corporation
 

Build vs Buy

In general, we're big supporters of the open source movement. But it can be pretty difficult to use open source security tools effectively in constrained device environments. When you're evaluating security solutions for your next embedded device design project, it's important that you understand the Total Cost of Ownership (TCO) of tools like OpenSSL and OpenSSH. Often, you'll discover that licensing a fully-supported professional solution like Mocana's NanoSSH - which has been purpose-built specifically for embedded device environments - is, in the end, less expensive than trying to "shoehorn" OpenSSH into your device. You'll get much better performance out of Mocana's software, too. And for the record – all of Mocana’s security solutions are based on open standards, and are available to you as full source code at no extra charge. You’ll also find that Mocana’s SDKs offer an RFC feature-set depth and breadth that you won’t find anywhere else.

The table below will help you calculate the Total Cost of Ownership incurred by building, porting and/or integrating a typical OpenSSL or OpenSSH implementation. Complete the inputs table with numbers specific to your business, and your results will automatically be calculated in the 'Results' table below. Don't worry about getting your numbers exactly right; make your best guess and you can always adjust the figures later.

Try our numbers, or type in a few of your own:

DESCRIPTION
USING OPEN SOURCE
USING MOCANA
Your cost for one fully-loaded man-year (salary plus benefits)
Your best guess for the time needed to port and integrate the security modules, in weeks. (Typical time needed for OpenSSH in device environments: 5 weeks).
1
Your best guess for the time needed to test and QA the portions of your applications using the security modules. (Typical time needed for OpenSSH in device environments: 3 weeks).
1
Your best guess for time needed, annually, to support, maintain and revise the security portions of your application, in weeks (Typical time for OpenSSH: 8 weeks/year, due to piecemeal updates to opensource codebases that require remapping of all of those updates to your application)
1
Number of security protocols / standards you need to support in your project/product (For example, if you needed to implement SSH and SSL, you’d enter “2” in the box to the right)
1

Submit this form
  Clear Form

Results

DESCRIPTION
RESULT ($)
TOTAL DEVELOPMENT COST of Ownership of Open Source modules over 5-year Product Lifetime
TOTAL DEVELOPMENT COST anticipated by using Mocana's NanoSSH or NanoSSL toolkit: