Everything to know before adding Flitt to your panel

1. What your customers get

Flitt adds advanced statistics, a public page, votes, logs, Discord and security to every game server, right in your panel.

Which games?

Garry's Mod, FiveM and Minecraft (Paper, Spigot, Purpur, BungeeCord, Velocity, Sponge and the other plugin servers).

Which features?

Statistics (peak, average, hours played, new players, busy hours, countries, sessions, next-24-hours forecast, CSV export), monthly PDF reports, public page and listing on the Flitt server list, votes with in-game rewards, logs by category with search, Discord bot and webhooks, backdoor scan (Garry's Mod, FiveM), server networks (proxy, lobby, players across the network).

Where does the customer see it?

In your panel, on native pages: a "Flitt" entry (or your brand name) in the server menu and a page in their account. No iframe, no account to create elsewhere, no redirect.

Which languages?

Customer pages follow the account language: English, French, German, Dutch, Spanish, Polish.

And subusers?

Twelve Flitt permissions are added next to the panel’s own (statistics, reports, public page, votes, logs, integrations, security, settings…) and are given like the others, in Users.

2. Installation, theme and compatibility

Which panels?

Pterodactyl 1.11 and 1.12 (with or without Blueprint) and Pelican. PHP 8.2+ with sodium, the queue worker (pteroq) and the scheduler cron, like any panel. Node.js and Yarn to rebuild the front-end, as for any theme.

How is the extension installed?

One command on the panel server, with your key: it downloads the extension, checks its fingerprint, backs up the panel files it touches, runs the migrations (flitt_* tables only) and rebuilds the front-end. If the build fails, the previous one is put back.

We have a custom theme. Will it break?

No. Flitt's pages are built with your panel and use its components and colours: your theme applies. No colour is hard-coded, and containers carry the flitt-page and flitt-card classes so your theme can target them. The installer adds a few marked lines to 7 files; if your theme changed one of them, it says so and shows the line to add by hand.

Do we get the code?

Yes. The extension ships in clear (PHP, React/TypeScript), readable and documented: you see everything it does and can adapt it to your theme. Updates are signed by Flitt (Ed25519); an older version is always refused.

Your brand?

In Admin > Flitt: a name, an accent colour and a logo replace "Flitt" in the menu, titles and charts of the customer pages.

Updates and uninstall?

A banner in the admin shows a new version, one command installs it (rolled back automatically if it fails); security updates can install themselves. Uninstalling exports the Flitt tables, removes the added lines and puts the panel files back as they were.

3. Activation for your customers and paid option

Who decides a server gets Flitt?

Two agreements. You allow Flitt on the server (create form, server tab, bulk action, or automatically per egg and per node), then your customer turns it on in their server settings. If you prefer, "on from creation" makes your allowance enough.

How do we tie it to our billing (paid option)?

Through your panel's Application API: one call allows or removes Flitt on a server (also by external id), and a server created through the API can start with Flitt allowed. Ready-made modules exist for WHMCS and Paymenter (Flitt sold as a configurable option); Blesta uses the same API.

What is installed on the customer's server?

The small Flitt addon, plugin or resource, written by Wings only in its own folders, each file checked against its fingerprint before it is written. The customer can refuse it. Before each start, Wings writes the server's configuration without calling Flitt: if Flitt does not answer, the server starts anyway.

What if the customer deletes the addon or stops the option?

Every 15 minutes, a reconciliation puts the addon back if it was deleted while Flitt is on, and removes it from servers where Flitt was turned off. Removing your allowance turns Flitt off on that server, nothing else.

When does a server count for you?

A server only counts on a day it ran for at least 30 minutes. A test server on for 10 minutes, a stopped server, an event server open for two days: you only pay for the days really used. Each day is frozen with its proof (minutes online, server by server), visible in your space.

A customer wants to leave with their statistics?

They can transfer their server to their own Flitt account, with its history (one-time code). The other way round, a customer already on Flitt can bring their server to you without losing anything.

4. Cloud or Edge: where the data is

You choose per node or per server. The features are the same for your customers.

Cloud?

The servers' data is kept by Flitt, in the European Union. Nothing more to install.

Edge?

The data stays with you: a light binary (Linux or Windows), installed with one command on your machines, keeps it and answers the addons. Flitt only gets what it needs to know which servers are running; your panel reads logs straight from your Edge. It is the cheapest mode.

What is stored?

Players and their sessions, logs (when the module is on) and attendance statistics. Never your customers' game files, configurations or worlds.

Where does the Edge keep the data?

You choose per group: in one database on your side (file, MySQL or PostgreSQL), or in each server. In the second case, each server keeps its data in a .flitt folder of its own volume, encrypted by the node's Edge with a key your customer never has: they can neither read nor change it, the folder is hidden from the file manager and SFTP, follows the server in its backups and node transfers, and goes away with it. It takes a few MB of the server's disk. You can change your mind: the Edges move the data by themselves.

Several machines?

Edge instances are arranged in groups, behind one address; add as many as you want with a registration code. A server can change group with its whole history (undo within 7 days).

How long is history kept?

You choose it in your panel: from 7 days to unlimited. In Cloud, it is kept for one year at most.

5. Billing

One invoice a month, computed by the day. Your customers never pay Flitt: you bill them yourself, at the price you want.

How is it computed?

Per server and per day of use (license renewed and 30 minutes online that day), at the price of your offer, different for Cloud and Edge; your offer may set a monthly minimum. An Edge server whose collection Flitt had to take over (Edge unreachable) counts at the Cloud price for those days. Your space and the Billing tab of the panel admin show the month's usage, the estimate of the next invoice and your invoices.

When do we pay?

On the 1st of each month, for the month that ended, charged automatically to your payment method. If the month's usage goes over a threshold, the part already reached is invoiced in advance and deducted from the invoice of the 1st: you never pay twice.

Why a cap at the start?

Against fraud, a new organization can allow a limited number of servers until its first monthly invoice is paid. Servers already allowed keep going; only new ones wait. The cap can be raised sooner on request.

Can we pay manually?

Yes, for trusted hosts, on Flitt's decision: one invoice on the 1st for the month that ended, paid by bank transfer or card within a delay agreed with you (7 business days by default). You are told by e-mail 10, 5 and 1 day before it is issued (with the estimate), on the day it is issued, then the day before it is due. An invoice unpaid at the due date pauses Flitt until it is settled.

And if an invoice is unpaid?

Your game servers are never stopped. With automatic payment, after 7 days, Flitt licenses are no longer renewed: Flitt's features pause on your servers. The organization is suspended after 30 days, then closed 30 days later. Everything resumes on payment.

Commitment?

None, and no access fee. You can cancel at any time from your space; it takes effect at the end of the month. Prices exclude taxes; any VAT is set out in the terms.

6. Resale: arguments for your customers

You set your price freely: paid option, included in a range, free on big plans. A few arguments that work:

"Know who plays on your server"

Player peak, busy hours, countries, loyalty, new players: what you need to decide when to run an event or an update.

"Bring players in"

A polished public page, a listing on the Flitt server list, votes with in-game rewards and a Discord bot showing the server live.

"Keep your server clean"

The backdoor scan (Garry's Mod, FiveM) checks every script and explains every risk found, with file and line. The customer's code never leaves your panel.

"Keep proof"

Logs by category, with search, to settle disputes between players or staff.

"It's all in your panel"

Nothing to install, no account to create: one switch in the server settings.

"Cheaper than on your own"

You can offer it below Flitt's public price for a single server: a real reason to take the option with you.

7. Security and personal data

Secrets?

Organization key, the panel's signing key and server keys are encrypted with your panel's key (APP_KEY) and never sent to a browser. Every request from the panel to Flitt is signed (Ed25519).

The customer's browser?

It only talks to your panel, behind its session, 2FA and subuser permissions; the panel calls Flitt.

Data on the Edge?

Every document is encrypted (AES-256-GCM) before it is written; the key never leaves your machine. With storage in each server, the files themselves are encrypted too, with a key of their own for each server.

GDPR?

For the data of players and of your customers, you are the controller and Flitt is a processor (article 28): Flitt only processes it to provide the service, reports any breach within 72 hours and deletes or returns it at the end of the contract. Hosted in the European Union. A data processing agreement is provided on request.

To go further

The Security page details encryption, signatures, retention periods and the addon's source code.

8. How the request goes

1. You send the request

A Flitt account, then the host form: company, country, panels, number of servers, interest in Edge.

2. We review it by hand

We may come back to you for details. A 30-day sandbox (5 servers, no billing) can be opened for you to try everything on your panel.

3. You receive your offer by e-mail

With your prices, fitted to your fleet. Nothing is billed before you accept it.

4. You accept and install

Accept the terms, add a payment method, then one command for the extension (and one per Edge if you want some). The guide and downloads are in your space.

5. Your customers turn it on

You allow servers (or let the default settings do it), your customers click a switch. Support stays reachable from your space.