> ## Documentation Index > Fetch the complete documentation index at: https://summer-18f03259-codex-native-multiplayer-entry.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. # Product Source & Platform Status > The canonical status for Summer Engine source access and live, scaffolded, or planned Summercraft platform capabilities. Summer's AI-agent layer is MIT open source. The Summer Engine desktop app is free to download and use, but its source code is not public right now. This page is also the single canonical status source for Summercraft capabilities: reference pages describe contracts, while this page says whether the supporting production path is live. ## What is open today? The public repo is the agent layer: * CLI * MCP server * Agent skills * Hooks * Plugin manifests Repo: [github.com/SummerEngine/summer-engine-agent](https://github.com/SummerEngine/summer-engine-agent) ## What is free? The Summer Engine desktop app is free to download and use. Local MCP workflows are free too, including workflows where you bring your existing Claude Code, Cursor, Codex, Gemini, Devin Desktop, or other agent subscription. ## What is paid? Live hosted Summer services are paid because they run cloud infrastructure and model calls: * Hosted Summer AI * Asset generation * Cloud storage * Orchestration Managed multiplayer is planned as a paid hosted service; it is not production-live today. ## Platform capability status | Capability | Status | What that means today | | ------------------------------------------------ | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------- | | Create Summer game records | **Live** | Authenticated creators can create a game record through the Summercraft API. | | Upload and verify a game-only `.pck` | **Live** | Direct-to-storage upload, server-side SHA-256 verification, and immutable release records are deployed. | | Browser submission and static scanner | **Live** | The signed-in submit page accepts a `.pck` plus `manifest.json` and runs pattern-based static analysis before creating a review submission. | | Manual review queue | **Live** | A submission can enter human review; there is no automatic approval. | | Authenticated release download | **Live** | Owners and admins can retrieve pending releases; published catalog releases follow the documented access rules. | | Summer SDK gameplay and subsystem interfaces | **Scaffold** | The GDScript contract and examples exist, but documented interfaces do not prove the hosted runtime path is deployed. | | `SummerMultiplayerPeer` transport | **Scaffold** | The compatibility contract is published and implementation is in progress. | | Browser or desktop-shell play for uploaded games | **Planned** | A `published` catalog status does not make an uploaded game playable. | | Hosted dedicated game servers | **Planned** | Creators must not promise managed hosting to players. | | Automatic matchmaking and relay | **Planned** | No production matchmaking or relay service is available for uploaded Summer games. | | Automated production runtime sandbox | **Planned** | Submission review is manual; the production sandbox path is still being built. | | Production gameplay runtime | **Planned** | Uploaded and approved packs do not execute in a Summercraft gameplay runtime today. | | Hosted persistence and economy | **Scaffold** | `Summer.data` and `Summer.economy` are contract surfaces; no hosted backend durably stores player data or runs the economy rail today. | Status words are deliberate: * **Live** means the production path is deployed and documented. * **Scaffold** means a contract, adapter, or tested local surface exists without a complete production path. * **Planned** means creators and agents must not promise the capability. See [Summer SDK](/api-reference/summer-sdk) for contracts and [Submit Your Summer Game for Review](/api-reference/summer-sdk/submission-guide) for the currently deployed submission flow. ## Native multiplayer development The production table above describes the public Summercraft submission and playback path. It is not a statement that multiplayer engine development or restricted staging testing cannot exist. A staging test does not establish general creator access or production availability. Before implementing an online game, identify the environment your installed tools actually support. The public SDK examples on this site describe the scaffolded `SummerGame` / `SummerPlayer` contract and game-only `.pck` submission. They are not an installation or integration guide for a separate native multiplayer development build. Do not copy those stubs into a native runtime and assume the APIs are interchangeable. ### If you have a native development environment Use the documentation shipped with that exact build. Record its version and the target environment before writing integration code. A usable environment must supply: 1. A compatible editor/client and an accessible native API reference or starter project. 2. Creator authentication and a documented publication command for that environment. 3. A matching hosted build policy, resulting build/release identity, and game configuration. 4. An authenticated player launcher for each supported device and a documented join flow. These are setup requirements for an online test, not tasks to solve inside gameplay scripts. This public documentation does not currently provide a self-service native staging installer, credentials, or player launcher. Do not invent their URLs, substitute public PCK submission for a different publication protocol, or require access to an internal expert assistant. Missing setup must be reported as a specific missing input. ### Work that can proceed An agent can inspect installed tools, verify their versions, read the matching API reference, and build the requested gameplay when that integration contract is available. A missing hosted launch prerequisite does not require abandoning all game development. Keep any unfinished online requirement explicit; a local prototype does not complete a request to play with friends on separate devices. Do not silently replace that request with browser gameplay or a shared keyboard. For online acceptance, launch the same recorded release on two authenticated devices, join the same session, and verify shared gameplay and reconnection. Record any lobby capacity limit from the actual configuration; do not promise an unlimited lobby. Until this succeeds, report what was built and the exact remaining launch gate. ## Is the engine app open source? No. The desktop app is free proprietary software right now. If Summer publishes engine source later under a no-competing-engine license, the honest term would be source-available, not open source. For the public canonical page, see [summerengine.com/source-status](https://www.summerengine.com/source-status).