Activate Builders vs Founders vs Portfolio — the three tiers, the absorption rules, the graduation path.

IAWS Activate is one program with three credit tiers stacked vertically

Activate has been around since 2013. The public-facing page lists three named tiers — Builders, Founders, and Portfolio — but the relationships between them aren't made explicit. Founders reading the page often miss that the tiers absorb each other, that two of them have hidden partner-filed ceilings, and that the program ladder is graduated by funding state rather than by application sophistication.

Builders is the entry tier. A founder spins up an AWS account, accepts the Activate terms inside the AWS console, and receives a $1K credit code within 24 hours. There is no LLC requirement, no use-case scrutiny beyond a brief competitor check, and no reviewer in the loop beyond automated approval. This is the floor — anyone with an AWS account and a non-competing product can get it.

Founders is the middle tier — and the most confused. The public Activate page describes Founders as the "$5K credit for incorporated startups" via a self-serve application form. What the page does not say is that the same Founders sub-program has a partner-filed track with a ceiling of $25K. Both are called "Founders" because they share the same internal AWS credit pool and the same eligibility frame; the difference is which reviewer pool processes the application. Self-serve Founders is reviewed by an automated system + a junior reviewer who defaults to $5K. Partner-filed Founders is reviewed by a senior reviewer or partner-development manager who can approve up to $25K when the application is itemized.

Portfolio is the top tier. The public page lists Portfolio as "credits for VC-backed companies" with no dollar figure. Internally, Portfolio has a documented floor of $25K (downgrade case), a typical award of $100K, and an outlier ceiling around $200K for substantial workloads. Portfolio requires an institutional vouch — either a VC submitting via Portfolio Sub-Program access, or an AWS partner submitting via ACE with the institutional funding signal verified through Crunchbase and partner attestation.

The three tiers form a ladder. You start at Builders, graduate to Founders when you incorporate, and graduate to Portfolio when you raise institutional capital. The ladder is sequential — meaning your tier changes as your company evolves — and the tiers absorb each other, meaning a higher-tier approval supersedes the lower-tier pool rather than stacking with it.

IIWhy "Founders" covers two distinct reviewer pools and how to tell them apart

The single biggest source of confusion in Activate credit conversations is the word "Founders." It refers to both the public-facing $5K self-serve form AND the partner-filed $25K ceiling — and the public Activate page does not explicitly distinguish them. Most founders only learn about the $25K ceiling when an AWS partner mentions it during a discovery call.

Mechanically, both tracks pull from the same Activate Founders credit pool. The difference is the submission path and the reviewer assigned. The self-serve form goes through AWS's automated pipeline; the application gets pattern-matched against a checklist, the reviewer is a junior triage person, and the default approval is $5K. The partner-filed track goes through the ACE program; the partner files a structured ACE record with itemized projections, the reviewer is a partner-development manager (PDM) or senior reviewer, and the approval range is $5K–$25K depending on use case specificity.

The reviewer-trust signal is what unlocks the higher dollar figure. When a founder self-attests their projections on a public form, the reviewer can't independently verify whether the founder is being realistic about projected AWS consumption. When an AWS partner attests on the same projections through ACE, the partner is staking their relationship with AWS on the accuracy of the submission. The PDM trusts the partner-attested numbers more, which is why the same pool ranges from $5K (self-attested) to $25K (partner-attested).

This is also why "graduate to partner-filed Founders" is a discrete step for many founders. A bootstrapped startup that initially used the $5K self-serve credit can come back six months later and ask an AWS partner to file the partner-attested record, lifting the realized credit pool to $25K. AWS does not refund the original $5K — but the partner-filed approval adds the marginal amount up to the ceiling.

For SEO purposes, search queries like "AWS Activate $25K" and "AWS Activate Founders" should resolve to the same conceptual answer — the Founders sub-program. The dollar figure is determined by the submission path, not by a different tier name.

IIIBuilders ($1K) — eligibility, mechanics, and when this is the right ask

Builders is the lowest credit tier in Activate. The dollar figure is small but the access is universal. Most founders skip past it because $1K doesn't feel meaningful; that's a mistake during the first AWS sandbox month.

• Eligibility — Any registered AWS account. No LLC required. No funding required. No revenue required. The founder accepts the Activate terms inside the console; the credit code is issued within 24 hours.
• Ceiling — $1K. Single non-extending pool. No partner-filed variant exists — Builders is exclusively self-serve.
• Validity — 12 months from issuance. Auto-applies to monthly invoice; expires unused.
• Use case scrutiny — Minimal. AWS runs an automated competitor check (is this a cloud provider? is this an AI infrastructure substitute?). Otherwise, $1K issues without further review.
• When this is the right ask — First-time AWS user exploring services during initial sandbox month. Side-project founder building before incorporation. Solo engineer trialing a stack before committing to a workload. Hobbyist scaling a small experiment.
• When this is the wrong ask — You have an LLC and a workload. In that case, skip Builders and go straight to Founders self-serve $5K — same effort, 5× the credit pool. Filing Builders first does not "build trust" with AWS for a larger ask later; the tiers are independent.
• The hidden value — Builders carries no obligation. Founders who later raise institutional capital and access Portfolio sometimes retain Builders as a separate sandbox code — small enough to use for experiments without burning Portfolio credits on test workloads.

