The Starting Line

Let me paint you a picture of where we are today:

It's Sunday evening. I'm sitting in my home office in Colombia, surrounded by empty coffee cups and half-eaten empanadas. I just pushed a commit fixing a bug that's been haunting me for three days. My "launch" consists of this blog post and a prayer that someone, somewhere, gives a damn about what I'm building.

Welcome to Day Zero of InfraUX.

Today's Metrics Dashboard

<MetricsCard date="2025-09-28" previousDate={null} showChange={false}

Users: 0
Revenue: $0
GitHub Stars: 0
Features Shipped: 0.8 (yes, less than one)
Bugs Fixed: 47
Coffee Consumed: 5 ☕
Days Without Breaking Prod: N/A (no prod yet!) </MetricsCard>

What the Hell is InfraUX?

InfraUX is my answer to a simple question: Why does deploying a web app in 2025 still feel like performing brain surgery with a rusty spoon?

I'm building the all-in-one DevOps platform with 17+ planned modules:

Currently Available (well, 80% of it):

Visual Infrastructure Designer - Draw your architecture, not YAML (80% complete)

Coming Soon™ (the other 16+ modules):

Automatic IaC Generation - Terraform, Pulumi, CloudFormation, Ansible
CI/CD Pipelines - Built-in, no Jenkins nightmares
Monitoring & Observability - See what's actually happening
Cost Management - Know what you're spending before AWS surprises you
Drift Detection - When reality doesn't match the plan
Compliance & Security - Built-in, not bolted on
Chaos Engineering - Break things on purpose
Service Mesh Management - Istio without the pain
GitOps Integration - ArgoCD + Flux native
Database DevOps - Schema migrations that don't suck
Edge Computing - Deploy to the edge easily
Multi-tenant Architecture - Isolation without complexity
Disaster Recovery - Automated backup & restore
Performance Testing - Load testing built-in
Secret Management - Vault integration native
And more... - Whatever the community needs

Think of it as Figma + GitHub Actions + Terraform + Datadog + Infracost + 12 other tools you're currently juggling. Eventually. When it's done. Which it's not.

The Problem We're Solving

I've been a DevOps engineer for 10 years. In that time, I've:

Written approximately 73,000 lines of YAML (kill me)
Debugged Terraform state conflicts at 3 AM more times than I can count
Explained what a "security group" is to 47 different junior developers
Watched brilliant engineers quit because they couldn't understand our "simple" Kubernetes setup

The tools we use were built by infrastructure experts, for infrastructure experts. Everyone else is just collateral damage.

The Solution: One Platform to Rule Them All

InfraUX replaces your entire DevOps toolchain:

Instead of:

Terraform + Terragrunt + Atlantis
Jenkins + GitHub Actions + CircleCI
Datadog + Prometheus + Grafana
Infracost + Cloud billing dashboards
Confluence + draw.io + Lucidchart

You get:

Visual Everything: Design, deploy, monitor - all visual
Unified Platform: One login, one interface, one source of truth
Smart Automation: AI-powered suggestions and error prevention
Multi-Cloud Native: AWS, GCP, Azure, on-prem - we handle it all
Built-in Best Practices: Security, compliance, cost optimization baked in

Why Build in Public?

Because infrastructure tooling has been a black box for too long.

Every DevOps tool website shows the same thing:

"Trusted by 10,000+ companies" (translation: 10 free trials)
"10x faster deployment" (compared to carrier pigeons)
"Enterprise-ready" (meaning expensive)

I'm doing something different. I'm showing you everything:

Real user numbers (currently: zero)
Real revenue (also zero)
Real challenges (currently: everything)
Real code (going open source next month)

What We're Sharing

Every single day, I'll share:

Metrics: Users, revenue, churn, server costs
Technical decisions: Why we chose X over Y
Failures: What broke and how we fixed it (or didn't)
Customer feedback: What you're telling us (please tell us something)
Personal struggles: The human side of building a startup

The Technical Foundation

For the nerds in the audience (my people), here's what I'm building on:

The Stack

// Frontend
{
  framework: "Next.js 15",
  visualEngine: "React Flow",
  stateManagement: "Zustand",
  styling: "TailwindCSS",
  language: "TypeScript"
}

// Backend
{
  api: "FastAPI",
  database: "PostgreSQL + Supabase",
  queue: "Celery + Redis",
  language: "Python 3.11"
}

// Infrastructure (ironic, we know)
{
  hosting: "Vercel + Railway",
  monitoring: "Posthog",
  ci: "GitHub Actions",
  budget: "$47/month"
}

Current Capabilities

What works today (the honest 80% of one module):

✅ Visual infrastructure designer (80% functional, 20% "character")
✅ AWS resource modeling (15 services... mostly)
✅ Basic Terraform generation (when it feels like it)
✅ Diagram versioning (don't ask about version 3)
✅ User authentication (Auth0 doing the heavy lifting)

What's still broken in the Infrastructure Designer (that last 20%):

🐛 Connection lines sometimes go on vacation
🐛 Save button has trust issues
🐛 Zoom controls are drunk
🐛 Dark mode is more like "dim mode"

What's coming (the other 16+ modules we promised):

🚧 All 16+ modules mentioned above
🚧 Multi-cloud support (AWS, GCP, Azure)
🚧 Import from existing infrastructure
🚧 Team collaboration features
🚧 Enterprise features nobody asked for
❌ The business model
❌ My sanity
❌ Sleep (what's that?)

The Roadmap (Or: Our Best Guesses)

Next 30 Days

Finish that last 20% of Infrastructure Designer (the hard part)
Launch public beta (with one mostly-working module)
Add 10 more AWS services
Fix those 4 critical bugs in the Designer
Get our first 100 users (currently: 0/100)
Maybe start module #2?

Next 90 Days

Infrastructure Designer at 100% (finally)
Start 2-3 more modules (not all 16, let's be real)
Hit 1,000 users (optimistic)
Launch paid tier ($29/month)
Get to $1,000 MRR (very optimistic)
Open source the core engine

Next Year

10,000 users
$50K MRR
Team of 5
Support all major cloud providers
Still drinking too much coffee

Lessons Learned (Already)

Seven months of building has taught me:

Perfect is the enemy of shipped: My first version was so bad, I deleted it entirely
Users > Features: I built 47 features nobody asked for
Complexity compounds: Every abstraction creates two new problems
Coffee has diminishing returns: After cup #8, you're just vibrating
Building alone is lonely: But the freedom to make quick decisions is priceless

The Ask

I'm not asking you to buy anything. Hell, I barely have anything to sell.

What I'm asking for:

Try it: Break my app. Please. I need to know what fails.
Feedback: Tell us what sucks. Be brutal.
Share: If you know someone fighting with infrastructure, send them my way
Follow: Watch my journey, learn from my mistakes
Contribute: Going open source soon, I need help

What's Next

Tomorrow, I'm:

Launching the public beta
Publishing our first technical deep dive
Fixing at least 3 bugs (and probably creating 5 new ones)
Drinking more coffee
Questioning our life choices

Join the Journey

This is Day Zero. I have:

No users
No revenue
No idea if this will work

But I have:

A vision for better DevOps
The stubbornness to keep building
A commitment to radical transparency
Really good coffee

Want to follow along? Here's how:

Question for you: What's the one infrastructure task that makes you want to throw your laptop out the window?

Building InfraUX in public, one bug at a time. See all posts →