How much AWS cloud credit can startups get?

AWS publishes Activate Founders and Activate Portfolio paths. The public AWS Activate pages describe $1,000 for eligible Founders and up to $100,000 for eligible Portfolio startups.

Who qualifies for AWS Activate credits?

AWS publishes requirements such as startup stage, company age, company website, AWS account, and Activate Provider or Org ID requirements for Portfolio applicants. Always check the current AWS page before applying.

What is the difference between AWS Activate Founders and Portfolio?

Founders is the self-funded or early-stage path for startups not associated with an Activate Provider. Portfolio is the provider-backed path for startups with an Activate Provider and Organizational ID, and can support a larger credit package.

What is an AWS Activate Provider?

An AWS Activate Provider is an approved startup organization, investor, accelerator, or similar partner that can give eligible startups an Organizational ID for the Portfolio path.

Can a startup get more AWS credits after using Activate?

Sometimes there may be another route, but do not assume a repeat grant. The case is stronger when credits were used, current AWS spend is visible, and there is a new workload, funding round, customer rollout, or AI project.

Are AWS credits the best path for every startup?

No. For some startups, the better path is a discount, payment terms, funded project help, or even a different provider route if AWS fit is weak.

Should a startup move to AWS just for credits?

Not by default. Credits only make sense if AWS fits the workload, engineering roadmap, compliance needs, customer requirements, and long-term cost profile.

AWS Startup Credits: How AWS Activate Works

Direct answer

AWS startup credits usually start with AWS Activate. The main paths are Founders and Portfolio; Portfolio can be larger, but it needs an Activate Provider and Org ID, and prior AWS credits can affect the route.

Partner route

Eligibility is the first filter. Commercial credibility is the second.

AWS Activate is the public starting point. The stronger commercial question is whether a partner can package a credible case around real AWS usage, AI or data growth, migration, customer rollout, discounts, funded work, payment timing, or another provider route.

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.

Check the route How partner routes work

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.

First-time AWS startup

Check Activate Founders or Portfolio before looking for any partner route.

Best when company details, website, stage, and AWS account are clean.

Provider-backed startup

Portfolio may fit when an Activate Provider and Org ID are real.

Best when prior equal-or-greater AWS credits do not block the package.

Already used credits

The ask shifts from application eligibility to commercial review.

Best when current run-rate, usage growth, funding, customer rollout, AI, data, or migration is visible.

Credits are weak

Discounts, payment terms, funded work, or another provider path may be stronger.

Best when the company has real spend or a real project, not just a free-hosting request.

Published AWS paths

AWS publishes Activate Founders and Activate Portfolio. AWS materials describe $1,000 for Founders and up to $100,000 for Portfolio, subject to eligibility, stage, funding timeframe, provider affiliation, and terms.

Sources: AWS Activate credits AWS Activate application guide AWS Activate credit guide

AWS startup credit program: the short version

AWS Activate path

What to check first

Common wrong move

Founders

Are you new to Activate, self-funded or early-stage, founded in the last 10 years, and using a real company website?

Expecting a Portfolio-sized package without an Activate Provider.

Portfolio

Do you have an Activate Provider, an Org ID, and no prior equal-or-greater AWS Activate credits?

Applying before the provider relationship and account details are clean.

For a focused comparison, read AWS Activate Founders vs Portfolio. If you need the provider-backed route, read AWS Activate Providers and AWS Activate Portfolio Org ID.

AWS is one route

If AWS credits are weak, already used, or too small for the next stage, compare the broader commercial routes before applying again.

Compare all routes Check AWS fit

The AWS credit route map

Route

What it means

Best fit

Activate Founders

Published AWS path for self-funded or early-stage startups without an Activate Provider relationship.

Good first check for early teams that are new to Activate and have a functioning company website.

Activate Portfolio

Published AWS path for eligible startups with an Activate Provider and Organizational ID.

Good when the startup has a provider relationship and has not already received equal or greater credits.

Post-Activate review

Not a simple renewal. The case depends on spend, usage, funding, and what changed.

Good when credits were consumed and AWS usage is expected to grow.

Commercial support path

Discounts, payment timing, funded help, or project support may be more realistic than more credits.

Good when credits are limited but the account has real spend.

If you already used AWS Activate

The best post-Activate cases do not sound like "we want more free credits." They sound like: "We used the allocation, AWS is part of production, current run-rate is visible, and a new project or customer rollout will increase usage."

If that is your situation, read after AWS Activate credits. That page is built around the real partner conversation: usage, retention, expansion, discounts, funded work, payment terms, migration support, or a second-provider route. If the second-provider route is specifically Google Cloud, use Google Cloud credits after AWS Activate to check whether the case is real or just credit shopping.

This is why using all your cloud credits can be a stronger signal than letting credits expire unused. Consumed credits show there was real demand. Expired unused credits may make the account look less urgent unless something material changed.

Post-credit framing

Do not ask, "Can we get more AWS credits?" Ask, "What is the strongest AWS or partner-supported commercial path now that we can show usage and growth?"

Good-fit signals for AWS startup credits

New to Activate

You have not already received an equal or greater AWS Activate credit allocation.

Founded less than 10 years ago

AWS public materials list company age as part of startup eligibility.

Pre-Series B or early funded

AWS Activate public materials focus on early startup stages and provider-backed paths.

Real AWS workload

Current or near-term AWS usage matters more than wanting credits in the abstract.

AI or data growth

Bedrock, data pipelines, inference, SaaS infrastructure, or customer deployments can make the spend case clearer.

Used credits already

If credits were consumed, bring the run-rate and growth trigger before asking for another route.

When AWS credits are not the best answer

AWS may still be the right cloud, but credits are not always the right instrument. If your usage is ongoing and predictable, a discount or commitment structure may matter more. If the issue is cash timing, payment terms may help more. If the issue is a new AI, data, migration, or customer deployment project, funded technical help or project support may be the cleaner ask.

No current AWS usage

A credit request without a workload is usually weak.

Credits expired unused

You need to explain what changed and why usage will now materialize.

Architecture does not fit AWS

Do not move a product to AWS purely for a credit headline.

The bill problem is permanent

Credits buy time. They do not fix long-term architecture or unit economics.

What to prepare before applying or asking a partner

Activate history

Whether you used Founders, Portfolio, another provider route, or no credits yet.

AWS account and billing detail

Current spend, credit balance, expiration, linked accounts, and service-level run-rate.

Company stage

Founding date, funding stage, investor/provider relationship, and public website.

Workload plan

AI, Bedrock, data, SaaS infrastructure, migration, customer rollout, or other AWS-heavy project.

Commercial flexibility

Whether discounts, payment terms, funded help, or another provider path could also solve the problem.

If you are comparing routes, read cloud credits through resellers and cloud credit programs for startups in Europe. If the blocker is which AWS package fits, use the Founders vs Portfolio guide. For a basic first filter, use AWS Activate eligibility.

Recent field notes

What we are seeing from startup cloud-benefit reviews.

Based on 45 non-cancelled startup cloud-benefit calls booked since January 2026, the strongest-fit companies usually had one or more clear signals: existing cloud spend, credits ending soon, recent funding, AI or GPU-heavy workloads, or a planned infrastructure project.

These are internal patterns from recent startup conversations, not guaranteed provider approval criteria.

45: non-cancelled calls
2026: booked since January
5: strong-fit signals

Next step

Check whether AWS credits, discounts, terms, or a partner route fits.

The quiz takes about 60 seconds and helps avoid applying through the wrong path.

Check eligibility