Since its first release, the stand-alone version of Gallery Server Pro has been licensed under the GNU General Public License and available at no charge. Over the years I have had requests for a commercial license that frees you from the restrictions of the GPL and, for some companies, its stigma.
At the same time, the donation model I’ve been using has not been generating enough revenue to pay the bills, forcing me to accept short-term contracts to fill the gap. I don’t really mind that much, but it slows down the progress of Gallery Server Pro. My head is filled with cool ideas and I never seem to get caught up. I would love to spend more time fulfilling all the feature requests you send me.
As a result, version 3.0 will be released in several variants, as seen in the chart below.
| GPL
FREE | GPL Professional
$49 | Enterprise
$249 $149 Sale! | |
|---|---|---|---|
| Unlimited file types |  | | |
| Unlimited albums and media files | | | |
| SQL CE support | | | |
| Source code available | | | |
| Includes future 3.0.X releases | | | |
| Gallery Server Pro logo hidden | - | | |
| Commercial license | - | - | |
| SQL Server 2005/2008/2012/Express (up to 20x faster than SQL CE) | - | - | |
| SQL Azure support | - | - | |
| Sample PayPal and Facebook templates | - | - | |
| Guaranteed forum support | - | - | |
The free GPL version you know and love lives on, with full functionality supporting unlimited file types and number of media files using the SQL CE database.
The GPL Professional edition is the same as the free GPL version, except it comes with a special product key that hides the Gallery Server Pro logo in the footer of the page.
The Enterprise edition uses a commercial license and adds support for SQL Server and includes several bonus features such as SQL Azure support, sample PayPal and Facebook UI templates, and a guaranteed response in the forum. It is regularly priced at $249 but for a limited time I’m knocking $100 off.
The DotNetNuke module is not listed because it won’t be available until at least Entity Framework 6 is released. (It requires the multiple contexts per database feature being introduced in that version.)
These changes give you the flexibility you’ve been asking for while providing enough revenue to allow me to introduce features at a faster pace. It should be a win-win situation for all of us.
2 comments:
Congratulation on this ambitious release. What is your best guess on the timeline for the DNN version?
I address the DNN timeline in this post.
Post a Comment