Docs

Setup is one resource, one key and ten minutes.

How the panel, the agent and the API work, with the code you paste to set them up.

the whole setup

ensure fivedock
set fivedock_key "fda_live_…"

-- then, from any server script:
exports.fivedock:screenshot(source, { folder = '/screens' }, cb)

fda_live_… is the agent key, and it only goes in server.cfg. Every export is described in the agent guide. Scripts and sites that call the HTTP API use an API token, fd_live_…, from the Tokens page instead.

Install the agent

Drop the resource in, paste your key, and upload your first screenshot.

Install the desktop app

Windows, no terminal. Pair the box, pick your server.cfg, back it up with a click.

Install the CLI

One command on Windows or Linux, then pair the box and back it up from your terminal.

Send errors from your app

Install the SDK, mint a logs:write token, and read your errors grouped in the panel.

Upload files yourself

From the panel, from your own uploader, or over the S3 endpoint with rclone and the aws CLI.

Find what lags

Profile the server and your players’ FPS, and get the resources, loops and commands behind the lag.

Upload API reference

Every Fivemanage-compatible address, one-time upload links for NUI, stable links, limits and errors.

Move from Fivemanage

Start here

Paste a read-only key. We copy every file and hand you the list of old link → new link.

There are seven guides so far, with more on the way. If something is missing, ask in Discord.

The agent is open source. It runs on your machine with access to your database, so you get to read it before you trust it: GitHub.