May04

SKU Changes for VistaDB Products

As some of you may have already noticed, we have changed the SKUs for VistaDB Products based upon customer feedback and requests.

Here is the major case for the change in SKUs from users:  I want more choice in what I buy and when, and I want to be able to add more developers after the initial purchase cheaper than buying Pro licenses.

Simpler – VistaDB Developer License

Every Developer using VistaDB to compile needs a VistaDB Developer License.  This license includes all of the following items, and is now the baseline SKU for purchase.  This is it, there is no other type of Developer License.  A site license uses the same engine as this license, just has more activations.

All Developer Licenses Include

  • VistaDB 4 Embedded Database engine with royalty free runtime
  • Runtime targets: .Net 2.0 SP1, .Net 3.0, .Net 3.5, .Net 3.5 SP1, .Net 4.0, Mono 2.6 or higher Supported
  • Entity Framework Provider
  • Visual Studio 2008 / 2010 Support (Standard or higher)
  • Up to 8 KB Pagesize
  • Single Assembly for 32 and 64 bit deployment on any supported runtime
  • Samples
    • TODO Application 3 tier application using WCF Service on server side, and WPF, Asp.net, and Silverlight Presentation Layers
    • Help Search FTS – Asp.net website allowing search of FTS indexes
    • TicketSystem – Asp.net website for simple ticket tracking with embedded database in App_Data
    • Timesheet – Asp.net website for simple timesheet entry application
    • RSS Aggregator – Winform System tray application for pulling RSS feeds.  Demonstrates how to build a complete DAL using only  ADO.Net Provider Factories
    • Entity Framework
      • Databinding
      • CRUD Operations
    • Simple Samples
      • DDL Commands
      • DataSets
      • DataRows
      • Databinding
      • ConnectionStringBuilder
      • Cascading updates and deletes
      • Basic operations
    • Error box – Shows how to trap database errors and display extended error information to the user
  • Nunit Tests – NUnit solution in Visual Studio 2008 for Nunit 2.5
  • Asp.net membership providers (binary only)
  • Customer Experience Improvement Program – System Tray application that sends us feedback on engine use, errors, etc.  This is an opt-in only application as a part of the setup, may still be turned off later from the system tray.

Tools on the machine for local developer use (not redistributable)

  • VistaDB Data Builder
  • VistaDB Data Migration Wizard

What’s not included?

Maintenance and support are not included.

What about Maintenance Subscriptions?

You will note that there is no longer a maintenance subscription, or upgrade assurance available for Developer Licenses.  We have tested that revenue model and found that the majority of developers didn’t renew, and didn’t see the value in having a subscription.  It is too complicated to track for only a small portion of the customer base, so it has been discontinued.

If you purchase VistaDB 4.0, you will get all 4.0 builds.  Minor releases (VistaDB 4.1, 4.2) will be an upgrade fee in the 25% range.  When 5.0 comes it will be a new release upgrade fee, which we have not determined yet.  Customers from previous major versions (like 3.x users) will be able to upgrade to 4.0 for a new release upgrade fee shortly.

Cost Savings to Small Companies

The cost savings for a typical small business can be quite significant.  A company that does not want the Add ons can buy 5 developers for about 45% of the cost compared to the old SKU structure.  We also offer Professional Bundles with more than one Developer at a package price, the Add ons are the same, but with more Developer Licenses.

Add on Paks

Add on Paks are items that only have to be purchased once per Account.  For example if you have four developers, you must purchase four Developer Licenses, but only require one Data Migration Wizard Pak in order to get the source and distribution rights to the VistaDB Data Migration Wizard.

If you would like to get all the Add on Paks, and Developer Licenses together we offer a Professional Bundle that includes all of them for a discounted price as a package. 

Bundles

There is a VistaDB Comparison Matrix available showing graphically the differences in the following bundle editions.

Consulting Services

Yes, we do offer consulting services for database projects.  We offer a Database Design Review, and Custom Consulting Agreements.

Existing Customers

