Get an ingest token

An ingest token is the credential your server uses to identify itself to CerebRUST. It looks like this:

crst_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

One token, one server.

How to get one right now

Sign in and open Server Access from the Owners menu, then press Start my 7-day trial. No card, and the token appears straight away.

Every token on your account is listed on that page with its status and the server it is bound to, and there is a Copy button beside each one. That is the page to start from however you came by the token.

What it costs

Free for 7 days, then £6.99 per month, per server.

Start the trial on Server Access — one click, no card, nothing to cancel if you change your mind. You get a token immediately; paste it into the plugin and your server appears the first time it calls in. Every feature is switched on from the first minute; there is no cut-down tier.

One trial per account, ever. It covers one server, which is what a token covers.

Subscribing keeps the same token. Buy access during or after your trial and CerebRUST takes over the token you already installed rather than issuing a new one — so there is nothing to edit, nothing to reload, and your telemetry does not stop. Pay with a card, Apple Pay or Google Pay.

After the trial there is no one-off purchase — it is a subscription, and you can cancel whenever you like from Manage billing on the same page. Cancellation takes effect at the end of the period you have already paid for — you keep the time you bought — and on top of that your token stays valid for a further three days of grace, so a renewal in flight can never drop your telemetry mid-wipe. Invoices, receipts and card changes all live in that same portal.

If your trial runs out and you do nothing, the plugin simply stops being able to send data. Nothing already collected is deleted, and it all comes back the moment you subscribe.

If you were given a token before payments opened, it keeps working exactly as it did. Nothing you already have just became billable.

What we tell you, and when

CerebRUST tells you when your access is in trouble — in the dashboard’s notification inbox, and as a Discord DM if you’ve linked your Discord account. Five messages, and no others:

When	What you get
A payment is declined	Your card was declined, Stripe will retry, and the date your access runs to
It goes through on a retry	It worked, nothing to do
You schedule a cancellation	The date access ends, and that resubscribing before it means nothing lapses
Access is ending within three days	What stops working, and when
Access has ended	Your server has stopped reporting

A normal, successful renewal says nothing. Stripe emails you a receipt; a monthly message from us saying we took your £6.99 would be noise, and we’d rather you kept notifications switched on for the one that matters.

Emails come from Stripe, not from us

We never see your email address — you sign in with Steam, which doesn’t give us one, and Stripe collects it at checkout. So receipts, failed-payment emails and the “update your card” link are sent by Stripe, and they’re the messages that reach you when you’re not looking at the dashboard. Ours are the in-product half: the inbox and the Discord DM.

If you’re on a trial, or you’ve been given free access rather than paying, you get the “ending soon” warning too — worded for what you actually have, with no mention of cards you have not given us.

How binding works

A fresh token is unbound. The first time your server calls in, the token locks to that server — specifically to its IP : game port : query port.

From then on:

• That token only works from that address. A copy pasted onto a second server is rejected.
• The server is linked to the account that the token was issued for, and shows up under My servers in the dashboard.
• The bind also creates the server’s first wipe record, which is what all telemetry is scoped to.

This is why you cannot share a token between servers, and why a token that has been used somewhere else will not work for you.

If your server address changes

Because the token is bound to IP : game port : query port, changing any of them breaks the bind and you will see a 409 error in your server console.

Common causes: migrating hosts, a provider reassigning your IP, or changing your query port.

Ask in Discord and the bind can be cleared or reissued. Don’t reinstall the plugin hoping it clears itself — it won’t, and the rebind has to happen on our side.

Multiple servers

You need a separate token per server. Each one appears in the dashboard as its own server, with its own settings, staff, map and leaderboard.

Keeping it safe

Treat it exactly like a password:

• Never paste it into a screenshot, a public channel or a support message
• Never commit oxide/config/Cerebrust.json to a public repository
• If it leaks, ask for a replacement — a leaked token lets someone submit fake telemetry as your server

Where the token goes

On most servers it goes into oxide/config/Cerebrust.json — see Install the plugin.

On a Pterodactyl server running the CerebRUST edition of the Rust egg it goes into the CerebRUST Ingest Token field on the Startup tab instead, and the panel writes it into that file on every start. There, the panel field is the source of truth and editing the file by hand does not stick.

Next

Install the plugin and drop the token into your config.