Run the world behind your game.

Start with a generated application ​

You do not need to understand every Elura crate before running a server. Generate an application first, then learn each piece while changing real code:

cargo install elura-cli
mkdir my-game && cd my-game
elura init all --dir .

The generator creates editable application code, local configuration, Docker files, and Kubernetes manifests. Continue with the 10-minute quick start to configure development secrets and launch both processes.

The mental model ​

Player client ──> Gateway ──> World ──> your typed handler
                  sessions     routing   game rules

• Gateway owns public connections, authentication, sessions, and routing.
• World executes authenticated game commands and middleware.
• Your application owns routes, game rules, configuration, persistence, and deployment choices.

That separation stays the same whether you run locally, as a monolith, or across multiple Kubernetes nodes. Read the architecture overview when you want the full picture.

Choose your next step ​