Starting a new client project used to mean the same forty-five minutes every time. Pick a framework. Wire in authentication. Configure TypeScript paths. Add a UI library. Set up the email provider. Get the database talking to the frontend. Write the folder structure from scratch or copy-paste from a previous project and spend twenty minutes cleaning up the parts that don't apply.
None of that is interesting work. It doesn't ship anything. It just has to happen before the real work can start.
Fusion Stack is our answer to that problem. One command. Pick your frontend, backend, auth, UI, and email. Get a fully wired, production-ready TypeScript project. Start writing business logic immediately.
Three teams have folded it into how they work. Here's what that looks like.
CoreWave Media: Two clients, two stacks, both shipped
CoreWave Media is a digital agency that builds websites and applications for clients. Their work covers a wide range — event platforms, nonprofit sites, commercial landing pages. The requirement that stays constant is delivery speed: clients expect things to move fast, and setup time is overhead that doesn't add value to anyone.
They've shipped two projects with Fusion Stack.
InLove is a wedding platform built for a couple's celebration — a full event coordination site with a live countdown, an RSVP system, a guest photo gallery, and a detailed ceremony itinerary. It's live at inlove4eva.com. The design brief was romantic and polished. The technical requirement was a site that had to work flawlessly on the day, with no tolerance for downtime or broken forms.
Evolve Impact Inc. is the site for a Canadian event management and community development organization based in Calgary. It covers their programs, scholarship opportunities, sponsorship partnerships, and event gallery. It's live at evolveimpactinc.com. The brief here was professional and trustworthy — an organization asking for donations and sponsorships needs to look like it has its house in order.
Two different clients. Two different aesthetics. Two completely different audiences. The same scaffolding underneath.
For a team that cycles through multiple client projects, Fusion Stack removes the part of the process that doesn't differentiate their work — the configuration — so they can get to the part that does.
TechBros: Building a product, not just a site
TechBros (techbros.tech) is a digital agency building websites and applications for businesses. They're currently developing Avina, a web application for a delivery company — a more complex product build that requires real-time data, user authentication, transactional email, and a polished frontend.
Their stack: Next.js, Convex, Clerk, shadcn/ui, and Resend.
That combination covers a lot of ground. Convex for the reactive backend and database layer. Clerk for authentication. Resend for email. shadcn/ui for the component system. Next.js as the application framework tying it together.
Wiring all of that manually — configuring Clerk middleware, connecting Convex with the right JWT template, setting up Resend with typed email functions, scaffolding the shadcn component directory — is a non-trivial setup job. With Fusion Stack, it's a single command and a handful of environment variables.
Avina is still in development. But the project is moving on business logic, not configuration debt.
NexiumLabs: Eating our own cooking
We built Fusion Stack because we were doing the same manual setup repeatedly across client projects at NexiumLabs. It made sense to solve it once.
We now use it as the starting point for every new client project we take on internally. The tool we built to save other teams time has become part of how our own studio operates — which is either the best possible proof that it works, or a conflict of interest, depending on how skeptical you are.
We'll let the other two teams settle that question.
What the pattern shows
Three independent teams. Two are agencies building client work on deadline. One is the studio that made the tool. All three reach for the same scaffold when starting something new.
The combination that comes up most is Next.js + Convex + Clerk + shadcn/ui — a full-stack TypeScript setup with reactive data, authentication, and a component system included. It's the stack we designed Fusion Stack around, and it's the one that production usage keeps validating.
More stack options are coming. Express and Hono as standalone backend targets, additional authentication providers, and database options beyond Convex are all on the roadmap.
If you're a freelancer, an agency, or a small studio that spins up new projects regularly, the tool is at fusion-stack.vercel.app. The docs are at fusion-stack-docs.vercel.app.
One command. Everything wired. Start shipping.
Built in the open
Fusion Stack is open source — and that matters for a tool like this.
Every stack combination it supports was shaped by real project requirements. The Convex + Clerk + Next.js path exists because that's what we kept wiring by hand. The Hono option exists because not every project needs a full-stack framework. The roadmap is driven by what teams actually reach for when they start something new.
Being open source means that process doesn't stop at what NexiumLabs needs. If your stack isn't supported yet — a different auth provider, a different backend, a database option that isn't Convex — you can add it. The architecture is designed to be extended: each stack option is a self-contained module, and the CLI validates combinations at generation time so new options integrate cleanly without breaking existing ones.
It also means you can audit exactly what gets generated before you run it. No black boxes. No vendor lock-in baked into the scaffold itself. What you get out is TypeScript you own.
The repository is at github.com/NexiumLabs/fusion-stack. Issues, pull requests, and stack suggestions are open.