AWS Activate Founders is the smaller direct route for eligible early startups. AWS Activate Portfolio is the larger provider-backed route and requires an Activate Provider plus an Org ID.
$1,000
Founders credit level
$100K
Portfolio credit ceiling
Org ID
required for Portfolio
AWS Activate credits & commercial routes
Many founders search for AWS startup credits and land on AWS Activate without knowing which package fits. That can create a weak application or the wrong expectation.
AWS currently describes Activate Founders as a $1,000 credit package for eligible self-funded or early-stage startups. AWS describes Activate Portfolio as up to $100,000 for eligible provider-backed startups associated with an Activate Provider and using an Organizational ID. AWS Activate credits AWS Activate application guide
If Portfolio may fit, read AWS Activate Providers and AWS Activate Portfolio Org ID. If you already used AWS credits, read after AWS Activate credits before assuming the public application is still the best move. For the broader AWS route, read AWS cloud credits for startups, and for the basic first filter, read AWS Activate eligibility.
Founders vs Portfolio comparison
| Question | Activate Founders | Activate Portfolio |
|---|---|---|
| Primary fit | Self-funded or early-stage startups without an Activate Provider relationship. | Startups associated with an AWS Activate Provider. |
| Provider requirement | No Activate Provider required. | Activate Provider and Organizational ID required. |
| Published credit level | $1,000 in AWS Activate Credits. | Up to $100,000 in AWS Activate Credits. |
| Common blocker | Expecting the larger package without a provider relationship. | Missing Org ID, unclear provider relationship, or prior equal-or-greater credits. |
| Best first move | Prepare a clean direct application case. | Confirm provider details before applying. |
Partner route
Eligibility is the first filter. Commercial credibility is the second.
Founders vs Portfolio is the package question. The partner-route question is different: can a credible partner defend this account with evidence around usage, implementation, retention, growth, migration, or a real workload instead of only chasing the bigger credit headline?
No-cost initial review
A realistic route check should not cost the startup money. The partner is compensated by the provider or channel side when a qualified account moves forward. Paid implementation work is separate if it is not provider-funded.
Public form
Company age, website, AWS account, package rules, prior credits, Org ID.
Partner review
Run-rate, workload fit, migration plan, funded work, payment terms, retention case.
Cost to startup
The initial fit check should not cost money when there is a realistic provider opportunity.
Guardrail
No guaranteed credits, no fake Org ID, no partner shortcut without a real workload.
When Founders is probably the first check
Founders is usually the cleaner first path when the startup is early, does not have an Activate Provider relationship, has a real company website, and has not already received AWS Activate Credits in a way that blocks the ask.
When Portfolio is probably the first check
Portfolio is usually the cleaner first path when the startup is associated with an Activate Provider such as an investor, accelerator, or startup organization, and has the Organizational ID needed for the application.
Why the partner layer matters
A provider-backed route is not only about getting a code. Providers are more likely to take a case seriously when a trusted partner can show the account is real, the workload can be implemented, and support now may help retain or grow the customer.
The better question is not just "Founders or Portfolio?" It is "which route can a credible partner actually defend with evidence?"
What to prepare before applying
Provider relationship
Do you have an AWS Activate Provider, and can they provide the Org ID?
Prior credits
Have you received AWS Activate Credits before, and how much?
Company evidence
Website, business email, founding date, funding stage, and product description.
AWS workload
Which AWS services matter, what usage exists, and why AWS is the right provider.
Fallback route
If Activate is weak, check discounts, funded services, payment terms, migration support, or a second-provider route.
If your credits already ended, read what happens when AWS credits expire.
Check the AWS package before applying.
The route checker helps map Founders, Portfolio, post-credit review, discounts, payment terms, or funded help for your account.
