Skip to content
Browse documentation
DocsIntegrations & publishing
GuideUpdated 2 min readView Markdown

Store publishing

A public browser game, a self-publishing release kit and assisted publishing are separate paths. Start with publishing and export if you want a shareable EoC play link.

Self-publishing release kits

Both active Studio and Studio Team plans can access supported release kits for Steam, Apple App Store and Epic Games Store. These kits provide configuration, a release manifest, instructions and a local upload script. They use your publisher account and do not contain store credentials.

  1. Choose the target store and enter its requested app/product identifiers and version.
  2. Download the release kit and read its instructions.
  3. Build a compatible native game from your source, using the appropriate engine or wrapper. A browser-source ZIP alone is not an executable or signed app archive.
  4. Test on the target devices and prepare your artwork, rights information and content disclosures.
  5. Configure the official upload tool and credentials locally, run the kit's upload procedure, and verify the outcome in your publisher portal.
  6. Complete the store listing and its submission/review process.

EoC prepares the kit; it does not compile and sign a native binary in your browser or automatically approve a store listing. You manage the store account, fees and signing credentials. Requirements can change, so follow the kit and the store's current guidance.

Assisted publishing: requests are open

Publish with EoC accepts access requests from eligible verified accounts, including free accounts. Joining the request list does not publish your game, guarantee an invitation or accept a publishing contract.

The intended later workflow is an individually invited pilot for selected Steam and Apple App Store projects. It requires EoC's publisher setup and operating capacity, a tested native build, rights/content review, and a separate agreement covering commercial terms and responsibilities. Store review remains the store's decision.

Check your request page for its current status. This initial request workflow does not send automatic email notifications. New intake or progression may be paused. Eligible early requests can be withdrawn through the request page; contact EoC about a project already under review or distribution.

Prepare a useful request

Explain the game, its target store and current playable state. Be ready to provide build/artwork information and the relevant AI/content and license disclosures when invited. Do not submit credentials or private signed download links. Arrange a suitable private transfer before sharing confidential release materials.

No release date, revenue share or publishing fee is implied by joining the list. Review the eventual project agreement and applicable source licenses separately.

Need a hand with this workflow? Find help or contact support.