c08128156b
Positioning document — draws the line between babysitting and orchestration. Ready for marketing page or standalone deployment. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2.7 KiB
The Corrosion Manifesto
Rust Servers Deserve Orchestration
Rust is brutal.
The wipes are unforgiving. The players are demanding. The uptime matters.
But the tools?
Still manual. Still fragile. Still built around babysitting.
We think that's wrong.
Servers Shouldn't Be Babysat
They Should Be Orchestrated.
Editing JSON over SFTP at 1:47am isn't power.
It's friction.
Restarting blindly after a crash isn't management.
It's hope.
Watching force wipe days like a hawk isn't control.
It's stress.
Corrosion exists because Rust server administration hasn't caught up to the game itself.
This Isn't a Plugin.
It's a Control Plane.
A control plane doesn't "add features."
It orchestrates systems.
It:
- Coordinates wipe sequences
- Verifies health states
- Automates Steam updates
- Protects data with rollback
- Isolates tenants by design
- Namespaces every command
- Moves administration to the browser
You don't SSH into AWS.
You orchestrate it.
Rust servers deserve the same maturity.
Automation Is Not a Luxury.
It's Stability.
Manual wipes break communities.
Missed updates cost players.
Unplanned downtime kills momentum.
Automation isn't about convenience.
It's about consistency.
Corrosion automates what should never have required manual intervention in the first place.
Outbound-Only. No Duct Tape.
Corrosion doesn't require inbound firewall ports.
It doesn't tunnel gameplay.
It doesn't proxy traffic.
Your server stays yours.
Corrosion is orchestration — not interception.
Multi-Admin Without Chaos
Communities grow.
Moderators join.
Owners delegate.
Manual permission juggling is brittle.
Corrosion introduces structured, role-based access control so your server scales without losing order.
Wipes Should Be Predictable.
Not Ritual.
Pre-wipe countdown. Backup. Map rotation. Steam update. Health verification. Rollback if needed.
A wipe isn't an event.
It's a sequence.
Corrosion treats it that way.
This Is Only The Beginning.
Analytics are coming.
Retention insights.
Map performance trends.
Hosting company integrations.
A module ecosystem.
Corrosion isn't a single plugin release.
It's infrastructure for the Rust ecosystem.
The Line in the Sand
Rust servers are no longer just hobby projects.
They are communities.
Communities deserve tooling that reflects that.
If you believe:
- SSH shouldn't be mandatory
- Wipes shouldn't be chaos
- Panels shouldn't be duct tape
- Automation should be default
Then you already understand Corrosion.
Deploy Once.
Automate Everything.
Never SSH Again.
Corrosion The Control Plane for Rust Servers.