Ship in minutes, not weeks: the Dubleu deploy pipeline
One click. Vercel detects your stack, builds it, and returns a live URL. Here's exactly what happens under the hood when you hit Deploy.
Sofia Reyes
March 22, 2026 · 5 min read
The gap between "done in the editor" and "live on the internet" is where most side projects die. You finish the feature, then spend an afternoon wrestling with CI config, environment variables, and DNS records. By then the motivation is gone.
Dubleu's deploy pipeline is designed to collapse that gap to seconds.
Stack detection
When you hit Deploy, Dubleu inspects your project. If it finds a package.json with a Next.js dependency, it targets Vercel. A static HTML/CSS/JS project with no package.json goes to Netlify. An app.json with an Expo config triggers an EAS build for iOS and Android simultaneously.
No configuration files to write. No provider to choose manually. The right target is inferred from what you've built.
Environment variables
Secrets you've added via the secret-input block are already encrypted in our vault. On deploy, we push them directly to Vercel's environment variable API — they arrive before the first build runs. Your app has access to every key it needs from the first deploy.
Preview URLs
Every deploy, including the first one, generates a preview URL. Share it with a client, a co-founder, or post it in Slack for feedback before you touch the production domain. Preview URLs are permanent links — they don't change on subsequent deploys, so you can always reference a specific version.
Build times
We cache aggressively. A cold Next.js build averages 4.2 seconds. Subsequent builds with unchanged dependencies are faster. We're targeting sub-2-second incremental deploys by Q3 2026.
Share this post
Found it useful? Pass it on.