Operations infrastructure for Roblox
Track your staff, rank people, pay them automatically.
Hours in. Ranks and payroll out.
- No account cookie for ranking
- Immutable audit log
- Built for Roblox groups
Platform
Everything a serious community runs on, in one console.
Every module is off until you add it, so a small group is not handed the whole catalogue on day one. Rostack replaces the patchwork of ranking bots, Discord webhooks and spreadsheets with one system of record that can show its work.
Activity tracking
A module you drop into your game reports minutes played, messages sent and idle time for every staff member. Nothing is self-reported, and a retried report overwrites rather than counting twice, because these numbers decide who gets paid.
Sessions and shifts
Trainings, shifts and events your staff claim, host and take a register for. Slots are claimed in a transaction, so two people cannot take the same one, and every attendee is marked passed or failed with a note.
Payroll from tracked work
Turn the hours you measured into a payout run: everyone over quota, everyone who hosted, at your rates. The preview shows the arithmetic that put each person on the list, and the run still needs two people to approve it before a Robux moves.
Ranking that follows the work
Rules are data: promote on activity, tenure, quota or application outcome. Every run is previewed before it touches Roblox and capped, so a bad rule cannot empty your hierarchy. Rank 255 is never assignable.
Staff, roles and conduct
Staff are the people in the Roblox roles you nominate, tracked whether or not they ever sign in. Permissions map to those roles, so a demotion in Roblox removes access here. Applications, time off, handbook and conduct records included.
Audit log and drift
Every privileged action is recorded with actor, before and after state, reason and trace ID, append-only in the database itself. A scheduled sweep diffs your group against Rostack and surfaces changes made anywhere else.
Trust model
Two paths, and we are honest about both.
Most Roblox tools ask for your account cookie and never explain why. Rostack uses the official API wherever one exists, and tells you plainly where one does not.
Ranking
Official Open Cloud, no cookie
Roblox exposes group role assignment as a first-class API. You create an Open Cloud key in the Roblox Creator Dashboard, scope it to this one group, and paste it once. Revoke it there and Rostack loses that power the same second. We never see a password or a session cookie.
- Auth
- Open Cloud API key
- Scope
- group:write, one group
- Credential held
- Yes, KMS encrypted
- Revocable by you
- Creator Dashboard
POST /cloud/v2/groups/{id}/memberships/{id}:assignRole
Payouts
Legacy credential, quarantined
Roblox publishes no Open Cloud payout API; the endpoint accepts only a session credential. So payouts run in a separate service with its own identity, unreachable from the internet, and the keys are split: the app can encrypt that credential and is permanently unable to read it back. Only the payout service holds decrypt.
- Auth
- .ROBLOSECURITY
- Storage
- Cloud KMS + Secret Manager
- Isolation
- Dedicated service
- Before release
- Two people approve
POST groups.roblox.com/v1/groups/{id}/payouts
If a tool asks for your cookie just to rank members, it is using an outdated method. That has been unnecessary since Roblox shipped group writes to Open Cloud. We only ask for a credential for the one operation that still has no alternative, and we isolate it accordingly.
Verified against Roblox's published OpenAPI document
Audit
Every change leaves a record you can hand to someone.
Hours worked, rank changes, payroll, registers and drift all land in one append-only log with the actor, the reason and a trace ID. Switching a module off hides its page and never its record. Nobody edits history afterwards, not your staff, and not us.
- Privileged actions logged
- 100%Privileged actions logged
- Entries editable after the fact
- 0Entries editable after the fact
- People needed to release a payout
- 2People needed to release a payout
Audit log
- intake
Join request accepted for velvetmoss
rule · Auto-accept verified
- drift
Drift detected: 3 members ranked outside Rostack
reconciler · flagged for review
- payout
Payout run #1043 settled, 128 recipients
prepared by wren · approved by rowan
- payroll
Payroll drafted from tracked hours, 128 recipients
rule · over 300 min this week · 64,000 R$
- rank
Aviatrix_dev promoted to Senior Moderator
rule · met the weekly quota
Security
What we actually do with your data,
in checkable sentences.
No adjectives. Each of these describes a control in the running system, and the security page explains every one of them in enough detail to verify.
Encrypted in transit and at rest
TLS on every connection, with HSTS so a browser refuses plain HTTP. Stored data is encrypted at rest on Google Cloud. Anything that is a credential is encrypted a second time with Cloud KMS, on keys that rotate automatically every 90 days.
The website cannot read your payout credential
It holds the permission to encrypt one and not to decrypt it. Only an isolated service can, and that service answers nobody but the site. Even then it reads each payout from the database itself and pays only a run recorded as approved, exactly as recorded and under fixed ceilings, never simply what it is asked to.
Ranking never touches your account cookie
It runs on an Open Cloud key you create in Roblox's own dashboard, scoped to one group and revocable there. Rostack stores it encrypted with Cloud KMS, because it has to be replayed to Roblox on every call. The keys Rostack issues to your game servers are different: those are kept only as a SHA-256 hash and cannot be read back at all.
A code at the moment money moves
Payouts need a verified email and an authenticator app. Releasing Robux asks for a fresh code every time, and a schedule that pays on its own can only be set up, changed or approved with one. Each code works once, and repeated wrong codes make the account wait. A stolen session cannot release a payout on its own.
An audit log nobody can edit
Every privileged action is written before it runs, with who, why and a trace ID. The log is append-only in the database rules themselves, not merely in application code. Not your staff, and not us.
Your data is yours to take or remove
Download everything we hold about you as a JSON file, or delete your account, from Settings. Both are self-service and immediate. What is retained after deletion is listed, not hidden.
Only what the product needs
A Roblox user ID and username, an avatar URL, an email if you add one, and the work your own game servers report: minutes played, message counts and session attendance. No analytics cookies, no third-party trackers, no advertising, and nothing sold or shared. The one cookie is your session.
Honest about where data lives
On Google Cloud in the United States, under Google's data processing terms, which include the EU standard contractual clauses. Stated plainly because European users are entitled to know it.
Pricing
One flat price per group. Never per head.
Start free with a small team. Plus is the whole product. Max is Plus with five times every limit, for groups that outgrow it.
USD · monthly · cancel anytime
Free
Try it on a small team.
- Staff tracked
- Up to 10
- History
- 7 days
- Sessions a month
- 10
- Robux paid out a month
- None
- API rank changes a day
- 50
- Up to 10 staff tracked
- Ranking by hand, members, roles and API keys
- Activity tracking and 10 sessions a month
- Time off, moderation, feed and the audit log
- 7 days of history
Plus
RecommendedThe whole product, for a working team.
- Staff tracked
- Unlimited
- History
- 90 days
- Sessions a month
- 200
- Robux paid out a month
- 50,000
- API rank changes a day
- 1,000
- Unlimited staff, never counted
- Payouts and payroll, with schedules that pay on their own
- Quotas, promotions, handbook and conduct
- Discord notices and live streams
- 90 days of history
Max
5× PlusPlus, five times over.
- Staff tracked
- Unlimited
- History
- 15 months×5
- Sessions a month
- 1,000×5
- Robux paid out a month
- 250,000×5
- API rank changes a day
- 5,000×5
- Everything in Plus, with five times every quota
- 15 months of history
- 1,000 sessions a month
- 250,000 Robux paid out a month
- 5,000 API rank changes a day
Custom
Beyond Max, agreed with you. Quotas set to what your group needs, billing arranged with you.
Compare plans
| Per group | Free$0/mo | Plus$9/mo | Max$29/mo | CustomCustom |
|---|---|---|---|---|
| People | ||||
| Staff tracked | Up to 10 | Unlimited | Unlimited | Unlimited |
| History | ||||
| Activity, audit log and past sessions | 7 days | 90 days | 15 months | Agreed |
| Work | ||||
| Activity tracking | ||||
| Sessions a month | 10 | 200 | 1,000 | Agreed |
| Time off | ||||
| Quotas | ||||
| Money | ||||
| Robux paid out a month | 50,000 | 250,000 | Agreed | |
| Payroll from tracked activity | ||||
| Schedules that pay on their own | 5 | 25 | Agreed | |
| Ranking and API | ||||
| Ranking by hand | ||||
| API rank changes a day | 50 | 1,000 | 5,000 | Agreed |
| API keys | 1 | 10 | 50 | Agreed |
| Community | ||||
| Feed and moderation | ||||
| Promotions, handbook and conduct | ||||
| Oversight | ||||
| Audit log | ||||
| Drift sweeps | Every 6 hours | Hourly | Every 12 minutes | Agreed |
| Reconciliation view | ||||
| Integrations | ||||
| Discord notices and live streams | ||||
| Your own name and accent colour | ||||
Prices in US dollars, billed monthly for one group. Choose or change a plan in that workspace's settings and cancel whenever you like. A plan never deletes anything: history beyond its window is kept, and comes back the moment you choose a plan that shows it.
FAQ
Straight answers.
The questions people actually ask before trusting a platform with their group and their Robux.
Do I have to give Rostack my account cookie?
Not for ranking, staff management, activity tracking or applications. Those run on an Open Cloud API key you create in the Roblox Creator Dashboard, scoped to one group, which you can revoke there at any moment. A session credential is required only for Robux payouts, because Roblox publishes no official payout API. If you never switch payouts on, Rostack never asks for one.
What stops a bad rule from wrecking my group?
Several things, by design. Rules fail closed, so a rule with no conditions matches nobody rather than everybody. Every run produces a preview you confirm before anything is sent. Runs are capped, high ranks can be protected, and a job can be stopped mid-flight. A rank that would fall outside 0–255 is skipped rather than clamped.
Can a payout ever go out twice?
Each recipient in each run gets an idempotency key generated before execution and checked inside the transaction that marks the line paid, so a retry after an ambiguous failure cannot pay twice. The same discipline runs through activity tracking, which feeds payroll: game servers send cumulative totals rather than increments, so a replayed report overwrites the same record instead of adding to it. Above a threshold you set, a run needs two different people to approve it, and a schedule only ever pays terms that people approved in advance, each with their own authenticator code.
How does Rostack know when something changes on Roblox?
Roblox does not publish group webhooks, so anything claiming to be instant is polling too. Rostack sweeps on a schedule, diffs your group against its mirror, sets aside the changes it made itself, and shows you what is left. It cannot tell you who made a change or the exact minute, and it says so rather than inventing a name.
Who can see the audit log?
Anyone you grant the permission to. Entries are append-only in the database itself, not merely in application code, so nobody, including us, edits history after the fact. Every entry records the actor, the before and after state, a reason and a trace ID.
How much does it cost?
Free is for trying Rostack on a small team: up to 10 staff, ranking by hand, activity tracking, 10 sessions a month, time off, moderation and a week of history. Plus is $9 a month per group and is the whole product: unlimited staff, payouts and payroll that runs itself, quotas, promotions, the handbook, the conduct log, Discord and 90 days of history. Max is $29 a month and is Plus with five times every limit. Anything beyond that is a Custom plan: contact us. Paid plans never count staff, because charging by headcount would mean charging a community for being popular.
Run your community like it matters.
Connect your group with an official Open Cloud key and have ranking rules running in minutes. No cookie, no spreadsheet, no unmaintained bot.