AWS Activate: Builders vs Founders vs Portfolio — the real dollar amounts, eligibility, and how to climb the ladder.

IThree tiers, one program — and why the naming trips people up

AWS Activate is a single startup program. The confusion is that it contains three credit tiers with different names, different dollar amounts, and — critically — two completely different application mechanics. Getting the mental model right first saves weeks of filing the wrong thing.

The three tiers, in ascending order, are Builders, Founders, and Portfolio. Builders is the entry rung: $1,000 in credits, available to essentially any company with a website and an AWS account. Founders is the middle rung: $5,000 in credits, available to early-stage startups that are not yet institutionally funded. Portfolio is the top rung: a credit award that AWS describes only as being "for portfolio companies of eligible partners," with the dollar figure conspicuously absent — in practice, $100,000 for the typical institutionally-funded startup.

The first thing to internalize is that Builders and Founders are self-serve. There is a public application form, you fill it out yourself, and approval is automated or near-automated — usually within a few hours, occasionally up to a couple of days. No partner, no VC, no introductions. You sign up, you describe your company, the credits land in your billing console.

The second thing to internalize is that Portfolio is not self-serve and there is no form you can find. This is the single most common point of confusion among founders who go looking for "the $100K Activate application" and come up empty. The form does not exist publicly because Portfolio is gated to two submission channels: a nomination from a VC or accelerator that holds Activate Portfolio access, or a partner-filed submission through the AWS ACE (APN Customer Engagements) program. We unpack both channels in detail below.

A naming wrinkle worth flagging: AWS has revised the tier names more than once, and older guides still reference labels like "Activate Founders" as a catch-all for everything partner-filed. As of 2026 the cleanest way to hold it is by dollar amount and submission mechanic — $1K self-serve (Builders), $5K self-serve (Founders), $100K gated (Portfolio) — because those three attributes are what actually determine your path. The label matters far less than whether you can file it yourself.

If you only remember one sentence from this section: the two small tiers are something you do in an afternoon by yourself; the large tier is something a partner or VC does on your behalf over a couple of weeks. Everything else is detail hanging off that distinction.

IIBuilders — the $1,000 self-serve baseline

Builders is the floor of the Activate ladder. It exists so that any developer or early team can get a small credit cushion without proving anything beyond "we are a real company building on AWS." Treat it as the on-ramp, not the destination.

The Builders tier provides $1,000 in AWS promotional credits, valid for two years from the date of issue. Eligibility is deliberately broad: a company website, a working email on that domain, and an AWS account that has not previously received Activate credits. You do not need funding, revenue, an accelerator, or a partner. The application is a short public form, and most approvals are automated within hours.

Builders credits behave exactly like every other Activate credit once they hit your account — they auto-apply against eligible AWS usage on your monthly invoice until exhausted or expired. The $1,000 covers a meaningful amount of early experimentation: a small EC2 or Fargate footprint, an RDS instance, some S3 and CloudFront, a bit of Lambda. For a team still in the "is this architecture even right" phase, it is usually enough to run a prototype for a few months without seeing a bill.

Where Builders stops being enough is the moment real workloads start. A single modest production environment with a managed database, a load balancer, observability, and a non-trivial compute footprint will burn through $1,000 in weeks, not months. That is by design — Builders is meant to get you onto AWS and comfortable, not to fund a runway. The expectation baked into the program is that you graduate to Founders or, if you raise, straight to Portfolio.

One practical note that catches people: receiving Builders credits does not disqualify you from later tiers, but the tiers absorb rather than stack. If you take $1,000 of Builders today and later qualify for $100,000 of Portfolio, you do not end up with $101,000 — Portfolio supersedes the smaller award. So there is no penalty for taking Builders early, but there is also no compounding benefit. Take it if you want the cushion now; do not treat it as a down payment on a larger number.

IIIFounders — the $5,000 self-serve tier for early-stage startups

Founders is the middle rung: five times the Builders credit, still self-serve, still public, but aimed specifically at startups rather than any company. It is the largest amount you can get without either a VC nomination or a partner filing on your behalf.

