wovain

• 

  Title

• 

  Connections

• 

  Brief

• 

  Ideas

• 

  Designs

• 

  Judge

• 

  Approve

• 

  Price

• 

  Campaign

• 

  End

Inspiration

I always joined Devpost hackathons and never submitted. Perfectionism and scope creep won every time. This time I wanted to finish one.

wovain is an idea I've carried for a long time. My friends who are fashion designers are great at creating designs. Turning those designs into a business means listings, pricing, shop setup and ads, and that work eats their design time. I wanted something that takes all of it on while the designer keeps the taste and the money decisions.

What it does

You set the direction for a drop in one sentence. wovain backs it with evidence from Qloo and Tavily, drafts graphics on real Fourthwall blanks for you to edit, prices each piece and has a Nemotron judge check it. Nothing moves until you approve. Then it creates a hidden product in your Fourthwall shop and a paused Meta campaign, so you decide when money is spent.

How I built it

The first version was a small ChatGPT app. The day I watched it create a real product in my Fourthwall shop, I got hooked. I bought wovain.com, built the website around it, and started treating wovain as my own startup, one I plan to launch as a real business.

That decision changed everything after it. In one week the stack moved three times: Vercel and Neon, then Firebase, then Google Cloud Run and Cloud SQL, all managed in Pulumi. I rebuilt the app on Next.js 16 with oRPC, Better Auth and Drizzle once I knew it had to carry real accounts and billing. The AI pipeline started on Genkit and moved to Mastra on Inngest so long runs could survive retries.

The guardrails mattered more to me than the features. Every money or publishing step passes a gate in code: a price floor, a budget range, the designer's approval, and Meta campaigns that are always created paused. Every risky change ships behind a feature flag with a kill switch, and every deploy goes out as a canary that promotes or rolls back on its own.

Then I built the flows that keep it running when I'm not looking. GitLab Duo flows review merge requests, scout for problems and post a daily digest, and the issue board lives in code like everything else.

Challenges

• My own scope, the hardest one.
• The last day: recording this demo found a production bug, and the fix went in that afternoon.
• Three hosting moves and two AI frameworks in one week.
• Eight logo rounds, including dropping a stitched W that risked a trademark clash.

What I learned

The constant pushback on the size of my scope from the scope skill, and seeing the full spec early, before getting drowned in prompts and bugs as usual, finally got me to submit. Pivoting fast is fine when the guardrails don't move.

What's next

Smoother, out-of-the-box connections to services, paid plans, and full media buying: wovain launches the campaigns you approve, then shifts budget, pauses losers and scales winners to keep every drop profitable, and feeds what sold into the next one.

Built With

• better-auth
• chatgpt
• claude-code
• drizzle-orm
• fal.ai
• fourthwall
• gitlab
• google-cloud
• mastra
• meta
• model-context-protocol
• nebius-token-factory
• nextjs
• nvidia-nemotron
• openspec
• orpc
• postgresql
• posthog
• pulumi
• qloo
• react
• shadcn-ui
• tailwindcss
• typescript