So, what about existing customers?  Everyone who has a current subscription will continue to be honored, but it will not be allowed to renew.  The following paths show where an existing SKU will be upgraded later this week as a part of the deployment of this system.

Machine License Changes

In addition we are rolling out a machine license change along with this system.  All Developer Licenses are still entitled to install on two machines with machine credentials.  But now we will automatically reclaim machines six months after installation.  The idea is that six months after installation if a machine crashes or is lost and you need to reinstall it should not be a big deal.  Any more frequently than that will require a support ticket for us to process them manually.

Licenses will be reclaimed automatically by the system after they are 6 months old.  The license is still valid, but will require a refresh in order to validate it is still valid for the Account.  The Account Manager has not been updated to display these reclaimed licenses yet (soon).

Discussions

05/05/2010 03:44 #

Sean Kearon

Can I ask what the build server licences are for?  I am a single developer with a Pro licence and currently my build machine is my dev machine.  Do I need a different licence if I move my build to another machine (but retain sole use of that machine)?

Sean Kearon United Kingdom

05/05/2010 10:46 #

js_vistadb

Build Licenses are ONLY for dedicated build server machines.  This is not for desktop use.

If you compile using a local only type of build server then you don't need one.  But if you have a stand alone build server (like TFS), or a Build server that runs builds for multiple users (like TFS Build again).  It allows anyone to submit builds to the server.  That is why the build license is so expensive.   Anyone can build against one of these servers.  

js_vistadb United States

05/05/2010 03:06 #

Sean Kearon

Thanks Jason.  I've also just read your article at www.vistadb.net/.../vistadb-build-license.aspx.  

As a developer, if I have access to TFS or another server that can use to build a product against a VistaDB, then I surely have a VistaDB licence to allow me to code and compile locally?  So, making me pay another $1,000 to be able to produce my builds on a separate machine seems like a high price to me. I'm not sure this is right...

Sean Kearon United Kingdom

05/05/2010 09:30 #

js_vistadb

Sorry, a VistaDB Developer License is for non concurrent desktop use.  It is not a Machine or Site license.  TFS and other build servers allow ANYONE to submit build jobs.  So you have to possess a Machine license to use a Build Server.

If you have 250 developers submitting jobs to that build server we still only get that one time fee.  A Build License is for the Build Server MACHINE - not the per developer license, not the for each user, it is machine wide.  That is why it is as high as it is.

We have customers who bought 4.x desktop licenses and installed them to Build Servers to circumvent our per developer licensing.  Then they can just buy one Developer License and use the "second" install for the build machine and everyone else can submit build jobs to it for free.  That will not be tolerated, sorry.  

We provide an incredible value for the amount we charge, there are NO runtime fees for VistaDB.  If you install 100 SQL Servers you pay 100x the price.  With us you pay nothing extra.  

We don't think asking for Build Server licenses is out of line with the rest of the industry either.  Look at Preemptive and their Dotfuscator.  A developer license and a build license are WAY different in pricing.  Once again, because anyone can submit a job to a build server and use it.  That is not the intent of build servers, but that is what I see a lot of businesses doing these days.

See the Add on - Build License page on the VistaDB site for information about the Build License.

js_vistadb United States

06/05/2010 03:05 #

Uwe

I personally prefered the subscription. This was a few which I was able to plan in my finances. The risk now is, that some people will may overjump some releases.

Uwe Germany

06/05/2010 04:37 #

Sean Kearon

@Jason - yes, I understand what you say there about environments with a large number of developers.  But how does this work as a single developer if/when I take on another developer to work with me?  Am I really forced to spend the $1,000 spend for a shared build machine in this scenario?

