AWS Credits for Startups: The 2026 Activate Guide

How AWS Activate actually works in 2026, which door leads to which amount, and why five different "$5,000 in AWS credits" offers are really the same offer.

AWS will give a pre-Series B startup up to $200,000 in Activate credits, and it gave each startup in its 2025 Generative AI Accelerator cohort up to $1 million, yet most founders who apply walk away with $1,000. None of those numbers is a rumor. They are published on AWS's own credits page and in its announcement of the 2025 accelerator cohort. The gap between $1,000 and $200,000 is not luck, and it is rarely the quality of the startup. It comes down to which application door a founder walks through, and whether they hold a single string of characters called an Organization ID when they do.

Here is the problem: AWS credits are sold to founders through dozens of channels that all sound different and are, underneath, the same program. A bank offers "$5,000 in AWS credits." A corporate card offers "up to $5,000 in AWS credits." A developer platform, a cap-table tool and an internal-tools builder make the same promise. A founder who collects all five expecting $25,000 discovers that AWS grants Activate credits to a company once per package level, and the second, third and fourth offers add nothing. Meanwhile the one route that really changes the number, an Activate Provider relationship that unlocks the Portfolio tier, is buried under the noise.

This guide untangles it. It covers exactly what AWS publishes about each tier in 2026, the eligibility rules line by line (including a new requirement created by AWS's 2025 Free Tier overhaul), the rule that stops partner credits from stacking, all 31 routes to AWS credits in the StartupPerks catalog with the offers we re-checked on each provider's own page, a step-by-step application walkthrough, the AI-specific tiers, burn math for making credits last, and a decision framework for picking your route. Every figure links to its source.

Contents

1. The 2026 AWS credit ladder at a glance
2. What Activate credits are, and what they will not pay for
3. Eligibility, decoded line by line
4. The one-package rule: why partner credits do not stack
5. Every route to AWS credits we track
6. Founders or Portfolio: which door is yours
7. How to apply, step by step
8. AWS credits for AI startups: Bedrock, the $200K+ tier and the accelerator
9. Making credits last: the burn math
10. AWS versus Google, Microsoft and the rest
11. Seven mistakes that cost founders AWS credits
12. The decision framework
13. Frequently asked questions

1. The 2026 AWS credit ladder at a glance

AWS does not run one startup credit program. It runs a ladder of five rungs, and each rung has its own door, its own gatekeeper and its own ceiling. Reading the ladder correctly is most of the work, because the amounts rise by orders of magnitude from one rung to the next, and a founder who stops at the first rung never learns the others exist.

The bottom rung is the AWS Free Tier, which is no longer the free tier most founders remember. In its current form, AWS gives new customers $100 in credits immediately and up to $100 more as they try key services, for a total of up to $200. The Free plan lasts six months, and AWS states plainly that the account "closes on its own 6 months after you open it or when your credits run out, whichever comes first," unless you convert to a Paid plan. More than 30 services stay always free within monthly limits on both plans. This rung is available to anyone with a new account, and it has nothing to do with Activate.

The second rung is Activate Founders, the self-serve door for bootstrapped and self-funded companies. AWS's credits page describes it as "Up to $5,000 USD in Activate Credits," with the important qualifier that founders "start with $1,000 USD in Activate Credits" and "select participants may qualify for additional credits up to $5,000." In practice, the number to plan around is $1,000; the $5,000 is a ceiling AWS may extend, not a promise.

The third rung is Activate Portfolio, and it is where the real money lives: up to $200,000 in credits. Portfolio is for pre-Series B startups affiliated with an Activate Provider, an accelerator, angel investor, venture firm or other organization that AWS has approved to hand out an Organization ID. The Org ID is what unlocks the tier. Without one, a funded startup applies through Founders and receives Founders amounts.

The fourth rung is AWS Credits for AI Startups, which AWS lists as "$200,000+ in AWS Credits." It is marked "invite only for startups ready to scale post Activate Portfolio," and the stated path in is to talk with your AWS account manager. There is no public application form for this rung.

The fifth rung is the AWS Generative AI Accelerator, a competitive program rather than a credit tier. AWS's What's New page described the 2025 cohort's benefits as including "up to $1 million in AWS credits," and AWS's cohort announcement says 40 startups were selected "from a highly competitive pool of thousands of global applications." It is the largest credit number AWS publishes, and also the hardest to reach.

The chart makes the central fact of AWS credits impossible to miss: the jump from the Founders ceiling to the Portfolio ceiling is 40x, and nothing a founder can do on the Founders form closes that gap. Only a provider relationship does. That is why this guide spends as much time on Org IDs and provider routes as on the application form itself.

Our catalog pages for the two self-applied tiers, AWS Activate Founders and AWS Activate Portfolio, track these values against AWS's page, and the Amazon Web Services provider page groups them.

2. What Activate credits are, and what they will not pay for

Activate credits are promotional credits: they reduce your AWS bill, they are denominated in US dollars, and they are governed by the AWS Promotional Credit Terms and Conditions. They are not cash, they cannot be withdrawn, and they do not transfer between companies. Understanding the mechanics matters because the terms decide how much of a headline number a startup can actually use before it expires.

Credits apply automatically, month by month, to eligible new usage. AWS's explainer on Activate credits states that credits "apply monthly to new AWS usage charges on eligible services" and that they cannot be applied retroactively to past bills. That second point catches founders who run up a bill while their application is pending: charges incurred before approval stay charged. If you are about to start an expensive workload, wait for the approval email, or keep the workload small until it arrives.

Credits expire. The same explainer says credits "usually expire within 1-2 years depending on the package," and AWS's application guide repeats the advice to note the expiration date so the balance is not lost. Unused credits do not roll over into a new grant. A $200,000 Portfolio package that expires after two years has to be consumed at an average of roughly $8,300 a month to be fully used, which is far more than most seed-stage startups spend. We come back to this in the burn math section, because it changes which package is worth chasing.

The eligible list is broad. AWS says credits cover "over 200 eligible AWS services," naming compute (EC2, ECS, EKS), databases (RDS, DynamoDB), storage (S3) and networking (CloudFront, VPC) as examples. Two inclusions are worth singling out:

• Amazon Bedrock, including third-party AI models. AWS explicitly lists Bedrock usage among eligible charges, which means Activate credits can pay for foundation-model inference served through Bedrock, not only for AWS's own infrastructure. For an AI startup, this makes AWS credits closer to "AI credits" than many founders assume.
• Eligible AWS Support plans. Paid support can be covered, which matters for a small team that needs faster answers during a launch.

The ineligible list is short but specific. AWS names Amazon Mechanical Turk, AWS Managed Services, AWS Professional Services, AWS Training and Certification, and services not listed in the AWS Billing Console. The practical reading: credits pay for the cloud you run, not for people AWS sends to help you run it, and not for anything bought outside the billing console. If your plan relies on a consulting engagement or a marketplace product, budget for it in cash.

You can see your balance at any time in the AWS Billing and Cost Management console, under Billing, then Credits. The explainer notes that approved credits typically appear there three to four hours after approval. The same page lists each credit's expiration date, which is the number to put on your calendar.

Credits sit on an account, and accounts sit inside organizations. If you run multiple AWS accounts under AWS Organizations, confirm which account the credits land on before you build: the application links one AWS account, and AWS's guide notes that only one Builder ID links per AWS account. Founders who build in a personal account and later move to a company organization should make the switch before applying, not after.

3. Eligibility, decoded line by line

AWS compresses its eligibility rules into a single sentence on the credits page: "Pre-series B, founded in the last 10 years, AWS Account on Paid Tier Plan, and either new to Activate Credits or requesting more credits than previously received." Each clause has consequences that the sentence does not spell out, so here they are one at a time.

"Pre-series B." Activate is for early companies. A startup that has closed a Series B round is outside the program, whatever its burn. The Portfolio tier adds a timing rule on top: AWS's explainer says Portfolio applicants must apply within 12 months of their most recent funding. A seed round closed 14 months ago does not qualify a startup for Portfolio through that round's investor, even if the investor is an Activate Provider. If you raised recently, apply now; the clock is running.

"Founded in the last 10 years." The window is generous, and it rarely excludes a startup, but it does exclude a mature small business that has recently decided to "act like a startup." AWS asks for the company's details in the application, so the founding date must match what a reviewer can verify.

"AWS Account on Paid Tier Plan." This clause is new, and it trips up more founders than any other in 2026. AWS's Free Tier now distinguishes a Free plan (the six-month, up-to-$200 credit experience with limited service access) from a Paid plan (full access to every service). Activate credits require the Paid plan. A founder who opens an account on the Free plan, applies to Activate and links that account has linked the wrong kind of account. Upgrade the account to the Paid plan first. Upgrading does not mean you start paying immediately: Activate credits and always-free limits still apply to eligible usage, but it does mean usage beyond them bills to your card, so set a budget alert before you build (see section 9).

"Either new to Activate Credits or requesting more credits than previously received." This is the clause that governs stacking, and it gets its own section below. In short: AWS grants a company one Activate package at a given level. A second application only succeeds if it asks for more than the company already received, which in practice means moving up from Founders to Portfolio, or from a smaller Portfolio package to a larger one.

Two unwritten requirements matter as much as the written ones. AWS's explainer lists a "fully functioning website" as a requirement for Founders, and its application guide lists it for both tiers. A landing page with a waitlist form can count; a parked domain or a "coming soon" image usually does not. The guide also asks you to "use your business email address (matching your startup's domain)" when you build your Activate profile. A Gmail address and a company domain that do not match are among the delay causes AWS lists. If your company email and website live on different domains, fix that before applying.