IVFounders ($5K–$25K) — the two reviewer pools, two ceilings, one program

Founders is the most-used Activate tier across the startup ecosystem. The vast majority of Activate credit dollars flow through Founders — most of them at the $5K self-serve level, a meaningful minority at the $25K partner-filed ceiling. The difference between the two is where the dollar gap lives.

Founders self-serve is the public-form path. The founder fills the application at the Activate page, provides company info, AWS account ID, and a use case description. The form takes 5–10 minutes. The reviewer pool is automated + junior triage. Default approval is $5K. The realistic ceiling on this path is $5K — pushes above $5K require partner-filed escalation.

Eligibility for Founders self-serve requires a registered LLC (or local equivalent — Pty Ltd, Sàrl, GmbH, etc.) and an AWS-eligible use case. The "AWS-eligible" check means the workload uses AWS services in volume rather than being a static brochure site. Approval window is 3–7 days.

Founders partner-filed is the same Founders sub-program submitted through ACE. The partner files a structured ACE record with itemized projections (EC2 at $X, RDS at $Y, S3 at $Z, etc.), use case description, projected annual AWS spend after credits exhausted, and partner role. The reviewer is a senior PDM. Approval range is $5K–$25K; the typical award is $15K and the $25K ceiling is reached when projections are itemized, use case is specific, and partner attestation is present.

Eligibility for Founders partner-filed has the same prerequisites as self-serve PLUS a vetted AWS partner submitting via ACE. The partner must be Advanced or Premier tier with active ACE submission rights. Approval window is 10–14 days.

The graduation pattern within Founders: a bootstrapped startup with no funding typically files self-serve first ($5K, 3–7 days, immediate sandbox funding). After 4–8 weeks of actual AWS usage — with a real consumption history visible to AWS reviewers — the same startup can file partner-filed Founders to push the realized credit pool up to $25K. The historical consumption signal makes the projection more credible, which in turn pushes the second-application approval toward the ceiling.

VPortfolio ($50K–$100K) — the institutional-vouch tier

Portfolio is the top of the Activate ladder. The dollar pool is large, the eligibility is narrow, and the reviewer trust requirements are explicit. Portfolio requires evidence of institutional funding before AWS will entertain the application.

Eligibility for Portfolio requires institutional funding. The funding source can be a VC (any tier, though tier-1 names accelerate review), an accelerator (Y Combinator, Techstars, 500 Global, Antler, MISK, Flat6Labs, NASSCOM 10000 Startups, etc.), or notable angels with publicly verifiable track records. Self-attestation alone does not work — AWS reviewers verify the institutional signal through Crunchbase, news mentions, or partner attestation.

There are two submission paths for Portfolio: VC-direct and partner-filed. VC-direct works when your investor has Portfolio Sub-Program access — the VC submits the application on your behalf through their privileged portal. The VC path is faster when the VC is responsive (10–14 days from VC submission to credit issuance) but slower when the VC is overloaded or the partner-development relationship is dormant (28+ days). The partner-filed path uses the ACE program — an AWS partner submits the institutional-vouch-verified ACE record, and the reviewer processes it in 11–18 days regardless of VC responsiveness.

Portfolio's floor is $25K (downgrade case — applied when the application barely qualifies and the reviewer reduces from the $100K typical award) and ceiling is $100K (the round number most reviewers default to when the application is well-scoped). Outlier cases reach $200K when the projected AWS consumption justifies a larger pool, but these are rare and require substantial workload evidence.

Validity is 24 months from issuance — double the Founders validity. This is deliberate; AWS wants Portfolio companies to consolidate on AWS for the long term, and a 24-month runway funds that consolidation through the period when the company would otherwise be cost-sensitive.

VIThe absorption mechanic — why higher-tier approval supersedes lower-tier credits

The single most important mechanical rule across Activate tiers: they absorb. A higher tier approval does not add on top of a lower tier; it replaces. Founders who try to "stack" Founders and Portfolio end up with the Portfolio amount only.

When a startup receives Portfolio approval at $100K, AWS does not also award the Founders $25K on top. The Portfolio pool supersedes Founders — it is treated as the credit pool for the same workload, drawn from a larger reservoir. The math AWS uses is: "this company's projected AWS consumption justifies $100K; the credit pool will be $100K; the prior Founders allocation is folded into the Portfolio amount."

