Unused cloud credits when closing a startup

When a startup winds down, cash and unused compute are very different things. A cloud grant may still show a large balance while the company needs liquidity for other expenses. That balance is not automatically transferable or recoverable.

This is a preparation checklist for a credit review, not a completed customer case study or a promise of a sale. Company wind-down decisions should stay with the people authorised to make them.

Make a record before access changes

For each provider, record the account or organisation that holds the balance, the source of the credit, the remaining amount and the actual expiry date. Separate credits from cash deposits, invoices and contractual spending commitments.

Save the applicable offer terms and a dated, redacted balance record through your company’s normal process. Do not include API keys, passwords, recovery codes or unrelated customer information in a buyer or broker inquiry.

A useful record contains:

• Provider and credit programme or offer name.
• Remaining balance and expiry for each separate grant.
• Services covered and known restrictions.
• The person authorised to discuss the credit.
• Planned date for closing the account or stopping operations.
• Outstanding usage that may reduce the balance before then.

Our expiry guide explains why a single headline balance may hide several deadlines.

Find out whether any recovery route is permitted

Start with the provider’s agreement and the specific grant conditions. Do not assume that changing an account administrator or providing an API key transfers a credit validly. Ask the provider about the applicable conditions if they are unclear.

A potential buyer’s interest is not proof of permission. Equally, a review may conclude there is no suitable arrangement. Treat that as a possible outcome before investing time or relying on proceeds.

See the relevant seller guide for AWS, OpenAI, Anthropic, Azure or Google Cloud, including links to provider terms.

Give the reviewer the real timeline

Explain when operations stop, when the account is due to close and when each credit expires. Those dates are different. A review response before closure does not mean a buyer will be found or a transaction completed before closure.

At WeBuyAPI, 24–48 hours is the target for an initial review response. Matching and completion depend on eligibility, a suitable counterparty and the agreement between the parties. Do not count an inquiry as committed liquidity.

Keep responsibilities in writing

Before any permitted arrangement proceeds, identify who has authority to agree it, what each party receives, which checks must pass and when payment is due. Clarify responsibility for usage, access and unresolved obligations with the appropriate advisers and counterparties.

WeBuyAPI makes introductions and does not hold funds, credits or account credentials. Read the service terms and verification process to understand the scope of our role.

Request a review with a concise brief

A useful initial message is: “We have unused credits with this provider, issued under this programme, expiring on this date. Our operations are winding down on this timeline, and this person is authorised to discuss them.” Add the balance and any known restrictions.

You can submit credits for review without setting an asking price. A person will assess the details before any potential introduction. For valuation preparation, read how to value unused cloud credits.