Public guide
Product status terminology, launcher and client boundaries, authentication, installation, instances, runtimes, Cast TV, developer tooling and troubleshooting.
Open guide →DOCUMENTATION
One public map for the Leviathan ecosystem.
Launcher guides, authentication, API contracts, SDKs, integrations, server tools, troubleshooting, security, policies and release information in one place.
DOCUMENTATION MAP
Start with the area you need.
Website pages provide the public navigation layer. Canonical technical source documents remain in the public GitHub repositories so version history and review stay visible.
Launcher documentation
Architecture, authentication, development, installation, FAQ, release policy and troubleshooting for the Leviathan Launcher.
Browse launcher docs →API documentation
Public-safe API contracts, lifecycle expectations and developer-facing integration guidance.
Open API Docs →SDK and examples
Developer SDK surface, examples and public integration patterns as those interfaces become available.
Developer resources →Security and privacy
Security reporting, privacy, terms, cookies, authentication policy, Minecraft compliance and third-party notices.
Policies and security →Support and status
Troubleshooting, release policy, service status and public support routes.
Open Support Center →LAUNCHER
Launcher reference library.
The public launcher repository contains the main product documentation set. These documents describe public-safe behavior and development boundaries, not a guarantee that every documented feature is publicly released.
Architecture
Launcher structure, component boundaries and public-safe architecture.
Read Architecture →Authentication
Microsoft, Xbox, XSTS and Minecraft Services flow, ownership checks and authentication constraints.
Read Authentication →Development
Development setup, expectations and contributor-facing launcher guidance.
Read Development →Installation
Current installation status and boundaries for builds still in private development.
Read Installation →FAQ
Common product, access, authentication, compatibility and development questions.
Read FAQ →Troubleshooting
Diagnostics, logs, error context and safe troubleshooting guidance.
Read Troubleshooting →Release policy
Release status, validation expectations and how public availability is communicated.
Read Release Policy →Roadmap
Public direction, milestones and planned areas.
Read Roadmap →Changelog
Public repository change history for launcher development.
Read Changelog →DEVELOPERS
Developer and integration resources.
These public repositories form the developer-facing documentation network around Leviathan.
API Docs
Public API lifecycle, contracts and integration expectations.
Open repository →SDK
Public SDK documentation and future supported client interfaces.
Open repository →Integrations
Discord, webhooks, plugins and third-party adapter boundaries.
Open repository →Examples
Public examples and reference patterns for supported developer workflows.
Open repository →Server Tools
Minecraft server utilities, plugins and public server-side tooling documentation.
Open repository →Status
Public service and development status resources.
Open repository →POLICIES AND SECURITY
Public rules, privacy and security boundaries.
The website now provides first-party policy URLs for account and Google sign-in. The launcher repository remains the canonical source for additional project policy and compliance documents.
Privacy Policy
Website accounts, Google sign-in, Microsoft/Minecraft linking, sessions and data handling.
Read Privacy Policy →Terms of Service
Account use, authentication providers, acceptable use and service boundaries.
Read Terms →Cookie Policy
Essential session and OAuth cookies used by Leviathan account services.
Read Cookie Policy →Security
Security reporting, disclosure expectations and safe handling guidance.
Open Security →Minecraft compliance
Public documentation covering Minecraft-related product and authentication boundaries.
Read Compliance →Authentication and AppID policy
Rules for Leviathan authentication registrations and supported identity flows.
Read Policy →Third-party notices
Notices and attribution for third-party software and services.
Read Notices →Trademarks
Brand and trademark guidance for Leviathan and third-party names.
Read Trademarks →Code of Conduct
Expected standards for public collaboration and community participation.
Read Code of Conduct →PUBLIC BOUNDARY
Public docs do not expose private infrastructure.
Credentials, tokens, provider secrets, private endpoints, internal hostnames, private database details, payment secrets and sensitive security implementation details remain private. Public documentation can explain supported behavior and architecture without publishing material that weakens the platform.
Need an answer instead of a reference?
Use the Support Center for troubleshooting, account help and issue routing.