<img src="https://secure.leadforensics.com/51024.png" style="display:none;">

Dashworks Enterprise: Many Use Cases — One License To Manage Them All

Juriba Platform local_offer

Many times, after I give a demo, prospects get excited about the many different scenarios they can manage with Dashworks. All of a sudden, ideas come to life. "We could piggyback a hardware refresh onto our Windows 10 migration," or "We could roll out new, AppV-suitable applications while transitioning to VDI."

Then the excitement usually gets dampened by the same questions: "Does that require a different license? How will that change the overall investment?" Many of you are totally surprised to find out that you can manage all the different use case scenarios with one Dashworks license.

Today, I want to walk you through the different licensing options, show you which is best for each scenario, and most importantly, make you aware that you indeed can manage all the different scenarios with just one Dashworks license.


More Licensing Transparency

In the past, we have not spoken much about licensing on our blog or our website because we always felt that it was better to walk you through the sales process and learn more about your project (or projects) before deciding what licensing model was best for your particular situation.

However, I strongly feel that by being transparent about how licenses are calculated, what influences the cost of a seat, and what the particular terms are, prospects and customers can make more informed decisions that take future plans and possible change of scope into consideration — making it a future-proof and scalable investment.

So, to rectify this situation, we created a brand new pricing and licensing page where we take you through the details of our licensing model as well as some frequently asked questions.

The Dashworks Licensing Explained

The Juriba licensing model has to provide maximum flexibility to accommodate the many use case scenarios in which our clients are using Dashworks — without becoming complex. Essentially, to accomplish this we ask our customers three key questions:

  1. How many seats are being migrated across all of your projects? (Our primary license metric is in-scope project seats.)
  2. How long is your project, e.g., 12 months vs. indefinitely?
  3. What type of project or projects will you be using Dashworks for? (I know that initially I said you can manage all use case scenarios with one license and now I am saying that the license depends on what type of project you are planning on managing. Please, just bear with me for a minute.)

Single Modules vs. Enterprise License

Depending on your situation and needs, you can purchase Dashworks as single modules or as an all-in-one license.

The Dashworks modules are:

  • Analysis System (mandatory underlying data warehousing and analysis platform)
  • Project System for Users & Computers (optional)
  • Project System for Mailboxes (optional)
  • Analysis+ (optional)
  • Dashworks Application UAT Manager

For example, if you are using Dashworks only to migrate one-time from a legacy Microsoft Exchange server to an Office 365 environment, you would purchase Dashworks Analysis and Dashworks Project System for Mailboxes as a single module license for the number of mailboxes you are migrating.

However, if you are planning on using Dashworks to first migrate to Windows 10 and also to manage your Office 365 mailbox move, you could either purchase Dashworks Analysis, Dashworks Project System for Users & Computers, and Dashworks Project System for Mailboxes as separate modules — or purchase one enterprise license. Obviously, the latter option is more cost effective.

If you are just planning migrations for users, devices and applications, then you will only need the Dashworks Analysis and Dashworks Project System for Users and Computers license.


Perpetual vs. Fixed-Term License

Juriba offers two licensing options: perpetual or fixed-term. If you have a single, pretty straight-forward project with a fixed scope and timeline that is shorter than 16 months, the fixed-term license is probably your best bet. However, if you are managing a longer project (more than 16 months), multiple projects in parallel, or are transitioning to Evergreen IT / Business-as-Usual (BAU) Management, perpetual licenses will cost you less in the long-run.

No matter what type of license you pick, the investment needed is always calculated on the number of in-scope seats you require, meaning every on-boarded seat counts for one license. That license can be re-used in a different project for the same or the superseded seat, but cannot be re-used for a completely different seat.

To learn more about our licensing, check out our brand-new pricing page or schedule a consultation so we can create a personalized quote for you.

Schedule A Free Consultation