Early Access Overview

Sculk FiveM is in early access. This page is the honest version of what that means, so you can decide whether a founding licence makes sense for your community.

What you get today

• A founding licence key, issued instantly at checkout, at the locked early-access price. It never needs to be repurchased — the same key activates the build when it ships.
• The rollout guides in this documentation section: policy planning, event inventory, entity incident playbooks, and staff review workflows. They are designed so your server is ready on day one of the rollout.
• Priority support. Early-access questions get a tracked ticket and a real reply — see FiveM support.

What ships at rollout

The Sculk FiveM build itself: the server-side resource implementing event policy enforcement, entity and world integrity incidents, player-state signals, and the staff incident stream. Licence holders are emailed at their order address the moment the rollout opens.

We deliberately do not publish a ship date or performance claims here. When the build ships, the benchmark methodology used for Minecraft — measured numbers or no numbers — applies to FiveM too.

The protection model, in one paragraph

Sculk FiveM is server-side and policy-first. It watches privileged server events, entity and world changes, resource trust signals, and player state. Anything outside the policy you define becomes an incident with a timeline staff can read — observed, correlated, contained per your rules, and reviewed by humans. Players install nothing, and nothing is punished that your configuration didn't explicitly choose to punish.

Who early access is for

Buy a founding licence if you run a live FiveM community, you want staff-reviewable anticheat rather than a black-box ban bot, and you're willing to spend a little time now preparing policy so the rollout lands cleanly. If you'd rather wait for the public release and its final pricing, that's a legitimate choice — the guides here are readable either way.

Next steps

1. Read Rollout Planning — the order of operations from purchase to live enforcement.
2. Work through the Event Policy Worksheet with whoever knows your server's resources best.
3. Set up your staff workflow with the Staff Review Workflow guide.