Crewdle Build documentation

Crewdle Build is an AI app generator. You describe your business or idea in plain language, and Build produces a real, working web app you can edit and publish, not just a mockup.

Describe what you want to build, optionally attach a reference file, and pick a model, a reasoning effort, and the environment it runs in. Build turns it into a working web app.

Pick the model that builds your project, an effort level (higher effort thinks longer for a more thorough result, lower effort is faster for quick iterations), and the environment the app will run in, its backend, covered below. You can also attach a reference file or image to steer the design.

How Build works: six guided steps

Build follows a structured method so the result is coherent, not a pile of one-off screens. Each step feeds the next, and you can revisit any step to iterate.

1. Project plan captures the overview, goals, target users, and scope: what is in, what is out, and the tone and stack to build with.
2. Design system sets your brand: colors, fonts, spacing, and a library of reusable components.
3. Journey map lays out how your customers move through the experience, stage by stage.
4. Mental model turns that into an information architecture: the key concepts and how to navigate them.
5. Task model breaks goals into tasks and maps each one to a screen.
6. Prototype assembles a live web app from your design system components, screen by screen.

The workspace turns the steps into tabs (Project Plan, Style Guide, User Journey, Structure, Blueprint, Code), with an AI chat alongside to drive each one and a revision history to roll back.

Describe, generate, edit, publish

Start a project and tell Build what you need: a storefront, a customer portal, an internal scheduler. Build generates it with real pages, real flows, and realistic data. From there you can change copy, swap colors, add a section, or edit the underlying code in the built-in editor. When it is ready, publish it to a live URL, and point your own custom domain at it.

How to start a project

1. Open Build and describe what you want, or pick a starter like Landing page or Admin dashboard.
2. Answer the AI's quick questions, then let it work through the guided steps starting with the project plan.
3. Edit anything in the workspace, then Present, Share, or publish to a live URL.

A finished build: real components and real content, deployed to a live preview automatically as it's assembled. For a full walkthrough, see Build a website from scratch.

Environments: a real backend, provisioned for you

Anything you build needs somewhere real to run. An environment is a reusable Firebase backend that Crewdle provisions for you: hosting always on, plus a database, authentication, storage, and secrets, all included by default. Create one from Environments in the sidebar, then attach as many projects as you like to it: one backend can serve a whole portfolio of sites and apps. Build asks you to create one before your first project.

One environment, many projects: each service shows its own status as it provisions, in the region listed on the card.

Environments are what let a Build project be more than a static page: sign-ins, user accounts, saved data, and uploaded files all have somewhere to live. Manage users on the environment card handles your app's end-user accounts, create one with an email and password or search existing ones, without touching a console. When you start a project, pick its environment in the composer, right next to the model and effort controls.

Name it and go: hosting is always on, and database, authentication, storage, and secrets are on by default. Fine-tune them under advanced settings.

How to create an environment

1. Open Environments in the sidebar and click New Environment.
2. Name it, and optionally open Advanced settings to toggle the database, authentication, storage, or secrets services.
3. Click New Environment and watch each service provision; the card turns Ready in a couple of minutes. Pick it in the composer when you start a project.

What you can build

• Websites: storefronts, marketing sites, and info pages
• Customer portals: login, accounts, and dashboards for your customers
• Internal tools: schedulers, dashboards, and forms for your team

Collaboration and sharing

Build supports real-time collaboration, so more than one person can work on a project at once. Share a project with a link for review and comments, present it in a full-screen walkthrough, and sync the code to GitHub when a developer needs to take it further.

Engineering insights from GitHub

Once you link a GitHub account, Insights reads every repository, pull request, branch, and commit across your organization and turns them into a dashboard of real engineering activity over the last 7, 14, 30, or 90 days, not just what has changed inside Build. It is organized into six views:

Link GitHub to see repository, pull request, and commit activity across your organization.

• Overview: KPI tiles for merged and open PRs, median time to merge, active branches, contributors, and lines landed vs. still in progress, plus an activity chart and a commits-by-day-and-time heatmap.
• Analysis: click Generate to have a model you pick turn the raw metrics into a plain-language report: a headline summary, Highlights of what shipped, a Needs attention list that calls out real risks like stalled PRs, unreviewed work-in-progress, and aging dependency bumps, a What shipped changelog of individual changes, and a By person and By repository breakdown, each linking back to the source PRs and repos.
• Shipped: every active repository with its own merged PRs, commits, lines changed, and an activity sparkline.
• People: a per-contributor leaderboard of merged PRs, commits, and lines changed, so you can see who has been working where.
• In Flight: every open pull request, with its size, age, and how long it has been stalled, filterable by repository or author.
• Branches: every branch across your repositories, flagging which are stale or active without an open PR.

Overview surfaces the KPIs that matter: merge velocity, active branches, contributors, and lines landed vs. in progress.

Shipped breaks activity down by repository, each with its own sparkline.

People ranks contributors by merged PRs, commits, and lines changed over the selected window.

In Flight flags pull requests that have gone quiet, with filters by repository and author.

Branches surfaces stale branches and ones running without an open PR, with a delete action right there.

How to see engineering activity for a project

1. Open Insights and click Link GitHub account.
2. Authorize Crewdle to read your organization's repositories, pull requests, and commits.
3. Pick a date range (7d, 14d, 30d, or 90d), then move between Overview, Analysis, Shipped, People, In Flight, and Branches. Use Refresh to pull the latest.

Build CLI for developers

When the visual generator is not enough, developers can drop down to the Build CLI for AI-assisted coding in the terminal, working on the same project and the same platform. It authenticates with your Crewdle account. See the Build product page for more.