Start guided. Go as deep as you want.
Move naturally between visual building, map and asset creation, scripting, terminal work, playtesting, and portable export—without leaving your project behind.
The active project, scene, assets, history, and readiness stay with you as the work changes shape.
Open a project, begin with a playable blank, or use a guided game profile.
Edit scenes, terrain, entities, cameras, components, and reusable resources.
Generate, import, process, review, and accept candidates through one durable lifecycle.
Move into Power Studio for code, visual graphs, terminal work, and project-aware help.
Test the active scene, continue after reload, and produce portable, inspectable output.
PyreForge does not force beginners to understand an engine before creating—or force professionals to stay inside simplified tools.
Use plain-language setup, visible readiness, safe previews, and focused actions that teach the workflow while you build.
Inspect receipts, control providers and seeds, edit scripts, use visual graphs, and work directly from the integrated terminal.
The interesting part is not any one subsystem. It is visual editing, runtime, generation, persistence, recovery, and export surviving the same end-to-end checks.
Internal acceptance evidence, not a synthetic comparison against another engine. Counts describe the sealed Phase 1 boundary; newer map and asset slices are gated independently before joining it.
Specialist workspaces share the same project, assets, scenes, jobs, history, and health context.
Project-aware assistance for creation, scripts, and questions, with explicit provider selection and compatible local or BYOK routes.
Provider choice remains visibleRun the authoritative active scene with input, cameras, interactions, HUD state, and sandboxed gameplay scripts.
Scene-aware Play lifecyclePortable project and simulation ZIPs, asset and map formats, and model output. Target-engine adapters vary in maturity and remain explicitly labeled.
Receipts and artifact hashesImport, voxel, sculpt, material, animation, physics, and export tools connected to the same project resource system.
Specialist workspacePersistent project context, active-scene routing, revision recovery, dependency locks, and deterministic build manifests.
One project through every workspaceGenerate or import, process, validate, review, retry, accept, place, reimport, version, and roll back durable assets.
Raw results remain candidatesMonaco editing, a sandboxed QuickJS terminal, visual graphs, debugging, and project-aware script iteration.
Traditional code stays first-classMap Studio, asset generation, ForgeWeld, and Power Studio can stand alone from the main menu while sharing the unified lifecycle when a project is open.
Preflight supported locations, capture attributable elevation data, review the exact terrain candidate, then create an undoable scene.
Managed USGS-derived DEM route in active validationPaint square, hex, and isometric terrain, use procedural generation, and keep an offline path when providers are unavailable.
Local-first terrain toolsUse compatible ComfyUI, procedural, hosted, BYOK, and imported routes without exposing raw provider plumbing to beginners.
Requested vs. resolved receiptsPreview processed artifacts, retry the same route, regenerate variants, accept, place, replace a version, or keep exploring.
Nothing enters a scene by accidentBring in common model formats, adjust geometry and materials, animate, validate, and return project-ready resources.
Import → edit → validate → exportTrack logical identity, versions, dependencies, reusable definitions, variants, reimports, impact previews, and rollback.
Durable project truthThe studio is broad, but the claims stay tied to tested journeys. Experimental targets and unfinished polish remain labeled.
Multi-scene editing, active-scene Play, command history, save slots, cold reload, recovery, and portable export.
Cross-workspace browser journeysDurable sprite and terrain candidates, exact receipts, acceptance, placement, reimport, versions, variants, and rollback.
More creation routes are converging nowIntegrated code editing, sandboxed execution, terminal workflows, visual graphs, and project-aware context.
Advanced tools without a separate projectLocal, BYOK, and managed routes depend on installed models, configured providers, connectivity, and each provider's capabilities.
Preflight and route receipts stay visibleTerrain painting, procedural maps, limited managed real-world DEM capture, model import, editing, animation, and output.
Coverage and scale vary by workflowProject, simulation, asset, model, and map outputs are available. Godot, Unity, desktop, and mobile are not universal release claims.
Verify the exact target before shippingThe current verified release boundary is Chromium-based web use. Other browsers and packaged desktop require separate certification.
Platform claims remain evidence-basedCreator pages, showcases, livestreaming, assets, and templates are being developed as a decoupled platform—not hidden inside editor claims.
Independent product boundaryGame profiles provide useful starting structure and tools. They are starting points—not a promise that every genre arrives production-complete.
The first genre journeys are being proven end to end—from starter assets through creation, editing, Play, save/reload, and export. Once those full-cycle slices are polished, the same treatment will expand across tower defense, roguelike, survival, horror, racing, city builder, dating sim, educational, and the rest of the profile catalog.
Join the private beta and help shape a studio built for beginners who want a clear path and professionals who want real control.
Join the Private Beta