Real files. The Coder agent writes source into a job workspace; the Packager zips it. You download a project package, not a conversation transcript.
You receive the delivered package for your project use. CodeForge does not claim product ownership of your specific deliverable. You are responsible for review, security, and production deployment.
Depends on tier and model load. Small Spark jobs can finish in roughly a minute; larger Core–Forge jobs take longer while agents design, generate, and package. The status page updates live.
Tiers map to scope and price: Spark for tiny utilities, Core for solid APIs/tools, Build for fuller apps, Scale for complex systems, Forge for the heaviest jobs. Pick the closest fit and describe the outcome clearly.
Yes. Every job has a status page that polls phase updates until delivery, then unlocks download.
Slack delivery alerts are supported when a webhook is configured. Email can be enabled with SMTP settings. The status page works either way.
The factory is strongest at Python and FastAPI-style backends today, and can generate other structured projects from a clear prompt. Specific frameworks should be named in your request.
Start a new job with a tighter prompt, or contact support with the job ID. Treat the first delivery as a strong draft from an automated factory, then iterate.
No. Pricing is per project / per job by tier. You pay for the build capacity you need.
You can start a build from the homepage with a prompt and tier. Accounts and dashboards can come later for history and billing.
On CodeForge workers attached to a secured job queue — not on your laptop. The architecture is designed to add more worker nodes as demand grows.
Chatbots answer. CodeForge runs a pipeline: queue, agents, workspace files, package, notify, download. The product is the delivered software artifact.