Likelihood to Recommend If you have your own in-house servers or have a cloud server with the freedom to configure any PaaS that you want, then Dokku is for you. So far, I have never run into a scenario where Dokku was not able to fit my needs, after deploying many different types of applications with varying frameworks, languages, and connected services. If you already have a PaaS available, however, Dokku may not be for you.
Read full review Clearly, the [IBM Cloud Managed Istio] tool is very useful when you have multiple services and each service is connecting with other services through APIs in different networks. To manage this type of complex network, [IBM Cloud Managed Istio] is very useful. It comes with a license that can increase the billing of your project so make sure if your application network mesh, monitoring cannot be managed on your own then you can use it. If your application is not very complex then you have many tools available like Grafana, Prometheus, Sumo Logic, which you can integrate individually with your cluster and implement. In this type of scenario, it is better to not use [IBM Cloud Managed Istio] and it will serve your purpose as well.
Read full review Pros Dockerfile deployments are an incredibly simple and straightforward way to spin up applications. The docker-options plugin allows endless direct configuration of options passed to different docker lifecycle stages. Read full review Layers transparently onto existing applications Allows control of access and rules to be developed Creates metrics for usage Read full review Cons Dokku might overreach on its assumptions about how you want to host your app, using its own VHOSTS plugin by default. This may be a pro or a con depending on what you want. Proxy port configuration can be somewhat difficult, with Dokku resetting any pre-deployment configuration to "smart" defaults on the first deployment. Read full review Some more functionalities added could improve it better. Better technical user guidance. Read full review Support Rating Dokku is incredibly well documented and also takes advantage of the documentation and community of Heroku, being essentially the same thing, but in the case that you encounter an actual bug or issue, it can take time for a fix to make it into a new version. Since you manage Dokku yourself, there is no support team to call for help.
Read full review Training and usage support available
Read full review Alternatives Considered Dokku is essentially the same thing as Heroku, except maintained by you on the platform of your choice. If you have any experience using Heroku, then you will feel right at home using Dokku. Dokku is an entirely free to use PaaS, requiring only that you have a platform to deploy it on, making it far more versatile than Heroku in my opinion.
Read full review Read full review Return on Investment Since there's no investment besides a little time to set up, the return has been overwhelmingly positive. Deploying a new app is incredibly quick and easy. Read full review It reduced the complexity of network mesh (ingress/egress services). One tool with many solutions. No need to integrate monitoring tools or notification tools. It reduced the number of lines of YAML code. It reduced the number of labor hours. Read full review ScreenShots