// division 01

Global Game Distribution & Platform Publishing

We take a finished or near-finished build and carry it through store onboarding, page setup, build submission, review cycles and release-day logistics on the platforms a title is a fit for.

Storefront publishing is mostly paperwork, formats and deadlines, and it is where small teams lose months. We run the account and submission work under a written publishing agreement, so the developer keeps building and someone else keeps the calendar.

What the work covers

  • Store account and page setup, including capsule art specifications, descriptions and system requirements
  • Build submission, review-feedback handling and resubmission until a build passes platform technical requirements
  • Depot, branch and build management for pre-release testing rounds
  • Release scheduling, regional availability and pricing configuration in the storefront
  • Post-launch patch and hotfix pipelines

Questions developers ask

Which platforms do you submit to?

PC storefronts, the major console ecosystems and mobile app stores. The specific list for a title depends on the engine, the input model, the content rating position and whether the platform holder approves the developer account. We put the agreed list in the publishing agreement rather than advertising it up front.

Do you take over our store account?

Only if that is what the agreement says. Both models are workable: we publish under our own account, or we operate yours under a written mandate. The second keeps the storefront relationship with the developer, which many teams prefer.

No outcome is promised. Store acceptance is decided by the platform holder, age ratings are issued by rating boards, and editorial and creator coverage is an independent decision. We commit to the work described in the agreement and report what actually happened. Platform, storefront, engine and rating-board names are used descriptively to identify the destinations we submit builds to and the tools we work in. All trademarks belong to their respective owners. Their use here is not a claim of partnership, endorsement, certification or approval.