An important update on new PowerDNS Products
This is a heads-up on some announcements you will be seeing on powerdns.com relating to new PowerDNS products which (gasp) are not fully Open Source. We know this is a sensitive subject, so before we go live, we want to inform you fully of what we are doing. We’d also like to hear & incorporate your feedback.
The tl;dr: PowerDNS will remain enthusiastically Open Source, but we will be selling a ready-to use ‘Platform’ of PowerDNS Open Source & other technologies, without degrading our current products. For details, please read on.
As you may know, PowerDNS sells support on the core nameserver technologies: PowerDNS Authoritative Server, PowerDNS Recursor and dnsdist. And this is going well, well enough to fund four full-time developers & engineers. This delivers a lot of value to the Open Source world.
Over the past few years, as part of our paid support, we have also been delivering custom PowerDNS configurations based on our open source products. Such configurations integrate with Graphite, Ansible, exabgp, bird, iptables and loads of other products to deliver features like parental control, configuration management, governmental/judicial blacklists, DoS protection of (legacy) nameservers, malware filtering, quarantining, NXDOMAIN redirection, “customer communications”, monitoring, user-experience graphing, audit trail of configuration changes, (management) reporting, webbased control, BGP/OSPF/VRRP failover, ‘production’ DNS64 etc etc.
What we have also found is that many of our users (big hosters, large scale telecommunications service providers) need more from us than “/usr/sbin/pdns_recursor”. Although PowerDNS can easily be integrated with lots of things to deliver powerful functionalities and many of our users still love open source, they would prefer to get it packaged in a more ready to use way.
Putting it more strongly: we have learned that many organizations simply no longer have the time or desire to assemble all the technologies themselves around our Open Source products.
We will therefore be marketing the additional functionalities we have been delivering to our customers as a product tentatively called the “PowerDNS Platform”. I say tentatively because we want to inform you of this news first, even before we have settled on a name and updated our website with the new product.
The “PowerDNS Platform” as we ship it consists of our core unmodified Open Source products, plus loads of other open source technologies, combined with a management shell that is not an Open Source product that we’ll in fact sell.
Now, we understand this may be worrying to some of you. Some formerly truly Open Source products like MySQL are going down a path where you can see their products turning into a sales pitch for the commercially licensed version.
We would therefore like to clarify that we regard our core Open Source products as our crown jewels, jewels which only shine because we are an integral part of the DNS and PowerDNS Communities with whom we work together to create great software. We will continue to make sure that our nameserver software is a viable and hopefully even the best choice for the Internet at large. And in fact, there will not be “two versions” of the PowerDNS nameserver software: of the actual daemons there will be just one version – also because we would otherwise not get the advantages of scale we get from over 150000 deployments!
Simultaneously, we hope that by bringing PowerDNS in a more integrated fashion will enable more companies to benefit from running Open Source & open standards based software. Because this is what deeply believe in – that the future of the world is open, and that software can simultaneously be good Open Source and also work well in a commercial environment.
Thank you for reading this to the end! We would like to hear your feedback and perhaps worries. Please contact me on firstname.lastname@example.org to let us know your thoughts and concerns.
I say go for it, and the best of luck – anything that supports the continuing development of an open PowerDNS can only be a good thing in my book.
Open source software is an incredible value, and I am sure this new product will be as well. This is a reasonable and creative way to fund the on-going delivery of open source, and will contribute to solving real operational problems. There is no reason that ISPs, which are commercial enterprises, cannot pay for commercial software, and certainly no reason why open source developers should abstain from participating in that market.
However, I have to correct your characterization of the BIND subscription edition. The BIND subscription edition is a supported preview of an upcoming open source version. Because our new feature trains are widely-spaced (historically about 30 months apart), some new features are ready for first use long before we issue a new major BIND version. We create and support this preview of upcoming new features as a support service and frankly, our subscribers are helping to refine those features for the rest of our users. We have not created a separate, non-open source version of BIND. We completely agree that having a single core code base is the best strategy.
Hi Vicky, thanks for this clarification. While I did read the page about the BIND Subscription Edition, I apparently did not read it well enough. I have removed the whole paragraph about it, apologies for creating further confusion! It is already hard enough to explain how to make money with open source 🙂
So much of goodness :
1. its very courageous of you to share your future outlook, logic, and articles which are major influencers.
2. I run a startup http://www.karpa.biz, long-time user of open-source and observer of RedHat’s success.
3. I assemble and stitch OSS (PowerDNS as base for my DNS filter) to build my parental filtering solutions. Not sure of how to keep commercially afloat, I charge minimally for finished end-user experience [iNetClean plugin for Chrome and iNetClean for Android].
4. The article you refer “The Money In Open-Source Software” seemed off-the-mark.
More accurate observations come from ‘Simon Phipps’ in “VCs who miss the point of open source shouldn’t fund it” InfoWorld.
“RHEL has no Enterprise-only features. What is in RHEL is in Fedora.”
I know it may seem to make the problem tough, but clarity is important.
“combined with a management shell that is not an Open Source product that we’ll in fact sell.”
Why? Why does this need to be closed up at all. Companies are not turning to your for your ‘shell’. They are turning to you for your expertise in DNS and helping them turnkey their deployment for their needs.
What possible benefit does your paid customers and your open source users get from a ‘closed up management shell’. Why even introduce that when your so pro oss. Just offer a turnkey solution with customizations and support. Let the community help your improve the shell to test features or add features.
Just seems completely backwards when your looking to provide value to your paying customers. If I wanted a closed up shell I can’t depend on in the future I could pick any number of other closed up solutions that have a history of delivering results and a SLA.
I understand your take on things. But I think your estimate of what our users want is at odds with our experience which is both from the world of hosting and the world of access provision. Some more background can be found on https://mailman.powerdns.com/pipermail/pdns-dev/2016-February/001582.html .