A framework for the next era of FiveM.

Typed Lua APIs, a real PostgreSQL ORM, unified state, and server-authoritative anticheat. Built from scratch for teams that have outgrown legacy patterns.

Get startedJoin Community

Every surface, built on purpose.

Every layer designed to work with the others. No legacy baggage, no inherited debt from frameworks that just grew over time.

KuraDB. Schemas in TypeScript, versioned migrations, generated Lua types. Queries compose from typed operators, not raw SQL strings.

Orbit. Players, logs, moderation, and incident response in one live web console your team actually keeps open.

Kura State. One typed surface for memory, statebags, and the database. Health, money, jobs, inventory: same interface everywhere.

Modules. Typed APIs between modules. No shared globals, no guessing what another resource exports.

Anticheat. Designed server-authoritative from the ground up. The client never holds authority it shouldn't have.

Kura UI. Beautiful UI components designed for FiveM, with a runtime that handles the hard parts.

Why Kura exists

Most FiveM frameworks
were built for a simpler time.

Kura starts over with a single goal: make the safe path the easy path. No invisible side effects, no mystery state, no SQL where it doesn't belong.

Legacy

Patterns that keep old frameworks fragile.

  1. 01

    Raw SQL stitched into script logic

  2. 02

    A giant mutable player object passed everywhere

  3. 03

    Critical logic hidden behind client events

  4. 04

    A database schema nobody owns or fully understands

  5. 05

    State scattered across memory, statebags, and DB

Kura

The safe path is built into the architecture.

  1. 01

    A typed ORM with generated Lua types and versioned migrations

  2. 02

    One state surface, consistent wherever it lives

  3. 03

    Server-authoritative by default. No exceptions.

  4. 04

    A schema defined in code, not discovered in prod

  5. 05

    No loose events. Modules define what they accept

Numbers that stay quiet under load.

Estimated targets from development builds, not verified production data. We'll update these as Kura ships and real numbers come in.

Server resmon

full framework tick across all active modules

<0.7ms

Client resmon

complete client framework cost per frame

<0.5ms

Memory usage

across production deployments

~40MB

DB query latency

KuraDB to PostgreSQL execution, full round-trip

~4ms

From zero to server
in minutes.

You've spent enough time fighting your framework. Kura gets out of your way from minute one.

recipe.yamlhttps://raw.githubusercontent.com/projectkura/txAdminRecipe/main/kura.yaml
  1. 01

    Open txAdmin

    Start the server setup wizard and choose Remote URL Template as your deployment type.

  2. 02

    Paste the recipe URL

    Drop in the Kura recipe and let the wizard fetch every module in order.

  3. 03

    Deploy

    Your server spins up with everything configured. Follow the docs to take it further.

Read the docsRecipe source

Build the server you've always wanted.

Spin up Kura in minutes and start building. The docs have everything your team needs to hit the ground running.

Get startedView on GitHub