Workflow

From idea to a live product, in a clear order.

Create the project, build the frontend in the IDE, attach the Backend you need, check quality, then publish to a live sandbox — all in one Workspace.

workflow.runACTIVE

1Create the projectdone

2Build the productdone

3Connect servicesdone

4Verifydone

5Publishready

Portable project filesBackend only as neededChecks before releaseVisible Deploy status

Five stages in order

Project, product, services, checks, then Deploy.

Start from scratch, pick a template, or connect an existing Git repository.

Your files and Git history stay with you outside Faiber.

Guide the Design and Code agents in the IDE so the UI and React source stay in sync.

Design and code live in the same project — no separate export.

Choose only the Backend the product actually needs; those services attach automatically.

Identity, payments, Messenger, and Flow join the same project when you need them.

Run Lint, Build, Preview, and Design quality before you publish.

If something fails, you fix it here — not after Deploy.

Build with BuildKit and launch the app in an isolated sandbox.

Then inspect routes, logs, and health to confirm the product is live.

Repair loop

01Inspect

See the files that changed

02Run

Run Lint, Build, and Preview

03Repair

Fix the failure in the same project

04Prove

Keep the passing result

Deploy path

The app is built and started in an isolated sandbox. You can see routes, logs, and health — without putting server credentials in application code.

Faiber

Start a new project, or connect an existing Git repository to the same Workspace.