AWS Activate Credits: How to Reach the $100k Portfolio Tier
· Cloud Credits Research, FinOps research
AWS Activate is two programs wearing one name. Understanding which door you are standing at is the whole game: one door is self-serve and small, the other is worth up to $100k but gated by a relationship you may not have yet.
The two tiers
- Founders (self-serve). Open to unaffiliated startups. You apply directly, and the credit amount is modest (roughly $1,000). Useful for validating an idea; not a runway story.
- Portfolio (up to $100k). Accessible only through an approved Activate Provider: an accelerator, incubator, or venture fund AWS recognizes. This tier carries the headline number plus AWS support credits and training resources.
The gap between the two is not a bigger form. It is a gatekeeper.
How to reach the Portfolio tier
The Portfolio tier flows through an Activate Provider, so the practical path is to get affiliated with one:
- Join or align with an approved provider. If your startup is in a recognized accelerator or backed by a participating fund, ask their platform team for the Activate Provider org ID. That ID is what upgrades your application from Founders to Portfolio.
- Apply through the provider link, not the public page. The self-serve page routes you to Founders. The provider-supplied link is what unlocks the higher ceiling.
- Provide the requested company details. Funding stage, AWS account ID, and product description. Approvals are usually fast once the provider affiliation checks out.
The strategic read: the $100k tier is as much a business-development channel for AWS as a subsidy. Your investor's platform team introduces you, AWS deepens the relationship, and the credits create gentle lock-in. Budget your stay-or-leave decision before the credits expire, not after.
What the credits do and do not cover
Activate credits offset AWS usage charges, and the Portfolio tier bundles a pool of AWS support credits plus training resources. What they do not do is cover third-party marketplace software, premium support beyond the granted pool, or anything you buy before activation. Read the exact service exclusions in your offer, because a workload that looks free on the console can still bill against a non-credited line and quietly draw down runway you thought was covered.
The credits also apply in a fixed order against your bill, so a large committed instrument bought on top of credits can interact in ways that surprise finance at month-end. If you are near the end of a credit balance, model the first uncovered invoice before you sign a multi-year commitment.
The three programs side by side
| AWS Activate | MS for Startups (Founders Hub) | Google for Startups | |
|---|---|---|---|
| Top ceiling | $100k (Portfolio) | $150k (staged) | $200k / $350k AI (Scale) |
| No-investor tier | ~$1k (Founders) | Yes, full program | ~$2k (Start) |
| Gatekeeper for top tier | Activate Provider | None, milestone-based | Institutional investor |
We go deeper on the tradeoffs in startup credit programs compared. If accessibility matters more than the headline number, Microsoft's Founders Hub is usually the more open path.
Three rules for spending them well
- Apply before the spend. Credits apply forward only. Our AWS playbook covers the timing per program.
- Treat credits as runway, not architecture budget. Anything you build only because it is free becomes a bill on expiry day.
- Diary the expiry. Unspent credits vanishing is the startup-program cousin of unclaimed SLA credits: same invisibility, same fix. Put a number on it and give it an owner.
Where credits stop and recovery begins
Activate credits cover the build. Once you are in production and paying real invoices, two other kinds of money open up. Billing drift hides in your invoice (see finding billing errors in cloud invoices), and when AWS breaches its uptime commitments it owes you SLA credits. If an outage hits, capture the evidence the same day: awsdown.com tracks live AWS incidents, and the SLA calculators at cloudslacredit.com turn affected hours into a credit figure. The Azure and GCP playbooks mirror this for the other two clouds, and the resources library has the eligibility checklists.
Automating the whole loop (detection, evidence, claim) is what our sponsor Next Signal builds, so "we should recover that" becomes a routine instead of a regret. Start by reading the blog and running the recovery estimate.
