Before day one: the quote
You send last month's invoices, or a CSV export, from each provider you want to move. Within two working days you receive a quote laid out like a statement: one line per provider with the list price you paid, the price you would pay, and the broker's share. Nothing is committed until you accept.
| Day | You | Deplium |
|---|---|---|
| 0 | Accept the quote and pick a currency | Creates your workspace and Stripe customer; sends the transfer plan per provider |
| 1 to 3 | Accept payer invitations or add Deplium as billing owner, one provider at a time | Confirms each link, records existing commitments and credits |
| 4 to 6 | Nothing required; work continues as normal | Verifies that usage is flowing to the right payer and that rates apply from the next cycle |
| 7 to 10 | Join one call to set up budgets, alerts and allocation tags; enable SSO if wanted | Configures governance, connects Slack or email alerts, hands over documentation |
| First month end | Receive one statement | Issues the statement and, on Managed, the first rightsizing report |
Days one to three: the transfers
Each provider has its own mechanism, and they are all reversible. On AWS you accept an invitation into the broker's Organization from each account's console. On Vercel, Neon, Supabase or Fly you add the broker as an owner and it moves billing to its agreement. On reseller providers such as Azure or DigitalOcean, your account is linked to the broker's partner tenant. Each step takes minutes; the calendar days are for the provider's confirmation.
What you should not be asked for
Root credentials, API keys with write access, or administrative roles beyond billing. A transfer that needs any of those is not a billing transfer.
Days four to six: verification
The broker checks that each provider is now billing the payer, that existing Savings Plans, credits and reserved capacity are recorded so they are not double-counted, and that the agreed rates will apply from the next cycle. Providers bill in arrears, so the first statement covers the first full cycle after the transfer; anything before it is on the provider's last direct invoice to you.
Days seven to ten: controls
- Allocation tags: agree the tag key that spans providers, such as project or team, and map existing tags to it.
- Budgets and alerts: one budget per project across providers, alerts at the thresholds you choose, delivered to email or Slack.
- SSO: connect your identity provider to the dashboard and, where the provider supports it, to the provider.
- Documents: download provider SOC 2 reports and DPAs from one place.
The first statement
At month end you receive one statement in your currency with a line per provider, the list price for reference, and the amount saved. From here the routine is monthly: statement, report, and the Desk in between.
If you ever want to reverse it
Cancel at period end. Billing reverts to your own accounts at the end of the billing month, the broker leaves your teams and Organizations, and because nothing moved there is nothing to move back. Statements and exports stay downloadable for twelve months.
Common questions
Is there downtime?
No. The transfer changes who pays, not where anything runs. Deploys and traffic continue throughout.
Can I move one provider first?
Yes. Most customers start with the largest bill and add others over the following months. Each provider is transferred and can be reverted independently.
What if a provider takes longer to confirm?
The rate applies from the first full cycle after the provider confirms. The Desk keeps you informed; nothing on your side is blocked.