2
3 Comments

AI can build the app. But who builds the infrastructure? 🧐

I met someone yesterday who charges $400 for a one-day job migrating apps over to Cloudflare. 💰

That got me thinking about how much infrastructure complexity is hiding underneath these AI-built apps.

You can use Lovable, Replit, Bolt, Claude, etc. to build an entire application in a matter of hours. ⚡

But the moment your app needs file storage, you run into things like:

📦 Creating and configuring buckets
🔐 Setting up permissions and access policies
🔗 Figuring out public vs. private files
🎟️ Generating signed URLs
📏 Managing upload limits
📁 Handling file types and validation
🔌 Connecting storage to your application
☁️ Configuring Cloudflare and figuring out all the different settings
📈 Making sure everything can handle production traffic
🔄 Figuring out how to migrate or change providers later

None of this is particularly difficult for an experienced engineer.

But if you're a non-technical person who just built an app with AI, this is a completely different problem than building the app itself.

You shouldn't need to become a Cloudflare or AWS expert just to let users upload files.

That's what we're building Blobly for. 🫧

With Blobly, you can set up scalable file storage with a simple prompt from whatever AI development tool you're already using.

No complicated setup.
No digging through cloud dashboards.
No figuring out buckets and permissions.

Minimum setup. Maximum simplicity.

Your AI builds the application. 🤖
Blobly handles the infrastructure underneath it. ⚙️

posted toAvatar for product Blobly
Blobly
  1. 1

    The strongest part is the infrastructure gap between “AI can build the app” and “the app is production-ready.” Blobly has a clear wedge if it can make storage setup genuinely disappear from the builder’s workflow rather than simply hiding the same complexity behind another dashboard.

    1. 1

      Thanks, I think you summed up my goal and caution very well.

      1. 1

        That’s exactly the distinction I was getting at. If the infrastructure genuinely disappears from the builder’s workflow, that’s a meaningful difference from simply abstracting it behind another interface.