Provider affiliation (Portfolio only). Portfolio requires an Org ID from an Activate Provider. AWS's provider directory says it works with "hundreds of accelerators, angel investors, and venture capital firms worldwide" and features NVIDIA, Y Combinator, Carta and Andreessen Horowitz on the page. The Org ID is a string your provider gives you, usually through a perks portal or a founder handbook. If you are backed by an investor or accelerator and do not know your Org ID, ask them directly: it is common for founders to miss it because it is filed under "perks" alongside discounts on unrelated software.

4. The one-package rule: why partner credits do not stack

This is the most expensive misunderstanding in startup credits, and it is worth stating bluntly: Activate credits offered by different partners are, almost always, the same Activate credits. When a bank, a card or a software company advertises "$5,000 in AWS credits," it is typically an Activate Provider passing its Org ID to its customers. The credits come from AWS's Activate program, under AWS's eligibility rules, including the rule that a company is "either new to Activate Credits or requesting more credits than previously received."

Brex says so in its own words. Brex's partner perks page states that "All new Brex customers are eligible for $5,000 in AWS credits depending on Activate eligibility." The phrase "depending on Activate eligibility" is the tell. The Brex offer is an Activate grant, and whether you receive it depends on whether AWS has already granted your company an Activate package of that size.

So the arithmetic that founders do on these offers is wrong. A startup that opens a Mercury account ("AWS $5k credits" on Mercury's perks page), a Brex card, a Jeeves card ("Up to $5,000 in AWS credits" on Jeeves's rewards page) and a Capbase subscription ("up to $5K in AWS credits" on Capbase's pricing page) does not end up with $20,000. It ends up with one $5,000-level package at most, from whichever route it redeems first, and the later redemptions fail the "requesting more" test.

The rule also works in your favor, because it defines a ladder you can climb. "Requesting more credits than previously received" means a company that took a small package early can come back for a larger one later. The sensible sequence for most startups is:

1. Before funding: claim the largest package you can reach now. For a bootstrapped company with no partner, that is Activate Founders at $1,000. For a company that already banks with a partner that offers $5,000, it is the partner route, since $5,000 beats $1,000.
2. After an institutional round: apply for Portfolio with your investor's or accelerator's Org ID, within 12 months of the round. Portfolio is a larger request, so the earlier package does not block it.
3. If you are AI-first and scaling: ask your AWS account manager about the $200,000+ AI tier once Portfolio credits are in use.

Two practical corollaries follow. First, do not redeem a small partner offer the week before a larger one becomes available, because the timing does not hurt your eligibility for the larger request, but it does waste the effort and can confuse which provider's Org ID sits on your account. Second, the value of a bank's or card's "AWS credits" should not decide which bank or card you choose. If three providers offer the same $5,000 Activate route, it is a tie on that line; choose on fees, reliability and the rest of the offer. Our guide to startup bank accounts and the business banking ranking compare those other lines.

What does stack is credit from different clouds. An Activate package, a Google for Startups Cloud Program grant and a Microsoft for Startups grant are three separate programs run by three separate companies. Nothing in AWS's terms forbids you from also holding Google or Azure credits, and many startups use them for different workloads. The stacking strategies in our guide to getting $100K+ in startup credits cover how founders sequence the major clouds.

5. Every route to AWS credits we track

The StartupPerks catalog holds 2,378 program records. After removing false matches (two Austrian programs where "aws" is the national funding agency Austria Wirtschaftsservice, and tools that merely run on AWS without granting credits), 31 records grant AWS credits or access to AWS perks: 18 accelerator and investor programs, 6 banking and fintech products, 3 cloud programs (the two Activate tiers and Alchemy), and one each in AI, developer tools, HR and finance tooling.

We re-checked the stated AWS offer on each major provider's own page on 2026-09-26. The results, with the exact wording each page uses:

The fintech routes: convenient, but capped at the Founders ceiling

Five of the verified partner offers sit at exactly $5,000, which is the Activate Founders maximum. That is not a coincidence. These partners are passing through an Activate package at that level, so for a bootstrapped startup the practical value is simple: a partner route can take you from the $1,000 Founders starting amount to $5,000 without waiting to be one of AWS's "select participants." That is a genuine $4,000 difference for a company that was going to open a business account anyway.

What these routes cannot do is exceed the tier they deliver. A seed-funded startup that banks with Mercury and has an investor who is an Activate Provider should use the investor's Org ID for Portfolio, not the bank's $5,000 route, because Portfolio's ceiling is 40 times higher.

Aspire is the outlier among fintech routes. Its rewards page states "Get up to $100,000 in AWS credits," alongside large Google Cloud and Azure offers. For a company that can open an Aspire account and has no institutional investor yet, it is one of the few routes on our list that reaches Portfolio-scale numbers without an accelerator. As with every "up to" figure, the amount a given company receives depends on AWS's review, so treat $100,000 as the ceiling of the route, not the expected grant.

The investor and accelerator routes: where Portfolio lives

Portfolio is built around Activate Providers, and 18 of the 31 routes in our catalog are accelerators or investor programs. They range from global programs to regional incubators, and several state their Activate affiliation in their perk descriptions: Antler, Entrepreneur First, Plug and Play and 500 Global all describe AWS Activate Portfolio access as a portfolio benefit. Our full list lives on the accelerators page, which keeps these programs separate from product perks because they involve applications, selection and often equity.

The largest single AWS number in our catalog comes from an investor program. Conviction's Embed program states "$350K in AWS credits, $350K in Azure credits, $500K+ of other compute/inference/hosting credits" alongside its investment terms. That is a meaningfully larger AWS figure than the $200,000 Portfolio ceiling AWS publishes for its standard tier, which illustrates a point worth knowing: some investor programs state AWS packages above the standard Portfolio ceiling, so the published ceiling is not the most a provider relationship can bring.

AWS's own provider directory names four featured providers: NVIDIA, Y Combinator, Carta and Andreessen Horowitz. The NVIDIA listing is the interesting one for AI founders, because NVIDIA describes Inception as "a free program that guides AI startups through the NVIDIA platform and ecosystem" (our catalog page tracks its benefits), which makes it one of the more accessible provider relationships in the directory. Membership terms and the Org ID process sit with NVIDIA, so confirm the current path inside Inception's member resources rather than assuming automatic access.

Carta's presence on the list is a reminder to check your existing vendors. Many founders already use Carta or a similar tool for their cap table, and provider benefits are often filed in a perks section that nobody reads. Before paying for anything to get an Org ID, check the perks portals of every investor, accelerator, bank and software vendor you already have.

The developer-platform routes

Alchemy and Retool bundle AWS credits into their own startup programs. Alchemy's startup program lists "$5,000 in AWS credits" for qualified teams, together with Alchemy's own credits and engineering support, which makes it a natural route for web3 teams already building on Alchemy. Retool's startup program lists "Up to $5K in AWS credits and free resources" among more than $200,000 in partner deals attached to its own Retool credits. For both, the AWS component is a Founders-level package delivered through a partner, so the one-package rule applies.

6. Founders or Portfolio: which door is yours

The choice between Founders and Portfolio is not a choice at all for most startups: it is decided by whether you have a provider relationship. But there are edge cases, and getting them wrong costs months or tens of thousands of dollars.

Choose Founders if you are bootstrapped and have no investor, accelerator or partner route. Apply directly, expect $1,000, and treat the possibility of $5,000 as upside. The application is fast, the decision comes in days, and the credits cover a long runway for a small workload. If you also open an account with a partner that offers a $5,000 route, compare the timing: taking the partner route first gets you the larger Founders-level package without relying on AWS's discretion.

Choose Portfolio if you have raised from, or been accepted into, any organization that is an Activate Provider, and you are within 12 months of that funding. Ask the provider for its Org ID, confirm your company is on their list if they keep one, and apply. The Portfolio amount varies by provider, and AWS's own Portfolio record in our catalog notes that packages are tiered by the provider's level. You will not know your exact amount until approval.

The first edge case: you have Founders credits and have just raised. The "requesting more credits than previously received" clause is written for you. Apply for Portfolio with the new investor's Org ID. Your earlier Founders package does not disqualify you, because Portfolio is a larger request.

The second edge case: your investor is not an Activate Provider. Many angels and small funds are not. In that case, look at the other relationships you have or could cheaply create: an accelerator application you were planning anyway, a bank or fintech with a provider route, or a program such as NVIDIA Inception if you are building in AI. The AWS provider directory is the authority on who is a provider; our catalog's accelerators page shows which programs describe AWS benefits.

The third edge case: you are close to a Series B. Activate is pre-Series B. If your B round is imminent and you have not applied for Portfolio, apply before the round closes, while you are still eligible, and within 12 months of your previous round.

The fourth edge case: you are an AI company already spending heavily. Portfolio is still the door, because AWS describes the $200,000+ AI tier as being for startups "ready to scale post Activate Portfolio." Get Portfolio first, build a spending history, then raise the AI tier with your account manager.

7. How to apply, step by step

AWS's application guide, published in June 2026, breaks the process into seven steps. The credits page compresses the same flow into four. Here is the long version, with the traps at each step.

Step 1: create or sign in with an AWS Builder ID. The Builder ID is a personal profile, created with a personal email and verified before you continue. It is separate from your company's AWS account. AWS describes its purpose as giving you access to AWS tools across organizations.

Step 2: complete your AWS Activate profile. This is a one-time profile. AWS's instruction here is the one to follow exactly: "use your business email address (matching your startup's domain)." A mismatch between the email on the profile and your website's domain is one of the delay causes AWS names.