The Founders tier provides $5,000 in AWS credits, typically valid for one to two years depending on the issuance, plus access to the broader Activate benefits bundle — technical resources, a portion of AWS Support credits, and program content. Eligibility is aimed at startups that are early but real: incorporated, with a product or clear product plan, and generally not yet through a priced institutional round. You apply through the public Activate form and select the Founders path; approval is usually within a day or two.

The practical line between Builders and Founders is "company versus startup." Builders will approve essentially anyone. Founders expects to see a startup — a company building a scalable product, ideally with some signal of seriousness (a live site, a pitch, an accelerator affiliation, early traction). The bar is still low and the process is still self-serve, but the $5,000 is calibrated for teams that are going to build something substantial on AWS rather than run a brochure site.

Five thousand dollars covers meaningfully more than Builders — a small but genuine production environment for several months at typical pre-seed burn, or a longer runway of prototyping and load testing. For a bootstrapped or pre-seed team that is cost-sensitive and not yet ready for the partner-filed process, Founders is frequently the right and sufficient ask. It buys real time without requiring you to involve anyone outside your team.

The important structural fact about Founders is that it is the ceiling of the self-serve world. There is no self-serve tier above $5,000. Everything larger — the $25K-class composite awards, the $100K Portfolio award — requires leaving the public form behind and entering the gated channel. So when a founder asks "how do I apply for more than $5K myself," the honest answer is that you cannot; the next step up is structurally a different process, not a bigger version of the same form.

As with Builders, Founders absorbs into Portfolio rather than stacking. A startup that takes $5,000 of Founders and later secures $100,000 of Portfolio does not end at $105,000 — the Portfolio award is the number. There is no harm in taking Founders while bootstrapped and graduating to Portfolio after a raise, but the smaller credit is not additive to the larger one.

IVPortfolio — the $100,000 tier you cannot apply for yourself

Portfolio is where Activate stops being a form you fill out and becomes a process someone runs for you. It is the largest standard Activate award, the most valuable, and the most misunderstood — precisely because AWS removed the dollar figure and the public form.

The Portfolio tier provides a discretionary credit award that, for the typical institutionally-funded startup, lands at $100,000 — with a practical floor around $25,000 for smaller use cases and a ceiling that runs higher for outlier situations. The credits are valid for two years from issuance, the longest validity window of the three tiers, which is deliberate: $100K is sized to fund a startup through the period when it would otherwise be acutely cost-sensitive, roughly 18–24 months at typical Series-A burn.

Eligibility for Portfolio is not about your stage in the abstract — it is about whether you can reach one of the two gated submission channels. Channel one is a nomination from a VC or accelerator that holds Activate Portfolio access; most established funds and top accelerators do. Channel two is an AWS partner filing on your behalf through the ACE program. You do not need a tier-1 VC and you do not need to be in Y Combinator; you need either an investor with Portfolio access who will nominate you, or a partner willing to attest to your use case via ACE.

The VC-nominated path works when your lead investor already has Activate Portfolio access wired up — many do, and the credits flow as a standing portfolio benefit. The mechanics are simple in principle (your investor adds you to their portfolio in the Activate console) but the timeline depends entirely on how responsive your investor's platform team is; in practice it ranges from a few days to several weeks. If your VC has the access and an attentive platform team, this is a clean route.

The partner-filed path is the one most founders end up using, because it does not depend on your investor's administrative attentiveness and is typically 2–3× faster. An AWS partner with ACE submission rights files a structured opportunity record describing your company, your projected AWS consumption itemized by service, and the engagement they will deliver alongside the credits. An AWS reviewer reads the record and approves a credit amount. When the record is filed well, the credits land in 11–18 days. We break down exactly what that record contains, and what the reviewer checks, in the next two sections.

The thing to hold onto is that Portfolio is qualitatively different from Builders and Founders. The smaller tiers are entitlements — meet the bar, fill the form, get the fixed amount. Portfolio is a discretionary, attested award routed through a gated channel, which is why it has no public form and no published number. That structure is also why the success of a Portfolio application depends heavily on who files it and how well, rather than purely on your company's merits.

