From Idea to Production with One Prompt
What if you could describe an app and have it running on the internet in minutes? Not as a mockup or prototype, but as a real, functional application with a public URL. That's the reality of building with Claude Code and DartUp.
The New Development Paradigm
We're witnessing a fundamental shift in how software gets built. The traditional cycle of plan → code → test → configure → deploy → debug → repeat is collapsing into something much simpler: describe and ship.
Claude Code handles the coding. DartUp handles the deployment. You handle the ideas. Let's see what this looks like in practice.
Live Example: Building a URL Shortener
Let's build and deploy a complete URL shortener—with API, database, and frontend—in a single Claude Code session.
You: Build me a URL shortener with:
- A simple landing page where users paste a URL
- Generate short codes like /abc123
- Track click counts
- Use SQLite for storage
- Use Express and vanilla HTML/CSS (keep it simple)
Creating URL shortener application...
✓ Created server.js with Express API
✓ Created public/index.html landing page
✓ Created public/style.css
✓ Set up SQLite with better-sqlite3
✓ Added /shorten POST endpoint
✓ Added /:code redirect handler
✓ Added click tracking
In about 30 seconds, Claude has created a working URL shortener. Now let's deploy it:
You: Deploy this to DartUp as "shorty" with persistent storage
Deploying to DartUp...
✓ Detected: Node.js (Express)
✓ Persistent volume enabled at /app/data
✓ Building container...
✓ Deployed!
Live at: https://shorty.dartup.dev
That's it. A URL shortener with a database, tracking analytics, and a public URL—built and deployed in under 2 minutes. The persistent volume means the SQLite database survives container restarts and redeployments.
What Just Happened?
- 1.Claude analyzed your requirements and picked the right tech stack
- 2.Generated all the code: server, frontend, database schema
- 3.DartUp detected Node.js and created an optimized Dockerfile
- 4.Built the container image in isolation
- 5.Deployed with HTTPS, health checks, and auto-restart
- 6.Mounted persistent storage for the database
Another Example: SaaS MVP
Let's try something more ambitious. A simple SaaS for tracking habits:
You: Build a habit tracking app with:
- Users can add habits they want to track
- Check off habits each day
- See a streak count for each habit
- Simple and clean UI
- Use localStorage for now (no auth needed)
- React with Vite
Building habit tracker...
✓ Initialized Vite + React project
✓ Created HabitList component
✓ Created HabitItem component with streak logic
✓ Created AddHabitForm component
✓ Added localStorage persistence
✓ Styled with Tailwind CSS
You: Deploy to DartUp as "habits"
Deploying...
✓ Detected: React (Vite)
✓ Building production bundle...
✓ Configuring static server...
Live at: https://habits.dartup.dev
You now have a working habit tracker you can share with friends, use for user testing, or iterate on. No DevOps required.
The Power of Iteration
The real magic is how fast you can iterate. Don't like something? Just say so:
You: Add a weekly view that shows habits completed each day
✓ Added WeeklyView component
✓ Updated navigation
You: Deploy the update
✓ Redeployed to habits.dartup.dev
Feature requested, implemented, deployed, live—all in under a minute. This is what "move fast" actually looks like.
When to Use This Workflow
This approach is perfect for:
- MVPs and prototypes - Test an idea before investing weeks of development
- Internal tools - Build what your team needs without waiting for IT
- Side projects - Ship that weekend idea before motivation fades
- Demos and presentations - Build working demos, not mockups
- Learning projects - See your code running on a real URL
- Client prototypes - Show clients working software, not wireframes
What About Complex Apps?
This workflow scales. Need a database? Deploy with Postgres:
You: Deploy this with a Postgres database
✓ PostgreSQL sidecar created
✓ DATABASE_URL injected
Need background jobs? Add Redis:
You: Add Redis for job queuing
✓ Redis sidecar created
✓ REDIS_URL injected
DartUp grows with your app. Start simple, add complexity when you need it.
The Speed Matters
There's a psychological difference between "I'll deploy it later" and "it's already live." When deployment takes seconds instead of hours:
- You share your work more often
- You get feedback faster
- You iterate instead of planning
- You ship instead of polishing
- Ideas don't die in "I'll deploy it eventually" limbo
Getting Started
Ready to try this workflow?
- Sign up at dartup.dev (free)
- Get your API key from the dashboard
- Install the MCP plugin:
npx dartup-mcp@latest install - Start building with Claude Code
- Say "deploy to DartUp" when you're ready
That's it. Your ideas can be live on the internet in minutes.
What will you build?
Start free. Your first idea could be live in under 5 minutes.