Step 3: select the credit tier. Founders for self-funded startups; Portfolio for provider-affiliated startups, which requires the Org ID. Enter the Org ID exactly as your provider gave it: an invalid Org ID is another delay cause AWS lists.

Step 4: provide startup details. AWS asks for business information, product details, target market and traction, your current funding stage (pre-seed, seed, Series A or beyond) and your most recent funding date from any investor source. The funding date is what AWS uses to check the 12-month Portfolio window, so give the real date of your latest close.

Step 5: link your AWS account. Create a new account or link an existing one, using your business email for consistency. You need administrator permissions on the account you link, and AWS's guide lists missing administrator permissions as a cause of failed links. This is also the moment to confirm the account is on the Paid Tier plan (see section 3).

Step 6: verify the AWS account. Use the verification button in the Management Console. The confirmation you want to see is "Accounts linked successfully."

Step 7: review and submit. Check every field, submit, and watch for the confirmation email.

After submission, AWS's two pages give slightly different timelines: the credits page says "You'll hear back within 5-10 business days," and the application guide says processing "usually takes 7-10 business days." Plan for two weeks. If nothing arrives after ten business days, AWS's own advice is to check your spam folder. Once approved, credits typically appear in the billing console within three to four hours.

A pre-submission checklist distilled from AWS's own list of delay causes:

• The email on your Activate profile uses your company's domain, and that domain hosts a working website.
• The AWS account you are linking is on the Paid Tier plan, is active (not suspended), and you are an administrator on it.
• Only one Builder ID is linked to that AWS account.
• For Portfolio, the Org ID is copied exactly from your provider, and your most recent funding date is within the last 12 months.
• Pop-ups are enabled in your browser, which AWS's guide notes the flow needs.

8. AWS credits for AI startups: Bedrock, the $200K+ tier and the accelerator

AWS has made AI the center of its startup pitch. Its AI for Startups page describes Activate as offering "credits to build on Amazon Bedrock, Kiro, and 200+ AWS services." For an AI founder, three things on the AWS ladder matter more than they do for anyone else.

First, Bedrock usage is eligible for Activate credits. AWS's explainer lists Amazon Bedrock, including third-party AI models, among eligible services. That means an Activate package can fund model inference as well as the infrastructure around it. When comparing AWS against dedicated model-provider credit programs, count Bedrock-served inference as part of what AWS credits buy. Our guide to AI credits for startups and the AI credits ranking compare the model providers' own programs.

Second, the AI Startups tier exists, but it is not a form you fill in. AWS lists "$200,000+ in AWS Credits" for AI startups, "invite only for startups ready to scale post Activate Portfolio," reached by talking to your account manager. The sequencing matters: get Portfolio, use it, build the relationship with your AWS account team, and raise the AI tier when your workload justifies it. A startup with no Portfolio history and no account manager has no door to knock on.

