Release Management
Versioned builds, branches and controlled updates for stable, patch and hotfix releases.
Custom game launcher platform
Build your custom game launcher.
Ship builds, updates and player access through a launcher that looks and feels like your game.
No credit card · Versioned builds · Custom branding
Product viewControl builds, branches and your launcher from one place.
Engine independent
Built for the tools game teams already use.
LauncherForge stays engine independent while fitting into the development stack around your game.
Unreal EngineNative game integration
UnityRuntime integration
GodotEngine-independent workflow
LauncherForge CLIAutomated build delivery
One platform
From game build to player launch.
LauncherForge connects the infrastructure around your launcher without forcing every part of the experience into the same tool.
Use the native launcher for delivery and presentation, then connect your game through the CLI, runtime authentication and engine integrations.
Launcher Experience
Branded native launchers with custom templates, news, patch notes and game-specific presentation.
Player Access
Player accounts, license keys, private branches and short-lived launch authentication.
Game Distribution
Deliver game builds and updates through cloud infrastructure designed around launcher workflows.
Developer Tooling
CLI automation, APIs and integrations for Unreal Engine, Unity and Godot.
Connected flowBuild→Branch→Launcher→Player
One repeatable workflow
From player login to production release, every handoff is explicit.
The workflow connects your dashboard, launcher, game runtime and deployment tooling instead of leaving them as isolated pieces.
Create the launcher and connect your game.
Configure branding, game metadata, branches, access rules and the launcher experience.
Authenticate the player before the game starts.
The launcher handles login and starts the game with a short-lived launch token.
Publish a versioned build with the CLI.
Scan files, calculate hashes, deduplicate uploads and route the release to the intended branch.
Manage access, updates and support.
Control testers, patch notes, analytics, team roles and player support from one workspace.
Launcher templates
Pick a direction. Then make it unmistakably yours.
The templates are not screenshots or static themes. They are starting systems for a real native launcher, with the same release, auth and update layer underneath.
Native launcher preview
Built for the native runtimeAlderon Classic
Preview01J8M6GQ
PV
Maintenance Notice
Servers will be under maintenance soon. Some services may be unavailable.
Visual identityLogo, colors, typography and background
Launcher contentNavigation, news, patch notes and community
Same infrastructureBuild delivery, branches, auth and updates stay connected
Want a launcher that does not look like either template?
Create your launcherUse a template as the base, then replace the visual language and structure while LauncherForge keeps the native release system underneath.
Ecosystem compatibility
Built for the tools game teams already use.
LauncherForge is engine independent while providing purpose-built integration paths for game runtimes, storage and community workflows.
Product names and logos are trademarks of their respective owners. Compatibility does not imply endorsement or partnership.
Game authentication
Customize the launcher login, then pass a secure session into the game.
The launcher owns the player-facing authentication experience. Your game receives a short-lived launch session through the integration plugin and can read id, email and valid without rebuilding the complete auth flow.
1
Player signs in through your branded launcher
Use email and password, OAuth, password recovery and custom login screens.
2
Launcher requests a short-lived launch token
The token is scoped to the launcher, player and selected game session.
3
The launcher starts the packaged game
The launch token is passed as a startup argument instead of storing permanent credentials in the game.
4
The plugin validates and exposes the session
Game code reads id, email and valid and decides how to initialize the authenticated player.
LauncherForge.exe --launchToken=<short-lived-token>
// The game receives only the launch session it needs.
// Exposed values: id, email, valid.Unreal Engine plugin on Fab
Give Unreal projects a direct integration path for validating the launch session and reading authenticated player data.
Open LauncherForge on Fab →⌘Integration documentation
Keep setup, packaging, authentication and release instructions available to the entire team.
docs.launcherforge.io →UI
Authentication that matches your brand
Control the login artwork, text, OAuth entry points, recovery flow and launcher navigation without rebuilding the game integration.
OAuthEmailOTPBranding
Plugins and developer tools
A real toolchain for deployment, integration and operations.
Use purpose-built tools instead of copying files manually or wiring every release and authentication step from scratch.
launcherforge.exe / production
LAUNCHERFORGE CLOUD — CLI
Cloud CLI v1.0.0 Build 1 — Production
√ Logged in as studio@northbyte.dev | Plan: STUDIO
$ launcherforge deploy --game-id 42 --branch production
· scanning files and calculating SHA-256 hashes
√ 84,231 files scanned | 12.8 GB
√ unchanged objects reused from storage
√ version 0.9.5 published successfully
Reuse unchanged files and upload only the objects required by the target build.
Separate production, beta, nightly and private tester delivery without duplicating the launcher.
Connect Discord support, release visibility and player-facing operational data.
Pricing based on real operating capacity
Plans for indie games, studios and growing communities.
Clear plans, real limits and enough room to grow. Start small, then unlock more games, more team members and more release capacity as your project expands.
Try the workflow
Free
For validating the launcher and release process.
$0/ month
Games1
Members1
Storage1 GB
Branches1
- ✓1 launcher
- ✓1 game
- ✓1 team member
- ✓1 GB storage
- ✓30 GB bandwidth
Solo developers
Indie
For independent games releasing consistently.
$9.99/ month
Games1
Members2
Storage10 GB
Branches3
- ✓1 launcher
- ✓1 game
- ✓2 team members
- ✓10 GB storage
- ✓500 GB bandwidth
Release-heavy teamsMost balanced
Studio
For teams operating QA, betas and frequent updates.
$34.99/ month
Games3
Members4
Storage40 GB
Branches10
- ✓1 launcher
- ✓3 games
- ✓4 team members
- ✓40 GB storage
- ✓1 TB bandwidth
Integrations
Business
For advanced automation and external operations.
$69.99/ month
Games5
Members8
Storage80 GB
Branches20
- ✓2 launchers
- ✓5 games
- ✓8 team members
- ✓80 GB storage
- ✓2 TB bandwidth
FLEX
Flex
A flexible base plan designed to grow through additional resources.
$13.99/ month
Games1
Members2
Storage10 GB
Branches3
- ✓1 launcher
- ✓1 game
- ✓2 team members
- ✓10 GB storage
- ✓500 GB bandwidth
Explore LauncherForge
Go deeper into each part of the game launcher stack.
Dedicated guides explain how LauncherForge handles launcher creation, patching, automatic updates, engine integration and player authentication.
SEO / PRODUCT
Game Launcher Creator
Build a branded launcher around your game, releases and player access.
Explore →SEO / PRODUCTGame Patcher
Publish traceable, versioned game patches with hash-based scanning.
Explore →SEO / PRODUCTGame Auto Updater
Keep installed games aligned with the release assigned to each branch.
Explore →SEO / PRODUCTUnreal Engine Game Launcher
Connect packaged Unreal builds, updates and validated launch sessions.
Explore →SEO / PRODUCTUnity Game Launcher
Distribute exported Unity builds through a branded launcher workflow.
Explore →SEO / PRODUCTGame Launcher Authentication
Keep credentials in the launcher and validate short-lived sessions in the game.
Explore →Before you publish
Practical questions about operating LauncherForge.
Clear answers about distribution limits, private testing, game authentication and launcher customization.
Need implementation details?docs.launcherforge.io →
No. LauncherForge plans are based on operational capacity such as storage, bandwidth, games, branches, team members and enabled platform features. Player installations are not treated as an artificial commercial limit.
// Build the release layer once
Give your studio a launcher that looks custom and operates like infrastructure.
Connect authentication, release delivery, plugins, CLI workflows, documentation and player support in one product surface.