Docs
Start building
Getting Started

Webforgia Docs

Webforgia turns a plain-language description into a finished website, deck, document, app or game — then lets you refine it in chat, wire it to your tools and publish it. This is the reference for everything it does.

Start here

  • New to Webforgia? Read What is Webforgia?, then follow the Quick Start.
  • Building something specific? Pick it from Build Types — each page says what you get and how it is made.
  • Wiring it into your own tools? Go to MCP or the API.
  • Something not working? Troubleshooting lists every error and what to do about it.

What is in these docs

Getting Started
6 pages · What these docs cover and where to begin.
Open →
Build
17 pages · What happens between Send and a finished build.
Open →
AI Engine
8 pages · Data, not code: the idea behind the engine.
Open →
Editing
7 pages · Three ways to change what was built.
Open →
Connectors
13 pages · What connecting a tool really does.
Open →
Publishing
7 pages · One button to a live HTTPS address.
Open →
Code & Export
5 pages · Every way to take a project with you.
Open →
MCP
9 pages · Webforgia's MCP server, and MCP as build context.
Open →
Credits & Billing
7 pages · Credits are cents, charged for real usage.
Open →
Developers
6 pages · Building projects from your own code.
Open →
Troubleshooting
7 pages · Every build error and what to do.
Open →

How these docs are kept honest

Where a page lists something the product has — the stages a build runs, the agents on each team, every connector, every skill, every MCP tool, every price — the list is generated from the same code the product runs on. When Webforgia changes, those pages change with it. Where something is not built yet, the page says so rather than describing a plan.