Third, the Generative AI Accelerator is the biggest prize, and a genuinely competitive one. AWS's announcement of the 2025 cohort gives the facts: 40 startups selected "from a highly competitive pool of thousands of global applications," each eligible for "up to $1 million USD in AWS credits," in an eight-week program that kicked off in person in Seattle on October 14 and culminated at AWS re:Invent in Las Vegas in December. The cohort spanned Asia Pacific, North America, Latin America, Europe and the Middle East, and participants received mentorship and access to AWS domain experts and partners.

AWS publishes the accelerator's terms cohort by cohort, so check its startup pages for the current round's dates and eligibility before planning around it. Third-party summaries of the next cohort circulate widely; the numbers that matter are the ones on AWS's own pages at the time you apply. What the 2025 figures tell you is the selectivity: with thousands of applications for 40 places, the accelerator is a long shot for most companies, and it should sit alongside a Portfolio application, never replace one.

9. Making credits last: the burn math

A credit grant is only worth what you can spend before it expires. AWS says credits usually expire within one to two years depending on the package. That turns every headline number into a monthly figure, and the monthly figure is the one that tells you whether a package is right-sized for your startup.

Here is the arithmetic, using AWS's published amounts and a two-year expiry as the generous case:

The table explains two things founders usually learn the hard way. A $1,000 or $5,000 package, spent carefully, can cover a small production workload for its whole life: a few modest instances, a managed database and storage can sit comfortably under $200 a month. A maximum Portfolio package, on the other hand, is more than most seed-stage companies can spend before it expires. Unused Portfolio credits are not a loss in cash terms, but they are a reason not to design an architecture around credits you will not use, and a reason to be skeptical of any "stack" advice that simply adds headline numbers together.