VWhy the public Activate page hides the Portfolio amount

Founders routinely land on the official Activate page, see "$1,000" next to Builders and "$5,000" next to Founders, then see Portfolio described in words with no number — and conclude either that it is mythical or that they are missing a link. Neither is true. The omission is deliberate, and the reasons are structural.

Reason one: Portfolio is a discretionary range, not a fixed entitlement. Builders and Founders publish numbers because they are fixed — everyone who qualifies gets exactly $1,000 or exactly $5,000. Portfolio awards vary by use case, projected consumption, company profile, and the strength of the attesting submission. Publishing a single number would either over-promise (most applicants would anchor on the ceiling) or under-sell (anchoring on the floor would discourage strong candidates). Removing the number lets AWS reviewers exercise discretion without setting a public expectation they then have to manage.

Reason two: Portfolio is gated, so a public number would invite applications AWS cannot accept through public channels. Builders and Founders have public forms because they are meant to be self-serve at scale. Portfolio is intentionally routed through VCs, accelerators, and partners — the gating is the point, because it lets AWS lean on those parties to pre-qualify candidates. Advertising "$100K" next to a tier that has no public form would generate a flood of direct requests that have nowhere to go, which is exactly the friction the gating is designed to avoid.

Reason three: the gated structure means the number is communicated through the channel, not the page. A VC with Portfolio access knows the range and conveys it to their portfolio. A partner filing via ACE knows the typical award and sets the founder's expectation during the engagement call. AWS does not need the public page to carry the figure because the people who can actually access Portfolio learn it from the party submitting on their behalf. The page is a marketing surface for the self-serve tiers; Portfolio lives in the partner and investor ecosystem.

The practical upshot for a founder: the absence of a dollar figure on the Activate page is not a signal that Portfolio is unattainable or that you are looking in the wrong place. It is a signal that you are looking at the wrong surface. The number ($100K typical) and the application (a partner-filed ACE record or a VC nomination) both exist — they just live in the gated channel rather than on the public page. Once you understand that, the "missing number" stops being a mystery and becomes a map: stop searching the public site for a form, and start finding the partner or investor who can file.

VIWhat a partner-filed Portfolio application actually contains

Because Portfolio is the one tier you cannot file yourself, it is worth seeing exactly what the partner submits on your behalf. The difference between a Portfolio award landing in two weeks and a silent downgrade often comes down to whether this record is built correctly.

ACE — APN Customer Engagements — is the gated portal AWS partners use to register customer opportunities, including credit applications. Partners at the Advanced and Premier tiers reliably have ACE submission rights; Select-tier partners may not have full rights, which is worth confirming before you rely on one. When a partner files a Portfolio credit application, they create a structured opportunity record. The core fields are:

• Customer name + URL — your company and its website, so the reviewer can verify you exist.
• Use-case description — one to three paragraphs the partner writes from your inputs, describing what you are building and how it uses AWS.
• Projected AWS consumption — itemized by service (EC2, ECS/Fargate, RDS, Bedrock, Lambda, S3, etc.), which is the single most scrutinized field.
• Engagement type — typically "build" or "migrate" for credit-eligible records, signalling what work accompanies the credits.
• Estimated deal size — projected annual AWS spend after the credits are exhausted, which is how AWS models the long-term value.
• Partner role — what the partner will actually deliver alongside the credit application (DevOps setup, migration, a Bedrock proof-of-concept, and so on).
• Funding-source request — which pool the partner is drawing from (Portfolio for the base, with Build for Startups or Bedrock POC requested separately if there is a genuinely distinct workload).

Two details about this record matter disproportionately. First, the projected-consumption field is where most awards are won or lost: a realistic, itemized projection ($3K–$15K/month for a typical Series-A) reads as credible, while a wildly inflated one ($200K/month from a ten-person team) gets the whole award downgraded for implausibility. Second, the funding-source field is where the absorption-versus-stacking rule shows up — a competent partner requests Portfolio for the general workload and only adds Build for Startups or Bedrock POC when there is a genuinely separate project to attach them to, because asking for additive pools against the same workload is a reliable way to get the secondary requests silently zeroed out.

