Launcher
Instances, versions, loaders, runtimes, content, migration, repair and release management.
CONNECTED PLATFORM
One ecosystem.
Clear boundaries.
Leviathan is being built as more than a launcher. The platform connects identity, profiles, support, migration, discovery, community and future services without mixing security-sensitive systems into public surfaces.
Leviathan Platform
Connected, not tangled.
Each subsystem has a clear role.
PLATFORM COREIdentity + services
Launcher · Client · Web · Support
IDENTITYVerified
PRIVACYControlled
STATUSVisible
PLATFORM LAYERS
Everything has a place.
The goal is a coherent experience where the launcher, client, website and community tools share context without becoming one giant monolith.
Client
Performance, HUD profiles, accessibility, cosmetics and connected in-game features.
Identity
Leviathan account, verified Minecraft ownership, profile continuity and privacy controls.
Support
Error codes, diagnostics, private tickets, public bugs, known issues and lifecycle updates.
Discovery
Profiles, servers, content, status, news and useful platform search.
Community
Discord, creators, localization, feedback and contribution pathways.
VERIFIED IDENTITY
Prove ownership without exposing secrets.
Account linking is planned around the user’s own Microsoft and Minecraft authentication flow. Passwords and service tokens do not belong in Discord or public profile pages.
1LinkStart from Leviathan with a short-lived challenge.
2VerifyConfirm Minecraft ownership and stable UUID identity.
3ControlManage visibility, unlinking and safe transfer flows.
Identity recordPrivate by default
✓
Minecraft UUIDStable profile identity
Verified✓
Ownership methodRecorded without password storage
Safe◫
Public profileUser-controlled visibility
OptionalOPERATIONS
The boring parts should be excellent.
Updates, telemetry, support, diagnostics and service health are part of the product experience, not afterthoughts.
Release engineering
Versioned releases, checksums, staged channels, rollback and transparent changelogs.
Diagnostics
Stable error codes plus separate crash and correlation IDs with original errors preserved.
Telemetry governance
Collect useful product signals with purpose, retention and privacy boundaries instead of uncontrolled event sprawl.
Status
Make development state, incidents and service availability visible instead of hiding failures behind generic messages.
COMMUNITY LAYER
Players should know where to go.
Feedback, bugs, support, localization and creator participation need separate workflows that still connect back to the same Leviathan identity.
See where the platform is going.
Leviathan is being built in layers. The roadmap separates current work from future concepts.