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

# Introducction

> Learn how LauncherForge helps game developers create, publish, and manage professional desktop launchers from one platform.

# Welcome to LauncherForge

LauncherForge is a platform for game developers and studios that want to create, publish, and manage professional desktop launchers without building the entire distribution infrastructure from scratch.

Use LauncherForge to manage your launcher, games, releases, branches, player access, branding, and distribution workflow from a centralized workspace.

<Info>
  This documentation uses English as its default language. You can switch to Spanish from the language selector.
</Info>

## What you can build

With LauncherForge, you can:

* Create a branded launcher for your game or studio.
* Publish games and organize releases by branch.
* Upload stable releases, patches, and hotfixes.
* Manage game versions and release notes.
* Authenticate players who launch a game through LauncherForge.
* Customize the launcher experience with supported templates.
* Monitor storage, bandwidth, and workspace limits according to your plan.

## Who LauncherForge is for

LauncherForge is designed for:

* Independent game developers publishing their first commercial game.
* Small teams that need a professional release and update workflow.
* Studios managing multiple games, launchers, team members, or private branches.
* Developers integrating launcher authentication with Unreal Engine or Unity.

## How it works

<Steps>
  <Step title="Create your workspace">
    Your workspace contains your launchers, games, team members, subscription, and usage limits.
  </Step>

  <Step title="Configure a launcher">
    Choose a template, add your branding, and configure the launcher experience presented to your players.
  </Step>

  <Step title="Add a game">
    Create the game entry, define its branches, and configure the information required by the launcher.
  </Step>

  <Step title="Deploy a release">
    Use the LauncherForge CLI to authenticate, scan your packaged build, and publish a version to the selected branch.
  </Step>
</Steps>

## Core concepts

<CardGroup cols={2}>
  <Card title="Workspace" icon="briefcase">
    The main container for launchers, games, members, billing, and plan limits.
  </Card>

  <Card title="Launcher" icon="rocket">
    The desktop application your players use to discover, install, update, and launch your games.
  </Card>

  <Card title="Game" icon="gamepad">
    A product distributed through a launcher, including its metadata, branches, builds, and releases.
  </Card>

  <Card title="Branch" icon="code-branch">
    A release channel such as stable, beta, testing, or a private environment.
  </Card>

  <Card title="Build" icon="box-archive">
    A packaged set of game files uploaded and processed for distribution.
  </Card>

  <Card title="Release" icon="tag">
    A version published to a branch with its type, version number, and changelog.
  </Card>
</CardGroup>

## Start building

Follow the [Quickstart](/quickstart) to create your first launcher, add a game, and deploy an initial release.