Launching today
TryDirect
Deploy Multi-Container Docker Stacks to Your Cloud
6 followers
Deploy Multi-Container Docker Stacks to Your Cloud
6 followers
Deploy complex multi-container stacks (n8n, Dify, OpenClaw and 50+ more) to your own cloud in under 5 minutes - no DevOps. TryDirect provisions servers on Hetzner Cloud, DigitalOcean, Vultr, Linode, and more, then deploys production-ready stacks with databases, and monitoring built in. Includes a visual drag-and-drop stack builder, an AI assistant with 37 tools, and a self-hosted Status Panel agent on every server. Your infrastructure, your control.
The drag-and-drop stack builder sounds great for visual folks, but I'd love to see a built-in cost estimator that shows projected monthly spend on each provider before you commit. Trying to compare what Hetzner vs DigitalOcean will actually run for a given stack would save a lot of trial and error.
@lhancltm Great feedback, İlhan and honestly, this is the biggest usability
gap in Stack Builder right now. Today we show the stack config and let you pick a VM size per
provider, but we don't do the math to project monthly cost. The
reason is that pricing across providers is messy in different ways:
Hetzner is clean (fixed VM + traffic), DigitalOcean adds bandwidth
overages, AWS is per-resource across ~10 dimensions. Building a reliable estimator that
stays current is real work but you're right that it's the biggest
source of "should I even try this?".
I'm putting this on the roadmap. Question back at you (and anyone
else reading):
how would you want it framed?
1). Single number per provider: "~€45/mo on Hetzner, ~$68 on DO" = easier to compare
2). Breakdown with ranges: "Compute €X + storage €Y + bandwidth €Z (assumes N users/mo)" = more honest, more complex
been looking for something like this, the drag and drop builder sounds great. one thing id love to see is built in cost breakdowns per stack, like estimated monthly spend based on the resources picked, would make it way easier to decide between hetzner and digitalocean before hitting deploy