Weldr for Developers

ShippedIntroduced in beta

Owner

@engineering

Last verified

2025-10-13

Sources of truth

  • code: docs/progressive-ownership.md
  • test: tests/cli/weldr-cli-contracts.test.ts
  • code: tests/unit/ownership-manifest.test.ts

Automate the boring parts, keep full control of the code that matters, and integrate Weldr into your existing toolchain.

Why Weldr Fits Engineering Teams

  • Progressive ownership built-in – Leave commodity surfaces managed, extend APIs with @custom blocks, or eject modules into your repo with guaranteed TypeScript contracts.
  • Live preview for faster reviews – WebContainers boot the generated Next.js app in-browser so product/design can validate flows without waiting for deploys.
  • CLI + CI friendlyweldr sync, weldr contracts check, and ownership manifests integrate with your pipelines the moment you export code.
  • Zero-regret onboarding – Hosted Free Cloud matches the production stack, and self-hosting mirrors the same runtime for regulated environments.
  • Getting Started

  • Join the hosted beta – Accept your invite, create a workspace, and open a new app chat.
  • Describe the system – Outline entities, workflows, and UI expectations. Watch the preview and schema update in real time.
  • Toggle ownership – Use the Ownership panel or edit weldr.ownership.yaml to decide per-surface modes (managed, extended, ejected).
  • Materialize and export – Once the app compiles in preview, run:
  •    weldr login
       weldr sync <chat-id> --out ./apps/<project>
       weldr contracts check
       pnpm test

  • Commit + iterate – Merge into your repo, add custom code, and re-run weldr sync whenever the chat evolves.
  • Recommended Ownership Defaults

    | Surface | Default Mode | When to Switch | |---------|--------------|----------------| | db, auth, ci, infra | Managed | Keep managed unless you have bespoke infra or compliance needs. | | api, ui | Extended | Great for adding business logic or fine-tuning UI while preserving regen safety. | | domain_logic, styling | Ejected | Move differentiating logic or design systems here so Weldr validates contracts while leaving your implementation intact. |

    Read more patterns in docs/progressive-ownership.md.

    Integrating with Your Stack

  • Testing – Generated projects ship Playwright + Jest scaffolds. Wire them into your CI alongside contract checks.
  • Version control – Commit generated files and your custom code together. Ownership leases make diffs predictable.
  • Environments – Free Cloud uses Weldr-managed Postgres and storage. For staging/production, point the exported app at your infrastructure and keep the ownership manifest in repo.
  • Policies & governance – Upcoming Pro features add policy hooks so you can require reviews before surfaces change modes. Track limits in docs/pricing-and-accounts.md and milestone timing in docs/roadmap.md.
  • Self-Hosting Notes

    Need to run Weldr on-prem or in air-gapped networks?

  • • Follow docs/getting-started/installation.md to clone the repo, configure POSTGRES_URL, and boot the local stack.
  • • Use managed mode locally for parity with the hosted runtime; you can still eject surfaces into the same repo and run contract checks offline.
  • • For teams splitting private “secret sauce,” consider hosting Weldr in a separate workspace and syncing only selected surfaces to your main mono repo.
  • Support Channels

  • Slack (#weldr-docs) – Implementation questions, tips, and roadmap feedback.
  • GitHub Issues – Bug reports with reproduction steps and workspace IDs.
  • Office Hours – Sign up from the in-app roadmap banner for deeper design/architecture reviews.
  • Ready to go deeper? Explore the CLI guide (docs/guides/cli-sync.md) and manifest reference (docs/ownership-manifest.md).