ScodyX is an independent multi-engine app builder by iScholarX. Below is what the platform actually does today, layer by layer, and the limits worth knowing before you start.
Guided tour
Six stages, from the first prompt to a shipped build. Each stage lists what the platform does and where the limit sits.
Step 1 of 6
Start a project and write the outcome in plain language. You can attach a reference screenshot, queue follow-up prompts, and edit any earlier message to branch the conversation.
What happens here
Limit: Prompts are interpreted by a language model, so the first pass may not match your intent exactly — you refine it in the next run.
Every prompt runs plan → build → verify → repair. The plan is shown before files are written, and each phase becomes a timeline entry listing the files it touched and the credits it used.
Choose the model family per run, or let ScodyX Advanced route each task to the engine best suited to it. If a provider stalls mid-run, the managed Core engine takes over so the run still completes.
Generated apps boot in an isolated runtime with their own module registry and storage. Nothing reaches the host page, and the preview reloads as files change.
Generated apps can persist records and sign users in through the ScodyX bridge, or you can point a project at your own external database instead.
Push a branch, commit and pull request per run, deploy to Netlify or Vercel, or export the project as a ZIP you own outright.
Workspace roles, autonomy levels, audit logging and exportable evidence for each run — so a change can be explained after the fact, not just observed.
Credits are debited per phase and every debit is written to a ledger with a request ID.
Request IDs flow through generation calls so a failure can be traced instead of guessed at.
Invite members, assign roles, and keep each member's projects separate inside the workspace.
Connect GitHub, Netlify and Vercel per workspace, with connection status shown before you deploy.
Workspaces are separated at the database policy layer, and tenant isolation is covered by automated tests.
Product docs cover the build loop, data and auth, exports, deployment and credit behaviour.
We would rather set expectations correctly than oversell the product.
Free workspace, no card required. Move up a plan when you need more seats or credits.
Evidenced items are produced by checks that run against the live system and can be exported. Alignment-only items describe how our practices map to a published standard — they are not certifications, audits or attestations by any third party.
Full control register and framework mappings: Compliance & standards · Security overview