VIIWhat the AWS reviewer looks for — and why some Portfolio awards get downgraded

AWS reviewers do not study each application in depth; they pattern-match against a checklist. Knowing that checklist explains why some Portfolio records sail through at $100K, why others get downgraded to $50K or less, and why a small number get rejected.

Partners who have filed hundreds of these report a consistent order of questions the reviewer runs through. None of them is mysterious — they are exactly the checks you would expect AWS to make before committing five figures of credits to a company it has never met.

• Is this a real company? — A verifiable website, a findable team, and some funding or traction signal. The overwhelming majority of submissions clear this; it is a sanity gate, not a hurdle.
• Is the use case genuinely AWS-heavy? — The reviewer wants to see real services in volume — compute, managed databases, Bedrock, Lambda — not a static site on S3. A thin use case caps the award regardless of company quality.
• Is the projected spend realistic? — This is the most common reason a $100K ask gets downgraded. Implausibly large projections from an early-stage team read as padding and pull the whole award down. Credible Series-A projections sit around $3K–$15K/month.
• Does the partner have a track record? — Partners with high ACE approval rates get their records read more favorably; brand-new partners draw extra scrutiny. This is why who files your Portfolio record materially affects the outcome.
• Is the company already on AWS? — Existing spend history makes a $100K ask self-evidently plausible. A brand-new account with no history asking for $100K leans entirely on the partner's attestation to carry the projection.
• Is the company an AWS competitor? — AWS will not fund companies that directly compete with its own services — other cloud providers, certain AI-infrastructure plays. A small fraction of applicants hit this filter, often without realizing their product overlaps an AWS service.

VIIIHow to climb the ladder — and why you climb rather than stack

The three tiers are rungs, not a shopping list. You move up them as your company changes, and a higher rung absorbs the lower one rather than adding to it. Understanding the graduation pattern tells you which tier to target now and what triggers the next move.

The clean progression looks like this. A brand-new team takes Builders ($1K) for an immediate, frictionless cushion. As the startup becomes real but stays self-funded, it graduates to Founders ($5K) through the same public form. Then the company raises an institutional round — or lines up an AWS partner — and jumps to Portfolio ($100K) through the gated channel. Each step up supersedes the last: Portfolio absorbs Founders, which absorbed Builders. You never hold two Activate tiers simultaneously; you hold the highest one you have qualified for.

This absorption rule is the single most misunderstood mechanic in the program. Founders see "$1K + $5K + $100K" and try to mentally add them to $106K. That is not how it works — the tiers are alternative awards on one ladder, not separate grants. The corollary is reassuring, though: because the smaller tiers absorb rather than block, there is zero penalty for taking Builders or Founders early. Grab the cushion now; it costs you nothing toward the larger award later.

The genuinely additive credits live outside the Activate ladder entirely. Build for Startups (commonly ~$25K) and Bedrock POC ($10K–$50K) are separate pools that can sit on top of a Portfolio award — but only when they fund a distinct workload. The reviewer will approve $100K of Portfolio for your general infrastructure plus, say, $25K of Bedrock POC for a clearly separate AI initiative; the reviewer will not approve both against the same product. So the real path past $100K is not stacking Activate tiers — it is attaching genuinely separate, credit-eligible workloads to additive pools that happen to be adjacent to Activate.

What triggers each move up is worth naming explicitly. The trigger from Builders to Founders is becoming a real startup with a real product plan. The trigger from Founders to Portfolio is one of two things: closing an institutional round (which unlocks the VC-nomination channel) or engaging an AWS partner willing to file via ACE (which unlocks the partner channel without needing a VC at all). If neither trigger has fired yet, Founders is your ceiling and that is fine — the $5K is real and sufficient for a pre-funding team. Once a trigger fires, the jump to $100K is a couple of weeks of someone else's work.

IXBuilders vs Founders vs Portfolio — the full comparison

Everything above, distilled into one table. If you read nothing else on this page, read this — it is the fastest way to see which tier matches your situation and what the jump between them actually costs you.