# Platform architecture

Engines of Creation combines an interactive creation workspace with services for account access, AI requests, compilation, project storage and publication. The architecture supports both browser projects and more advanced development workflows, without treating them as the same runtime.

## The creation path

```text
Your idea and current project
          ↓
Conversation or explicit build approval
          ↓
Selected AI connection + project tools
          ↓
Candidate files → compilation → preview observations → review
          ↓
Accepted save → play, iterate, download or publish
```

A conversation can inspect project context without authorizing source changes. A build operates on a candidate tied to the current project. Checks and review apply to that candidate; later edits require new evidence. Recovering files does not convert an unfinished attempt into an approved version.

## The main components

| Component | Responsibility |
| --- | --- |
| Browser workspace | Conversation, project files, memory, preview, local records and user controls |
| Account and control services | Authentication, membership, plan access, scoped project operations and supported usage accounting |
| Provider connection | Sends the selected task/context to the chosen AI service through its supported route |
| Compiler and preview | Assembles supported browser source and runs the playable candidate in an embedded preview |
| Review workflow | Evaluates the candidate against the request before a guided save |
| Storage and publication | Optional private backups, hosted workspace artifacts and explicitly public game releases |

The web application uses Next.js. Backend services use Cloudflare Workers and related storage/execution services. A hosted terminal provides a separate project command environment. These implementation choices describe the product, not an invitation to use internal service endpoints as a public API.

## Browser and native execution

Browser games can use Canvas or Three.js with supported project assets. Downloaded browser builds use their own packaged runtime. Templates requiring servers or external services retain those requirements.

The hosted terminal and a locally paired Companion are separate execution paths. Native Claude Code or Codex sign-in belongs to the official provider client. A configured browser connection does not automatically configure a terminal or local computer. Follow the connection UI for the route available to your account.

GEngine operates inside Unreal Editor and has its own installation, tools and compatibility requirements. It does not turn a browser project into an Unreal build automatically.

## Storage boundaries

Local browser drafts, records and the encrypted credential vault are distinct from optional account backups and hosted Studio artifacts. Public publication creates a deliberately shared copy. [Projects and recovery](/docs/projects-and-recovery) explains which export carries source, memory and history; [privacy and security](/docs/privacy-and-security) explains the associated data handling.

## Blockchain is an integration choice

EoC is not a blockchain validator network. Browser creation does not require every game rule or asset to be onchain. Current integrations include read-only market data, examples and optional chain modules. Production payment, ownership or settlement logic requires its own implementation and validation. See [integrations](/docs/integrations) for the status of each path.