# Corrosion — B2B Reseller Plan for Hosting Providers

---

## Why Model B Over Model A

Model A (embedded SaaS) requires:

* Org-layer multi-tenancy
* White labeling
* Deep integration
* SSO
* Heavy engineering

Model B requires:

* License API
* Bulk provisioning endpoint
* Simple billing reconciliation

**Much faster to market.**

Hosts love: "Add this feature, charge more."

---

## Financial Structure

### Hosting Company Pricing Example

| Customer Pays | Host Keeps | You Earn |
|---------------|------------|----------|
| $15/mo add-on | $9         | $6       |
| $20/mo add-on | $14        | $6       |
| $10/mo add-on | $4         | $6       |

Let them control markup.

You standardize wholesale at **$6/server/month**.

That gives them incentive.

---

## Minimum Viable B2B — Technical Requirements

You don't need Phase 6 fully built. You need:

### 1. Bulk License Provisioning API

```
POST /api/host/provision

Body:
{
  "server_id": "abc123",
  "hostname": "rust-nyc-01",
  "customer_email": "user@example.com"
}

Returns:
{
  "license_key": "...",
  "companion_token": "...",
  "plugin_download_url": "..."
}
```

That's it.

### 2. Host Dashboard (Lightweight)

For hosts only:

* Active licenses
* Monthly count
* Status (connected / offline)
* Billing report export (CSV)

Keep it minimal.

### 3. Automated Monthly Usage Report

At end of month:

* Count active servers
* Send invoice for X * $6
* Or integrate Stripe metered billing later

Manual invoicing at first is fine.

---

## How You Pitch It to Hosts

Not: "We built a Rust tool."

But: **"We reduce Rust support tickets and increase your revenue per server."**

Hosts care about:

* Ticket volume
* Upsell opportunity
* Differentiation
* Stability

### The Pitch

> **Corrosion for Hosting Providers**
>
> * Reduce wipe-related support tickets
> * Eliminate Steam update confusion
> * Provide advanced Rust automation competitors don't have
> * Add $10–$20 per server in recurring revenue
> * Zero infrastructure changes required
> * Outbound-only connection model

---

## Competitive Advantage

Most hosts:

* Offer AMP/Ptero
* Maybe some scripts
* Nothing Rust-native

If one host integrates Corrosion properly, they can market:

**"Fully Automated Rust Hosting — Powered by Corrosion"**

That's a differentiation lever.

---

## Strategic Rule

**Never undercut hosts by selling cheaper directly.**

If they charge $15/mo add-on, your direct pricing shouldn't make customers think: "Why not just buy it myself?"

For B2B stability:

* **Direct license** = one-time purchase (CodeFling model)
* **Host add-on** = convenience + integration + automation

Different value.

---

## Tactical Moves (Pre-Launch)

1. Add a hidden "For Hosting Providers" page
2. Draft a 1-page pitch PDF
3. Prepare wholesale rate structure
4. Identify 3 Rust hosts
5. Reach out privately — not publicly. Quiet, targeted outreach.

---

## Long-Term Revenue Model

If you get:

* 5 hosting partners
* Each averaging 150 Rust servers

That's:

* **750 servers**
* **750 x $6 = $4,500/month recurring**

Without selling a single CodeFling license. Now scale that.

---

## The Real Play

Individual admins create brand awareness.

Hosting providers create revenue stability.

**You do both.**