Five habits keep credits from running out, or expiring, unexpectedly:

1. Put the expiry date on the calendar the day credits land. The billing console shows each credit's expiration. Review usage against it monthly.
2. Set a budget and alerts in AWS Budgets. A Paid Tier account bills your card for usage the credits do not cover, so an alert at 50%, 80% and 100% of your expected monthly spend is cheap insurance.
3. Keep ineligible services out of the credit plan. Consulting (AWS Professional Services), managed operations (AWS Managed Services), training and anything bought outside the billing console are not covered.
4. Tag resources from day one. Credits apply to eligible usage across the account, so without tags you cannot tell which experiment consumed them. Cost allocation tags make the monthly review a five-minute job.
5. Plan for the day credits end. The credit period is a runway, not a permanent discount. The architecture you choose while credits pay the bill is the one you will pay for afterwards, so price the post-credit monthly bill before you commit to a design.

The last habit is the one that separates founders who benefit from credits from founders who are trapped by them. Six-figure credit packages make expensive services feel free, and teams sometimes build on them without asking what the bill will be in month 25. The simple discipline is to run the numbers twice: once with credits, once without, and to be comfortable with the second number before the first one runs out.

10. AWS versus Google, Microsoft and the rest

AWS is not the only cloud courting startups, and it is not the one with the highest published ceiling. Here is how the top published figures compare across the major clouds, drawn from each provider's page through our catalog:

Ceilings are the least useful way to choose a cloud. Microsoft's startup page states "up to $150,000 in credits," Google's top tier requires funding and an AI-core product (our Google for Startups guide covers its tiers in detail), and AWS's top standard tier needs a provider. For a bootstrapped company, the relevant comparison is between the entry tiers, and there the differences are smaller than the headlines suggest.

