Cloud cost intelligence before deployment.

⚠️ Status: Currently in development.

Infrastructure decisions are made before deployment. But cost understanding usually comes after the bill.

Exact-looking numbers create false confidence. Hidden assumptions create surprise.

We believe:

• Uncertainty should be visible
• Assumptions should be explicit
• Tradeoffs should be inspectable

We don't promise accuracy. We promise honesty.

Better decisions happen when uncertainty is acknowledged, not hidden.

DraftMyStack is a design-time tool for understanding infrastructure costs before commitment.

This is for the moment when:

• You're comparing AWS vs GCP vs Azure for a new project
• You're debating architectural tradeoffs with cost implications
• You need to justify infrastructure decisions to stakeholders
• You want to understand hidden costs (egress, NAT, support) upfront

We help teams reason about infrastructure decisions before deployment by making assumptions, uncertainty, and tradeoffs explicit.

DraftMyStack is intentionally not:

• ❌ A billing reconciliation tool
• ❌ A post-deployment monitoring system
• ❌ An automated "cheapest stack" generator
• ❌ A replacement for real-time cost tracking

We optimize for decision clarity, not savings promises.

Most infrastructure regret comes from unexamined assumptions, not bad technology.

We've all been there:

• "I thought egress was negligible"
• "We didn't account for cross-AZ traffic"
• "Support plans added 15% we didn't model"

DraftMyStack makes those assumptions explicit, challengeable, and shareable — before code ships.

The core product is proprietary and not open-source.

If you're a platform engineer, cloud architect, or tech lead who wants to understand infrastructure cost before deployment:

→ Join the waitlist (landing page coming soon) → Follow updates on X (Twitter) → Start a discussion to share your use case

Before we launch, we're gathering real infrastructure decision stories to shape DraftMyStack.

If you've struggled with:

• Estimating cloud costs before deployment
• Comparing provider options with limited data
• Justifying infrastructure decisions to stakeholders
• Understanding hidden costs (egress, NAT, support)

Start a Discussion and describe the decision you faced.

We're not looking for feature requests — we want to understand real pain points and the assumptions you wish you could validate earlier.

Your insights will directly influence which cost drivers, assumptions, and comparison scenarios we prioritize.

We don't publish internal mechanics. We publish outputs and artifacts you can inspect.

Start with the public artifacts when available. They show how we think without revealing how we compute.

• 📧 Email: hello@draftmystack.com
• 𝕏 X: @draftmystack

If DraftMyStack ever feels confident about something that should be uncertain, it has failed.

Powered by the InfraVillage ecosystem.

_{More information will be available closer to launch.}