Also, you do provide excellent value for money and the product is absolutely great - I love using VistaDB.  I have also looked at Dotfuscator's pricing - they don't even publish their prices - shame on them!  I use the rather excellent Crypto Obfuscator from LogicNP Software (http://www.ssware.com/cryptoobfuscator/order.htm), which is a great tool with great value for money (and their licensing tool is totally excellent also!).  AFAIK, to license a build machine I just buy another licence, job done!

Sean Kearon United Kingdom

06/05/2010 11:03 #

js_vistadb

Two users don't NEED a build server.  Typically you don't need a build machine until you get to having teams of people.  If you submit a job to a TFS Build Server it doesn't run as you, in fact it could run on anyones machine who installed the Build Service.  You could have it running on two dozen machines.  Most commercial software will not allow that, and it is not covered under a desktop license meant for non concurrent use.

25 Developers - 25 Developer License - 1 Build License for the build server ($40/user for build server)

2 Developers - 2 Developer Licenses - 1 Build License for the build server ($500/user for build server)

If you are one of those who installed TFS locally on your own machine and check in and out locally (you can do it).  Then you can submit your build job to your own machine.  That will work.  But when you start running on other machines, they need to be licensed.  Server licenses are different than developer licenses.

@Uwe - Yes, I personally like subscriptions.  But 96% of users were skipping versions ANYWAY.  They were waiting until 1 year or more after their subscription lapsed, and then they want to "renew" their subscription.  That was never the intent.  So if people are going to skip anyway it breaks the who model.  I will do a follow up blog about Revenue Models.  Subscriptions under work when people use them, otherwise they end up costing you a lot of money.

js_vistadb United States

06/05/2010 11:32 #

Sean Kearon

Jason, could you please consider finding a route for smaller teams to be able to use a build server licence?  This would make it more accessible for teams with say 5 or less developers using something like Team City or Final Builder.  Even MS is now targeting smaller teams with TFS.

BTW: it seems my previous post has not been published - did I contravened posting guidelines?

Sean Kearon United Kingdom

06/05/2010 12:08 #

js_vistadb

We currently do not have any plans to offer a Machine level license at a cheaper price.  We are investing if TFS can provide information about which developer submitted the job, and then we could verify that developer has a license before allowing it.  That would allow us to control who gets to use the build server, but it would different than a Build License for the machine.  It would be something added onto a Developer License to enable TFS Build to work.

Posts don't always go up immediately - sometimes they wait for moderation for some reason (system flags them).  I get around to them and approve them in time.

Yes, Microsoft is targeting smaller teams with TFS.  $500 for a small team license that would let everyone use it for RCS, Workitem tracking, and Build Services.  Microsoft also has a market cap of several billion dollars.  We can't compete with them on price or we would be giving away our product too and charging millions a year for Gold Partnerships and Volume License Agreements.  Sorry, doesn't work that way at the small business level.

js_vistadb United States

07/05/2010 06:54 #

David Shannon

Up to now I've just been renewing my license each year to stay current.  But now it appears that the Developer License will cost the same for me as it does for someone who has never purchased VistaDB.  Is that how it will work?  No discount for current license holders, and thus no real penalty for letting one's license lapse?

If so, that could work out well for me.  I'll probably just stop where I am as far as purchasing goes and keep working with the version I have, then only buy a new license if something really appealing comes out, or if I hit a show-stopper.

But I want to make sure that is how it is going to work before I adopt that strategy.  Can you let me know for sure?  Thanks...

David Shannon United States

08/05/2010 01:13 #

Jason Short

I wouldn't say no difference.  If you have a license you will get a major discount (40-50%) for stepping up.  If you let it lapse over a year, then you will be a new user again and have to buy all over.  That is how a LARGE percentage of people do it right now.  They let it lapse, wait until they hit a major issue or until we finally have something they want.  I don't think most users actually track our releases anyway.  They wait until they are starting a new project and then go look for a new release.

I wish more people had kept them current, it was the better revenue model and release model for us.  We didn't worry so much about minor / major / etc.  It was all technical decisions.  Now we have to make the business issues a little larger as a part of that process.  I will probably have to do a large blog post about revenue models and products to explain it better.

Jason Short United States

08/05/2010 11:47 #

David Shannon

Sounds good.  I didn't see anything indicating the 40%-50% discount for current license holders but I may have missed it.  As that's the case, then continuing to update would probably make sense, as it has in the past.  

Is there a post on that discount somewhere, or will that be announced later?  No hurry on my part, my license is good until November.

David Shannon United States

Discussions are closed