Cloud: what the Bastrel API adds, and what works without it
Bastrel is a resource that runs on your server. The cloud is an optional layer on top of it: the Bastrel API and the panel. This page says what the cloud adds, what it never does, and what still works when it is unreachable.
Status: the API is written; the panel screens are in progress and nothing is deployed or sold yet. The cloud stays inactive in every source and development build and becomes active only in the release package. Plan names, limits and prices are the commercial decision of the Bastrel owner and are not set on this page.
What works without the cloud
Section titled “What works without the cloud”Everything that protects your server runs inside the resource: detection, automatic sanctions, bans at connection, the local ban list, the logs and the in-game alerts. With a valid licence token the resource keeps working fully offline for up to 7 days after its last contact with the API. Without a valid token it detects, logs and keeps bans in force, but only in observe mode (no automatic sanction). Bastrel never stops your server. See licensing for the four states.
What the cloud adds
Section titled “What the cloud adds”| Function | Page |
|---|---|
| A licence token that proves the server belongs to a subscription | licensing |
| Detections and bans sent to the panel, as references only | uplink |
| Settings published from the panel and applied after your approval when they make a detection quieter | remote-config |
| A web panel to read detections, players and bans, lift a ban and manage your staff | panel |
| Your purchase, your rights and your account | panel-rights |
| A documented HTTP API | API reference |
Some functions depend on the plan of the subscription (the features field of the token). A function your plan does not include is not started, and the resource writes it in the console.
What the cloud never does
Section titled “What the cloud never does”- It does not decide a sanction for you. Deterministic detections sanction on your server; heuristic ones only give a score for a human to review. The
aimmodule never bans. - It does not receive raw identifiers: licences, Discord, Steam or FiveM identifiers, hardware tokens and IP addresses become references (HMAC with a key that belongs to your account) before anything leaves the server, and player names are never sent.
- It does not ship code: the resource downloads data (lists, thresholds), signed like the licence token, never scripts. A list or a threshold that would make a detection quieter waits for your approval (
/bas config accept). - It does not hold a secret that your players could read: the licence key and the secret are server convars set with
set, neversetr.
Where the data lives
Section titled “Where the data lives”The resource keeps its own database (your MySQL or MariaDB, see install-sql): bans, detections and staff actions are stored there whether or not the cloud is used. The cloud stores the references and the evidence described in uplink. The retention periods, the roles (who is the controller of which data) and the rights of players are set by the data-protection documents that are still to be written and reviewed by a lawyer before the sale; this page does not replace them.