Personnel file
One editor per person: your own master-data fields, sanctions, clearances, leave, training, points and the full timeline of who changed what.
Personnel files, dispatch, training, tasks, applications, inbox and log: everything a faction, a clan or a team moves in a day, in one place. The core is game-agnostic; game-specific modules are switched on when you need them.
Numbers you can count in the product
No tab hopping, no second tool, no spreadsheet on the side. Duty, roster, tasks, requests and the log sit next to each other, and every member opens them with the Discord account they already have.
| Name | Rank | Callsign | Status |
|---|---|---|---|
| MKM. Keller | Chief | LSPD-01 | On duty |
| TVT. Vogel | Sergeant | SWAT-04 | On patrol |
| SAS. Aydin | Officer | LSPD-17 | On leave |
| JBJ. Brandt | Cadet | LSPD-42 | On duty |
| LRL. Roth | Officer | LSPD-23 | Off duty |
Members, ranks, divisions, duty, tasks, exams and a log are the same job whether you run a police faction in GTA roleplay, a Rust clan or a raid team. That job is the core. Everything that only makes sense in one game is a module you switch on or never see.
Made for
Personnel files, ranks, divisions, duty and dispatch, tasks and points, exams, events, inbox, log and undo. Always on, in every plan.
Applications, calendar, API centre, copy templates. Off by default; the owner switches them on per organization and can block any module per role.
The police toolbox and E-MD (EMS administration) are built for GTA roleplay. A Rust clan never sees them, and the next game-specific module lands the same way.
Not a feature list: the day of a faction, with the times at which the platform works by itself. The example is a police faction in GTA roleplay; a Rust clan's day looks the same, only the tasks are named differently.
Every active member draws one random task per category and per division. Automatically, nobody hands them out. If a point boost is running, the raised value is already on the task.
Proof: at least one image
Dispatch shows live who is on duty, which patrols are out and who holds which status. At fixed times everyone is clocked out and every patrol closed: nobody stays on duty for a week.
You release a Discord ID, the person signs in and fills in your form. Accepting hires: the answers land straight in the personnel file, and the blacklist is checked while the ID is typed.
Single choice, free text, images, knockout questions. An instructor grades the free text; until then the attempt is under review. Passed means a record in the file and, if you want, the next rank, automatically.
Clearances run out on their date, sanctions keep their history, every change writes itself into the file timeline. And whoever is affected hears about it in the inbox, not on the grapevine.
Inbox notified
An event with time, place, lead and participants. Points are paid per participation: added later means credited now, removed means exactly those points come back. It is in the calendar by itself.
+15 points per participation
The worker clocks everyone out and closes the patrols. By now the system log holds every operation of the day: who, what, on whom, why. And if one of them was wrong: undo it, alone or all at once.
Event participation settles the past week: a weekly target, exceptions per rank, leave counted pro rata. Whoever missed gets a message, the leadership gets a summary, even when nobody missed.
The core is always on and knows no game. Optional modules are switched on by the organization itself, and off again per role. Game-specific ones are marked.
One editor per person: your own master-data fields, sanctions, clearances, leave, training, points and the full timeline of who changed what.
Live board with status codes, patrols and activities; patrol logs, activity points and a scheduled shift reset.
Exam builder with knockout questions, free-text grading, examiner mode and unlocks; documents, forms and standing orders with read receipts.
Release a Discord ID, let the form be filled in, accept: the answers land in the file, the blacklist warns.
Everyone hears what concerns them; open requests sit in a second tab as things to do. No polling, no e-mail.
A daily draw at 04:00, proof by image, point boosts, a calendar per person and one spendable balance.
Event log with points per participation, statistics, a weekly target with a Monday report, division and personal calendars.
Who did what to whom, when and why. And a single change or everything one account did, taken back in one step.
Ranks, callsigns, nested divisions, confidential units, admin levels and an org chart that draws itself.
Read-only keys over 35 tables for Google Sheets, with a link builder and live preview.
Patient files, assessments, MedKit, diplomas, elections, tickets and a file search across all of it.
Fine catalogue, penalty calculator, Miranda card and four working views for the patrol.
These entries come from the release notes that go out to every user in the app. The same list is in the bell after you sign in.
You are holding your members' data. These are architectural decisions, not settings: there is no switch that turns them off.
Every organization-scoped route resolves the organization and your membership first. No query touches a table without the organization in its WHERE clause. A missing membership answers 404, so not even the existence of an organization leaks.
No passwords to store, leak or reset. The session is a signed token in an HttpOnly cookie that renews itself silently, and a single click invalidates every session you have, everywhere.
Webhook URLs are AES-256-GCM encrypted at rest and must pass a strict allow-list before they are ever called: a submitted URL cannot be aimed at an internal address.
A spreadsheet runs a cell starting with an equals sign as a formula, and rows carry text your members typed. Every text column is neutralised on the way out, including the header row.
People are terminated and archived, content is archived. Where something really is deleted, the log entry that records it is written first, and survives.
No blur on content cards, one static background painted once, cards below the fold that load when you reach them, coalesced requests and compressed responses. It runs on the laptop from the cupboard.
Free carries the core a group runs on: files, roster, dispatch, ranks, leave, the org chart and the log. Crew adds all seven modules. Fraktion adds the two integrations that reach outside the app, Discord role sync and your own domain.
Prices include VAT. Checkout and billing run through Tebex Limited, which sells the plan in its own name and applies the VAT rate of your country. Monthly, cancellable at any time to the end of the paid period; consumers additionally have a 14-day right of withdrawal.
No. Everything runs in the browser and is entered in the app. Duty is started in the app and stored on the server, so nothing has to be installed on your game server and nothing has to be kept running.
Signing in is Discord OAuth: there is no password. On top of that you can map each rank to a Discord role; when a rank changes the role follows automatically, processed on a queue with retries.
You define your own master-data fields, so your columns keep their names. In the other direction the API centre gives you a finished IMPORTDATA line, so an evaluation you already built keeps working: it just pulls from live data now.
You do. Every table is exportable as CSV, TSV or JSON at any time, without asking anybody. Organizations are strictly separated from one another, and the only cross-organization search is limited to your own workspace.
Every organization gets a universal short link on every plan. From Fraktion you can additionally verify your own domain by DNS: the login page then carries your logo and your name, and takes members straight into your organization.
Every change is logged with who, what, when and why. From that log a single change or everything one account did can be taken back, previewed first, in one step, and the undo runs through the same checks as the original action.
German and English. The language follows the browser, can be switched at any time and is remembered per user, error messages included.
Nothing is deleted. The plan falls back to the free limits, so export what you need beforehand: the export is read-only and available on every plan.
No. The core (members, ranks, divisions, duty, tasks, exams, log) knows no game and is what a Rust clan or a raid team uses. Only the police toolbox and E-MD are built for GTA roleplay; they are optional modules a game that does not need them simply never switches on. That is what the modular build is for.
Sign in with Discord, create your organization, invite the first ten. No credit card, no installation, no game server.
Start for free