What each framework is for
Oxide (commonly distributed via uMod) and Carbon are both plugin frameworks that sit on top of a Rust dedicated server. They let you run community plugins, customise gameplay and automate admin tasks. They are not the Rust game itself—Facepunch still owns the server binary and patch schedule.
Update reality
Rust updates frequently. After a game patch, plugin frameworks and individual plugins can lag. Plan wipe or restart windows with that lag in mind. Prefer frameworks and plugins with recent maintenance activity over abandoned lists you found on an old forum thread.
When Oxide is a good fit
Oxide/uMod remains widely documented. Many long-running community plugins and tutorials assume Oxide-style hooks. If your staff already know Oxide commands and your plugin set is Oxide-first, staying there usually means less retraining.
When Carbon is a good fit
Carbon is chosen by some operators for its own tooling and plugin story. Treat it as a deliberate stack decision: confirm every required plugin has a Carbon-compatible build, and test after each Rust update on a staging copy before wipe day.
Practical decision checklist
1) List the plugins you cannot run without.
2) Check each one against your chosen framework’s current builds.
3) Install on a copy of the server, not production.
4) Load into a local or empty map session and watch the console for hook errors.
5) Only then schedule the production cutover.
What this guide will not claim
We do not publish fake TPS charts or “X% faster” claims comparing Oxide and Carbon. Performance depends on plugin count, entity count, map, player behaviour and host CPU—especially single-thread behaviour on wipe day. Measure on your own workload.
Related: Rust server hosting · Wipe-day checklist
Plan calculator · Migration wizard · Free trial
Monolith runs game servers on a verified Ryzen 9 9950X production node with panel, SFTP and scheduled backups.
Share an honest review to help other server owners.