In practice, this matters because founders often ask whether they should file Founders first and Portfolio second. The honest answer: if you will qualify for Portfolio within the next 60 days (because you're closing a seed round, joining an accelerator, etc.), skip Founders and go straight to Portfolio. The Founders pool will be subsumed regardless. Filing Founders first only makes sense if you need credits immediately and Portfolio eligibility is still 60+ days away.

Builders is the partial exception. Because Builders is auto-issued and small ($1K), AWS sometimes lets it coexist with a later Portfolio approval as a separate code rather than absorbing it. This is not policy — it's an artifact of Builders being administratively distinct from the Founders/Portfolio reviewer pool. The dollar logic is still dominated by whichever tier sits highest; Builders' $1K is a rounding error against Portfolio's $100K.

The absorption mechanic also explains why "downgrade" cases happen. A pre-seed founder without institutional funding who files for Portfolio without the vouch — the application doesn't outright reject. It downgrades to the Founders pool, typically at $25K (partner-filed Founders ceiling, applied as a Portfolio downgrade). The reviewer effectively says, "you don't qualify for Portfolio, but you do qualify for the partner-filed Founders ceiling — here's $25K." This is functionally equivalent to going Founders direct, but slower because the application went through the larger-tier reviewer pool first.

VIIThe graduation pattern — Builders to Founders to Portfolio over 12–24 months

Most companies don't hit Portfolio on day one. They move through the Activate ladder as their funding state evolves. Knowing the graduation pattern helps you avoid filing the wrong tier at the wrong time — and helps you plan the timing of each application to maximize the total credit pool.

Stage zero — solo founder, pre-revenue, pre-LLC. Builders $1K is the right ask. Self-serve, 24-hour approval, no incorporation requirement. The credit funds the initial AWS sandbox month during which the founder is figuring out the stack. Most founders blow through $1K in 30–60 days as they spin up test workloads.

Stage one — incorporated, pre-funding, pre-product. Founders self-serve $5K is the right ask. The LLC is registered, the founder has a use case paragraph, the AWS account has a brief consumption history. Self-serve form approval in 3–7 days. The credit funds the next 4–6 months of pre-revenue infrastructure as the product takes shape.

Stage two — bootstrapped or pre-funding with a clear workload. Founders partner-filed $5K–$25K is the right ask. The product has shape, the AWS spend has 2–3 months of history showing consumption is real, the founder can articulate the workload and project itemized monthly spend. Partner files ACE in 10–14 days. The credit funds 12–18 months of infrastructure during the pre-funding period.

Stage three — institutional vouch arrives (seed round closes, accelerator acceptance, named angel commits). Portfolio $50K–$100K is the right ask. The seed funding is publicly verifiable, the AWS consumption history is robust, the projected post-funding spend is plausible. Partner files ACE in 11–18 days. The credit funds 18–24 months of post-seed infrastructure through the typical Series-A-targeting period.

Stage four — Portfolio exhausted, company hits Series-B or beyond. Activate is no longer the relevant program. The company moves to MAP (Migration Acceleration Program) for migration funding, EDP (Enterprise Discount Program) for committed-spend discounts, or PPA (Private Pricing Agreement) for negotiated pricing. The Activate ladder ends here.

The pattern is graduated and sequential — but it is not strictly required. A pre-seed founder who closes a seed round 60 days into Year 1 can skip Stage 2 entirely and file Portfolio directly. A bootstrapped founder who builds revenue to $1M ARR without raising can stay at Stage 2 indefinitely. The pattern describes the typical trajectory; the right ask at any given moment depends on the current funding state, not on a checklist of prerequisites.

VIIIThe stack-additives distinction — Build for Startups and Bedrock POC sit outside the Activate ladder

Builders, Founders, and Portfolio are mutually-absorbing tiers within Activate. Two other AWS credit programs — Build for Startups and Bedrock POC — are separate program families that stack ON TOP of whichever Activate tier you sit in. Conflating absorbing tiers with stacking programs is the most common reason founders mis-estimate their total credit pool.

Build for Startups is a partner-co-funded engagement program that funds discrete project work — a SOC 2 compliance push, a Heroku-to-AWS migration, a data-warehouse build, etc. Credit awards range $15K–$25K per qualifying engagement. The credits draw from a separate AWS pool earmarked for partner-driven engagements, which is why they stack on top of Activate rather than absorbing into it.

Bedrock POC is a credit program for proof-of-concept work on Amazon Bedrock. The award range is $10K–$50K depending on company stage and AI workload sophistication. The credits draw from a Bedrock-specific budget separate from Activate, which is why they stack rather than absorb. The qualifying use case has to be a genuine AI workload — vague "we use AI for some features" doesn't qualify.

The realistic stacking math: a seed-stage startup with Portfolio approval ($100K) plus a clearly distinct compliance project (Build for Startups, $25K) plus a clearly distinct AI workload (Bedrock POC, $25K) reaches $150K total credits. The Portfolio $100K is the Activate-tier pool; the $25K + $25K are program-family additives that stack on top.

The constraint is that the additive programs require distinct workloads. AWS reviewers will not approve $100K Portfolio for general infrastructure plus $25K Build for Startups for "the same thing AWS is already funding" — that's double-counting, and the reviewer will silently downgrade the Build for Startups approval to $0. The distinctness check is what gates the stacking.

For founders mapping out a credit strategy, the question becomes: which Activate tier am I currently eligible for, and which program-family additives have a genuinely distinct workload behind them? The answers map directly to the application sequence.