> ## Documentation Index
> Fetch the complete documentation index at: https://docs.arcane-powered.com/sdk/llms.txt
> Use this file to discover all available pages before exploring further.

# Publish your game

> From a studio account to a game players can buy: sign-up, approval, payouts, builds, review and pricing.

This page walks a studio through everything between "we want to be on Arcane Powered" and "players can buy our game", in order. Everything happens in the **publisher portal**, at [portal.arcane-powered.com](https://portal.arcane-powered.com); each step links to the page that covers it in detail. Integrating the SDK is optional: a game without it still launches, and Arcane tracks its playtime from the process. See [Get the SDK](https://docs.arcane-powered.com/sdk/get-the-sdk.md) when you want achievements, friends, lobbies or ownership checks.

**1. Create your studio**

Sign in with an Arcane account, then create your studio. Pick what you apply as: **studio** (you make games), **publisher** (you publish other studios' games) or **both**. A publisher also describes what it does, its website and the games it already published. See [Studio and team](https://docs.arcane-powered.com/sdk/portal/studio.md).

Creating a studio means accepting the studio terms, shown in the sign-up form. The version you accepted, the date and the account that accepted are recorded.

**2. Wait for Arcane to approve the studio**

A new studio starts **pending**. While it waits you can already set up payouts, fill in your profile, invite your team and browse the catalogue. You cannot create titles, upload builds or publish a store page until an Arcane staff member approves the studio. If something is missing, the note they leave tells you what.

**3. Set up payouts**

**Payments** opens a Stripe Connect onboarding. Stripe asks for your company, a bank account and an identity check. Until Stripe says the account is ready, sales still happen but your share cannot be transferred, so do this first.

**4. Invite your team**

**Settings → Studio Team** invites people by email. Studio roles are **admin**, **finance** and **member**; members then get per-game presets (release manager, store manager, developer, QA, analyst, community manager, viewer). Everyone on a game's team gets a free team copy to play it before release.

**5. Create the title and its store page**

**Games → New title.** Fill in the store page: description, cover, screenshots, trailer, tags and system requirements, then set the price on the **Pricing** tab. Add DLCs and editions (bundles of the game and its DLCs) from the same workspace. See [Store page](https://docs.arcane-powered.com/sdk/portal/store-page.md).

Every game also declares how it used **generative AI** (LLMs, image, music and voice generators; upscaling and ordinary tools do not count), on the **Generative AI** tab. Players see a badge built from it. A false declaration gets the game refused or removed.

**6. Upload a build**

The **Builds** tab uploads Windows, macOS and Linux builds, an HTML5 build players run in their browser, or an Android `.apk`. Uploads resume after a dropped connection. Builds can be published at once, kept as drafts or scheduled. See [Builds](https://docs.arcane-powered.com/sdk/portal/builds.md).

After the first build, you can upload from a terminal or a CI job with a studio API key: see [From the command line or CI](https://docs.arcane-powered.com/sdk/portal/builds.md#from-the-command-line-or-ci).

Every build is scanned for malware before it is published. A build that fails the scan is refused and never reaches players.

**7. Submit the game for review**

Every game's **first release** is reviewed by Arcane before players can see it. **Submit for review** checks that the store page has a description, a cover, screenshots, a price, system requirements, a published build and an AI declaration, then freezes a copy of the page for the reviewer. Staff play the game in the desktop app and approve it, or send it back with a note.

Once approved, you choose when it goes live. See [Release review](https://docs.arcane-powered.com/sdk/portal/review.md).

## Updates after release

How much Arcane looks at your updates depends on your studio's **trust level**, which Arcane sets and may change per game:

| Level | What happens to an update |
| - | - |
| 1 — Review all (every new studio) | Held until Arcane releases it to players |
| 2 — Spot checks | Goes live at once; one update in five is checked afterwards |
| 3 — Free | Goes live at once; only new games are reviewed |

Store-page edits on a live game are not reviewed. Arcane can take a game down at any level when it breaks the studio terms.

## Where your game is sold

Details in [Storefronts and pricing](https://docs.arcane-powered.com/sdk/portal/storefronts.md).

Arcane has two storefronts. While Discovery is in beta, the launcher shows Discovery in place of the Store, and the Store reads as coming soon.

* **Discovery**, for small independent games. A team of 15 people or fewer can join from the title's **Discovery** tab. You choose Arcane's share of each sale (10 % by default, anywhere from 0 to 100 %), and the portal simulates what you receive on a 1, 2 or 5 € copy. A copy bought on Discovery can **never be resold**. You can add reward tiers, a funding goal, pay-what-you-want on a paid game, or donations on a free one. Once the game sells well enough, Arcane offers to move it to the Store; you decide.
* **The Store**, for everything else. Arcane keeps **15 %** of each sale before tax, **10 %** for a game that came from Discovery. A different rate can be negotiated for a studio or a game. Copies bought on the Store will be resellable by players on the marketplace, which is planned for the first quarter of 2027.

In both cases Arcane collects the payment and the tax, and your share is transferred to your Stripe account. A free game is never "bought": players add it to their library.

## Other tools in the portal

Details in [Selling tools](https://docs.arcane-powered.com/sdk/portal/selling-tools.md).

* **Activation keys** for press, giveaways, bundles or retail. A key copy can never be resold.
* **Pre-orders** and **demo builds**.
* **Free periods**: let players play the full game for free for a while.
* **Bundles** with other studios' games, and discounts for owners of your other games.
* **Devlogs**: news sent to everyone who owns or follows the game, optionally by email.
* **Revenue sharing** and **credits** with partner studios (publisher, developer, distributor), each paid directly by Stripe.
* **Analytics**: sales, players, wishlists and where the game appears on the store.

## Questions

Reply to the Arcane team member who contacted you.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.