What AWS offers that the others do not is breadth and ecosystem depth. AWS runs more than 200 eligible services under Activate, including Bedrock for model inference, and a provider network AWS describes as "hundreds of accelerators, angel investors, and venture capital firms worldwide," which makes the Portfolio route reachable for many founders who never thought of themselves as provider-backed. Google's ceiling is higher for AI-first funded companies. Microsoft's program is the most open to self-serve applicants. Our cloud credits guide and the ranked list of cloud credits for startups weigh these trade-offs, and the cloud category lists every cloud program we track.

Because different clouds' credits do stack, many startups hold more than one. A common pattern is to build the core product on one cloud and use another's credits for a specific workload, such as model training or analytics. Before doing this, weigh the cost of splitting your infrastructure: credits are temporary, but operating two clouds is not.

11. Seven mistakes that cost founders AWS credits

Most lost AWS credits are not lost to rejection. They are lost to timing, to the wrong door, or to credits that expire unused. These seven mistakes come straight from the rules above and from the delay causes AWS lists in its own application guide.

Mistake 1: applying through Founders when you hold a provider relationship. A funded startup that applies through Founders receives Founders amounts, $1,000 to start. The fix costs one email: ask every investor, accelerator and program you belong to whether it is an Activate Provider and, if so, for its Org ID. Then apply for Portfolio, which AWS publishes at up to $200,000.

Mistake 2: missing the 12-month Portfolio window. AWS's explainer says Portfolio applicants must apply within 12 months of their most recent funding. Founders who spend a year heads-down after a seed round sometimes find the window closed. Apply in the first months after a round, even if you do not need the credits yet, and remember that credits usually expire within one to two years, so the grant and the need should line up.

Mistake 3: linking an account on the Free plan. AWS's eligibility sentence requires an account "on Paid Tier Plan." A founder who opens a new account, stays on the six-month Free plan described on the Free Tier page and links it to Activate has linked an ineligible account. Upgrade first, then set a budget alert so the Paid plan does not surprise you.

Mistake 4: a profile email that does not match the company domain. AWS asks for a business email "matching your startup's domain" and names mismatched email domains as a cause of delays. A personal address on the Activate profile, or a company that emails from one domain and hosts its website on another, invites a slower review.

Mistake 5: redeeming several $5,000 partner offers and expecting them to add up. They are typically the same Activate package, delivered by different partners. AWS grants a company credits only when it is new to Activate or requesting more than before, so the second and third $5,000 redemptions add nothing. Pick one partner route, and choose your bank or card on everything else it offers.

Mistake 6: running up a bill while the application is pending. Credits apply to new usage after approval and cannot be applied retroactively to past bills. If you start an expensive workload during the five to ten business days AWS takes to respond, that month's charges are yours. Keep the workload small until the approval email and the credits (usually visible three to four hours after approval) arrive.

Mistake 7: letting credits expire unused, or building a bill you cannot pay afterwards. A $200,000 package that expires in two years needs roughly $8,300 of eligible spend a month to be fully used, which is more than most seed-stage teams run. The opposite failure is worse: designing an architecture that only makes sense while credits pay for it. Price your post-credit monthly bill before you commit, and review usage against the expiry date every month.

The common thread is sequencing. Every one of these mistakes is avoided by doing the same four things in order: confirm your provider relationships, prepare the account (Paid plan, admin rights, matching email and a live website), apply for the largest tier you can reach within its window, and set budgets and an expiry reminder the day the credits land.

12. The decision framework

Every founder's route to AWS credits comes down to a handful of questions. Answer them in order and the right door is usually obvious.

Question 1: do you have an investor, accelerator or other organization that is an Activate Provider, with funding in the last 12 months? If yes, apply for Portfolio with their Org ID. Nothing else on the ladder comes close for a standard startup. Ask them for the Org ID today if you do not have it.

Question 2: if not, do you already use, or plan to use, a fintech or software partner that offers an AWS route? If yes, use the partner route for a $5,000-level package rather than starting at Founders' $1,000. Brex, Mercury, Jeeves, Capbase, Alchemy and Retool all state $5,000-level AWS offers on their own pages, and Aspire states up to $100,000. Redeem only one of the $5,000 routes: they do not add up.

