Depfu on your premises
When we started Depfu, there were a couple of questions we were getting a lot. One of them was “Do you have an enterprise/on premise solution”.
We have long ignored that topic, because we knew that having to support a version of Depfu that more or less runs completely outside of our control is much more work than just packaging the application up in some fancy docker containers, burn them on a DVD or whatever and hand them over to a surprised admin.
Last year, after a couple of potential clients didn’t stop bugging us, we finally caved in and started to test on premise operation with these clients. After more than half a year of running and adapting we now feel confident enough to announce general availability.
One of the more obvious things we had to improve is fault tolerance. While it is fine to occasionally fix a background job or restart a faulty dependency update on our own servers, we had to make sure that our machinery recovers more gracefully on our clients’ servers, as we can’t reach those servers easily. The other thing was to better support things like private registries which are more common in these enterprise contexts.
What do you get?
But what exactly do you get with Depfu Enterprise?
Depfu Enterprise runs on “your own” infrastructure, behind a firewall if you want to – we never see your code. It runs against your GitLab and GitHub Enterprise servers and only needs an adequate VM or bare metal server to run on. This does obviously include things like AWS EC2, in case you’ve been wondering about the quotes around “your own”.
Depfu Enterprise does support private package repositories for Rubygems and npm packages, which makes it easy for your team to manage internal dependencies more efficiently.
Installing and keeping Depfu Enterprise up-to-date is super easy, and we do releases quite often so that our customers always get the benefits of everything we develop for the SaaS version as well.
Interested? Let us know!
So far, this has been an interesting experience for us. What we like about our enterprise customers is that we get a lot more direct feedback (luckily not only in the form of bug reports) and that it forces us to think a lot more about stability, which has a positive impact on the product as a whole. Additionally, most features we’ve had to build for our enterprise customers also benefit the SaaS customers.