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.
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.
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.
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.