Question 3: if neither, apply for Activate Founders. Expect $1,000, keep your workload small, and set up budgets and alerts. When you raise, move up to Portfolio.

Question 4: are you an AI-first startup? Add two things to your plan: use Portfolio credits on Bedrock where it fits your stack, and consider a relationship such as NVIDIA Inception, which AWS features as an Activate Provider. Once Portfolio credits are in use, ask your AWS account manager about the $200,000+ AI tier, and watch AWS's startup pages for the Generative AI Accelerator's next cohort.

Question 5: will you actually spend it? Before chasing the largest number, check the burn math. A package you cannot use before it expires is not worth a worse bank, a worse accelerator or a rushed architecture. The right package is the largest one you can realistically consume.

The one rule that holds in every row: claim the largest package you can reach now, and plan the climb. The StartupPerks perk matcher builds a personal stack across every cloud, bank and tool program in our catalog, including which AWS route fits your situation.

13. Frequently asked questions

How much are AWS Activate credits worth in 2026? AWS's credits page lists Activate Founders at $1,000, with select participants eligible for up to $5,000, and Activate Portfolio at up to $200,000. AI startups past Portfolio can be invited to a $200,000+ tier, and the 2025 Generative AI Accelerator cohort received up to $1 million each.

Can I get AWS credits without funding? Yes. Activate Founders is for bootstrapped and self-funded startups. You need a company founded in the last 10 years, a working website, a business email on your company's domain and an AWS account on the Paid Tier plan.

What is an Activate Provider Org ID, and where do I find it? It is a code an Activate Provider (an accelerator, angel investor, venture firm or other approved organization) gives its companies so they can apply for Portfolio. Providers usually share it through a perks portal or founder handbook. AWS's provider directory describes the program; if your investor is a provider and you cannot find the code, ask them.

Can I combine AWS credits from Brex, Mercury and other partners? Usually not. These offers are typically Activate packages delivered through the partner's provider relationship, and AWS grants Activate credits to a company only if it is new to Activate or requesting more than it previously received. Brex's own page says its $5,000 offer depends on "Activate eligibility." Redeem one partner route; credits from different clouds, such as Google Cloud or Azure, are separate programs.

How long do AWS credits last? AWS says credits usually expire within one to two years depending on the package. The exact expiration date for each credit is shown in the Billing and Cost Management console under Credits.

Do AWS credits cover Amazon Bedrock? Yes. AWS lists Amazon Bedrock, including third-party AI models, among the services eligible for Activate credits.

What can AWS credits not be used for? AWS names Amazon Mechanical Turk, AWS Managed Services, AWS Professional Services, AWS Training and Certification, and services not listed in the AWS Billing Console as ineligible.

How long does the application take? AWS's credits page says you will hear back within 5 to 10 business days; its application guide says processing usually takes 7 to 10 business days. Approved credits usually appear in the billing console three to four hours after approval.

Why was my application delayed or rejected? The causes AWS names include an email domain that does not match your startup, an invalid Org ID, account linking problems and missing administrator permissions on the linked account. Also check that the account is on the Paid Tier plan and, for Portfolio, that your latest funding is within 12 months.

Can startups outside the United States apply? AWS's published eligibility sentence contains no country restriction: it asks for a pre-Series B company founded in the last 10 years, with an AWS account on the Paid Tier plan. The 2025 Generative AI Accelerator cohort included startups from Asia Pacific, North America, Latin America, Europe and the Middle East. Partner routes differ by market, so check each partner's own terms.

Do AWS credits pay for support plans? AWS lists eligible AWS Support plans among the charges Activate credits can cover, which can matter for a small team that needs faster answers during a launch.

Is there a cost or equity requirement for Activate? AWS's credits page describes Activate as a credit program with an application and eligibility rules; it does not list any fee or equity requirement. Investor and accelerator routes are different: a program such as Conviction's Embed pairs its AWS credits with an investment on its own terms, so read those terms separately from the credits.

Can I apply again for more credits? Yes, if you request more than you previously received. The usual path is Founders first, then Portfolio after an institutional round.

This guide reflects AWS's published terms and the partner offers we checked as of September 26, 2026. AWS and its partners change amounts, tiers and eligibility frequently, so confirm the current terms on each official page before you apply. StartupPerks is an independent directory and is not affiliated with Amazon Web Services.