Self-hosting Dub on Docker + Kubernetes: any limitations vs. Vercel stack (deep links, deferred deep links, webhooks, analytics)?
Hello Team,
I’m planning to self-host Dub on AWS using Docker + Kubernetes instead of the recommended Vercel + PlanetScale + Upstash + Tinybird stack.
Questions:
1.) Will all core features (deep links, deferred deep links, referrals, webhooks, analytics) work the same when deployed on K8s? Is there an official Docker image/compose setup you recommend, or should I containerize manually? 2.) Are there any parts tightly coupled to Vercel/Tinybird/PlanetScale that might break or need re-implementation? 3.) Any special requirements for iOS/Android deep links (AASA, assetlinks.json) or for the deferred flow when not on Vercel?
Basically: will Docker/K8s give me full feature parity, or are there caveats I should know? Thanks for the great project—happy to share back a Helm/K8s manifest once I get it running!
Source: dubinc/dub