How to build, verify and ship with ScodyX

Create an account, then open a workspace. Every workspace has its own projects, members and credit balance, and nothing is shared between workspaces.

Start a project by describing the app you want in plain language — the audience, the main screens, and the data it should keep. The more concrete the description, the less rework in later runs.

• Name the outcome, not the implementation: “a booking page for a dental clinic”, not “a React form”.
• Mention the pages you expect so the first build lands the right structure.
• Add constraints you care about, such as mobile-first, dark mode, or a specific tone of voice.

Each run follows the same four phases: plan, build, verify, repair. The plan is shown before files are written, the build streams files as they are produced, verification checks the app actually renders and routes, and repair takes another pass at anything that failed.

The timeline on the right of the builder records every run, the files it touched and the credits it used, so you can trace how the project reached its current state.

• Queue follow-up prompts while a run is in progress; they execute in order.
• Edit an earlier message to branch from that point in the conversation.
• Revert to an earlier run when a change goes the wrong way.

You choose which model family handles a run. ScodyX Advanced routes each task to the engine best suited to it — long-context reasoning, refactoring, or fast iteration — and falls back to the managed Core engine if a provider is unavailable mid-run.

Engine choice affects style and speed more than capability. If a run stalls or a provider errors, the run continues on Core rather than failing outright.

Generated apps can use the built-in managed backend for tables, rows and email sign-in, or you can connect your own database from the workspace settings. Connection settings are validated — reachability, credentials and row-level access — before they are saved.

Protected routes, sign-in screens and per-user data scoping are generated together so a preview behaves like the deployed app.

Every project can be downloaded as a plain source archive with no runtime dependency on ScodyX. Connect a GitHub account to push the project to a repository and keep committing from the builder.

Connect a hosting provider in Settings → Integrations to deploy. Each attempt is recorded on the deployments page with its status, provider response and failure reason if any.

Credits are consumed when an engine performs a run; reading, browsing and exporting are free. Plan credits are granted at each renewal and do not roll over. Credit packs you buy separately do not expire.

The credit ledger lists every grant and debit with a timestamp and request ID, so spend can be reconciled line by line. Retries and engine fallbacks within one run are de-duplicated and charged once.

Invite members to a workspace and assign roles to control who can build, who can manage billing and who can change integrations. Audit records show who changed what and when.