Launch FAQ

Use this cheat sheet when fielding launch questions. Answers are grouped by audience so you can grab the most relevant proof points fast.

Builders & Founders

Q: What problem does Weldr actually solve? You can turn a conversation into a working full-stack app without forfeiting control. Weldr handles the boilerplate (data model, UI scaffolds, auth, notifications) while you decide which surfaces stay auto-managed and which you own outright. Q: How is this different from Bolt, Lovable, or v0? Progressive Ownership. Every surface can be managed, extended, or ejected, so regenerations never overwrite your custom logic. Competitive tools force you to choose between automation and control; Weldr lets you keep both and documents the contract in code. Q: Is it production-ready? For Next.js + Postgres CRUD apps, yes—teams are already running Weldr-generated projects in production. For exotic stacks or deep integrations we consider it beta; Progressive Ownership ensures you can harden the code without losing AI help. Q: What’s the pricing story? We’re in free beta through launch. Planned tiers: Free (limited projects), Starter ~$29/mo, Pro ~$99/mo. No lock-in—exported code keeps running on your infra even if you leave.

Developers & Technical Evaluators

Q: Do I lose my custom code on regeneration? No. @weldr regions regenerate, @custom regions are preserved, and ejected modules are never touched. The Change Coordinator blocks any mutation that would overwrite code you own. Q: What stacks do you support today? Next.js + React + TypeScript + Drizzle/Postgres. Other frameworks (Vue, Svelte, Django) are on the roadmap; for now you can export schema/contracts and reimplement them manually. Q: How does contract validation work when I eject code? Weldr generates a TypeScript interface for each ejected surface. Your implementation must satisfy that contract; the compiler verifies it so future regenerations stay compatible. Q: Can I mix in custom auth, notifications, or Kanban logic? Yes. Auth, notifications, and Kanban are capabilities—describe the intent and Weldr scaffolds providers, env vars, and UI. You can then extend or eject those surfaces for bespoke logic without breaking the spec.

Influencers, Partners, and Media

Q: What’s the headline positioning? “Progressive Ownership for AI-generated apps.” Weldr listens to natural language, detects common app patterns, and keeps developers in control of their codebase. Q: Why now? Teams are hitting AI lock-in walls—regeneration keeps overwriting custom work. Weldr captures intent through capabilities (auth, notifications, Kanban, CRUD pages) and guarantees your ownership boundaries, so AI can finally ship production code safely. Q: Any proof points we can share?

• Zero surprise diffs: Canonical model governs every regen.

• 100% custom code preservation in @custom regions.

• Adapter swaps (e.g., Vercel ↔ Supabase) in under five minutes.

Q: What’s coming next? Short term: richer previews (auto regen, telemetry), more capability coverage (workflows, billing), and additional stack adapters. Medium term: open plugin/skill ecosystem so partners can contribute their own capabilities.

Quick References

• Comparison breakdown: business-docs/COMPARISON_PAGE_CONTENT.md

• Launch outreach targets: business-docs/outreach-targets.md

• Deep terminology explainer: docs/TERMINOLOGY_AND_CONCEPTS.md

• Launch playbook responses: business-docs/LAUNCH_DAY_PLAYBOOK.md