FactoryForge AIBeta
Open navigation

A canvas-first generator for factory planning.

FactoryForge starts where factory planning actually happens: one clear canvas. Prompts become generations, generations fill a reel, and the best attempt can become a finished published blueprint.

The product is not a chat transcript and not a spreadsheet wrapper. It is a planning surface that treats factories as structured data.

Canvas preview

Iron input

240/min

Assembler row

12 machines

Output bay

60 HMF/min

Prompt dock

Build a clean heavy modular frame factory at 60 per minute.

Preview JSON readyGenerate
Clean bus01
Compact stack02
Published03

Generate first. Publish when it is real.

The model separates cheap preview work from the durable artifact. That keeps iteration generous while making the paid step honest.

Generation

A generation is preview JSON with a lightweight thumbnail. It belongs in the session reel, can be revisited, and should be cheap enough to encourage trying another prompt.

Publish

Publish is the finished blueprint direction: bill of materials, footprint, packaging and logistics detail, best-case totals, and a permanent owned record with the prompt attached.

The workspace shape

Product app implementation owns the real canvas, prompt dock, solver, auth, credits, and save import. The public site only explains the contract and sends builders to the app.

Left rail

Sessions and published library.

Canvas

One active factory hydrated at a time.

Right reel

Generation attempts as thumbnails.

Prompt dock

Generate previews, then Publish keepers.

Canvas preview

Iron input

240/min

Assembler row

12 machines

Output bay

60 HMF/min

Prompt dock

Build a clean heavy modular frame factory at 60 per minute.

Preview JSON readyGenerate
Clean bus01
Compact stack02
Published03

Built for players who plan before they build

FactoryForge is for turning fuzzy goals into buildable factory structures without making every prompt feel expensive.

Prompt factories

Request item targets, rates, constraints, recipe preferences, and layout intent in natural language.

Inspect the plan

Use the canvas as the primary product signal: nodes, flows, logistics, and output goals in one place.

Keep the keeper

Publish only when the attempt is worth owning as a blueprint, not while you are still exploring.