$1K is the Activate Builders tier — the smallest published AWS Activate award and the only one that does not require an incorporated company. The credit is a promotional code distributed through the self-serve Activate form to any registered AWS account holder; auto-issuance typically completes within 24 hours. This page covers exactly what Builders is, who actually qualifies, when $1K is the correct ask, when it is not, and how the $1K stacks with Free Tier and with the $5K Founders tier above it.
The Activate Builders tier sits at the bottom of the AWS Activate credit ladder. It is the smallest credit pool AWS publishes, the only one available without company incorporation, and the only one issued through a promotional code rather than through the partner-attested ACE workflow. The mechanic is intentionally simple — Builders is the on-ramp tier, and AWS calibrates it for individuals who are still deciding whether they will become AWS customers at all.
The Builders tier is administered through the AWS Activate console at aws.amazon.com/activate. The form is shorter than the Founders form — it does not ask for a company name, a company URL, or an incorporation country. It asks for the AWS account ID, the applicant's name and email, a one-sentence description of the project, and a confirmation that the applicant is not building a workload that competes directly with AWS itself (the only meaningful screening question on the Builders track).
Awarded credits arrive as a promotional credit code — a string the applicant redeems through the AWS billing console under "Billing → Credits → Redeem credit." Once redeemed, the credit functions identically to the Founders promotional credits: it auto-applies against monthly AWS invoices, AWS-native services (EC2, ECS, RDS, S3, Lambda, CloudFront, etc.) consume the credit first, and Marketplace charges plus support fees plus Reserved Instance upfront payments are excluded.
The Builders credit carries a 12-month validity from the redemption date — not from the issuance date. This is a useful nuance: if the credit code arrives but the applicant is not yet ready to use it, the validity window does not start counting down until the code is actively redeemed. At very low projected burn ($100–$200/month) this allows a founder to hold the credit code until the workload is real enough to consume it efficiently.
The tier is funded directly out of AWS's top-of-funnel acquisition budget. The strategic intent on AWS's side is to bring individuals into the AWS billing console early — once an account has consumed AWS credits and has billing history, the conversion rate to a paid AWS customer is materially higher than for individuals who never created an account. The $1K is small enough that the verification cost can be near-zero (automated screening with no human review for the vast majority of applications) and large enough that the credit's presence in the billing console feels meaningful to the founder who receives it.
The Builders eligibility bar is the lowest on the Activate ladder. There is no incorporation requirement, no entity check, no minimum company age, no projected-burn worksheet. The check is essentially: does the applicant have a real AWS account, are they in a non-sanctioned region, and is the use case something other than direct AWS competition.
The Builders tier is the fastest credit issuance AWS does. The combination of a low screening burden, automated decisioning, and a promotional-code distribution mechanic means most applications resolve within 24 hours of submission. Same-day issuance is common for clean applications submitted during US business hours.
The mechanical timeline: the Activate Builders form submits to an automated screening pipeline. The pipeline checks the AWS account ID for validity, checks the billing-address country against the sanctions list, checks the use case description against a banned-pattern list (competitor language, cryptocurrency mining, ad fraud), and confirms there is no prior Builders award on the account ID. If all checks pass, an approval is auto-issued and the promotional credit code is emailed to the applicant.
For founders who submit a well-formed application in the morning Pacific time, the credit code typically arrives by end-of-business-day Pacific. For applications submitted outside US business hours, the typical window is the next US business morning. Edge cases — accounts created within the prior 24 hours, applicants from regions where verification needs an extra check, or applications with use case language that pattern-matches against banned categories — can extend to 48–72 hours, but these are exceptions.
This is materially faster than every other AWS credit pool. The Founders self-serve tier ($5K) takes 3–7 days because the entity check and use case review require either an automated entity-verification step or a human spot-check. The partner-filed Founders tier ($25K ceiling) takes 10–14 days because the ACE record requires partner submission, AWS reviewer assignment, and a more substantive projection review. The Portfolio tier ($50K–$100K) takes 14–21 days. The Builders 24-hour window is genuinely unique on the Activate ladder.
A practical consequence: founders who need credits in the AWS billing console immediately — for a customer demo tomorrow, to cover a billing-cycle close, to unblock a small project that has hit a free-tier limit — should default to Builders rather than to Founders. The $1K covers less, but the speed difference matters when the deadline is tighter than the Founders 3–7 day window allows. Many founders later layer the Founders $5K on top once the immediate need is unblocked.
| Burn rate | Monthly AWS spend | Months covered | Profile fit |
|---|---|---|---|
| Very light | $80/month | 12.5 months (capped at 12) | Pure learning, single Lambda function, free-tier-heavy stack |
| Light | $150/month | ~6.7 months | Side project, single-region small app, S3 + Lambda + DynamoDB |
| Light-typical | $200/month | ~5 months | Bootstrapped solo founder, small MVP scaffolding |
| Moderate | $300/month | ~3.3 months | Active MVP development, ECS Fargate + RDS dev instance |
| Moderate-heavy MVP | $400/month | ~2.5 months | Multi-service MVP with observability, dev + small staging |
| Heavy MVP | $600/month | ~1.7 months | Pre-production MVP — $1K runs out before validation completes |
| Production | $1,000/month+ | < 1 month | $1K is materially insufficient — Founders or partner-filed needed |
The $1K Builders tier is the right answer for a specific set of founder profiles. Outside these profiles, $5K Founders or a partner-filed application is the better target. The four profiles below are where Builders is the correct primary ask — not as a fallback after a Founders rejection, but as the right submission to file first.
The opposite case: when $1K leaves real money on the table and the founder should skip the Builders form for a higher target. These profiles should default to either the Founders self-serve $5K, the partner-filed Founders track, or the Bedrock POC track depending on the workload.
Builders and Founders are separate sub-programs within Activate. The single-issuance limits apply within each sub-program independently, which means a founder who claims Builders $1K can later claim Founders $5K on the same account without triggering the duplicate-application check. The combined starting pool is $6K self-serve, which materially extends pre-MVP runway for solo founders.
The mechanical detail: when an applicant claims Builders, the Activate ledger records a Builders issuance against the AWS account ID. When the same applicant later incorporates and applies for Founders, the ledger checks for a prior Founders issuance, not a prior Builders issuance — so the second application is processed normally. The reviewer treats the Founders application on its own merits (entity verification, use case review, eligibility region check) and issues the $5K independently.
The credits sit in the billing console as separate promotional credit entries. Both auto-apply against monthly invoices in order of expiration date, with the earlier-expiring credit (typically the Builders $1K, since it was redeemed first) consumed first, followed by the Founders $5K once Builders is exhausted. AWS does not differentiate between the two credit sources in the consumption math — they apply against the same services, with the same exclusions, in the same auto-application logic.
The combined $6K position is meaningful at pre-MVP scale. At $200/month projected burn, $6K covers 30 months — well past the 12-month validity window of the Builders credit and approaching the validity window of the Founders credit. At $400/month projected burn, $6K covers 15 months. The pattern is common enough among bootstrapped solo founders that it has become an unwritten standard: claim Builders first, incorporate within the first 60 days, claim Founders in month 2 or 3, run the combined pool through the pre-revenue validation window.
A specific sequencing consideration: the Builders 12-month validity starts at redemption. If a founder claims Builders, redeems immediately, then claims Founders 3 months later, the Builders credit has 9 months of validity remaining when Founders arrives. The Founders 12-month window then begins. Total validity coverage across both credits is roughly 15 months from the initial redemption, depending on the timing of the Founders application and the burn rate against each pool.
Y Combinator companies are often confused about whether they can stack the $1K Builders credit on top of the $5K YC-issued Founders credit. The honest answer: no. YC's $5K is issued through the same Activate program ledger that issues the Builders $1K and the public Founders $5K — and the ledger treats them as belonging to the same Activate sub-program family for duplicate-detection purposes.
The mechanic: when a YC company is accepted, YC's batch integration with AWS auto-issues the $5K Founders credit to each accepted company. The Activate ledger records a Founders issuance against the company's AWS account ID. If the same founder later applies for the Builders $1K through the self-serve form, the ledger flags the application as a duplicate-attempt within the broader Activate family and denies the second issuance. The credit code never sends.
This is the opposite of the Builders-then-Founders stacking pattern described above. The asymmetry comes from the order of issuance and the program-family logic: Founders-issued-first blocks a subsequent Builders application, but Builders-issued-first does not block a subsequent Founders application. The mechanic exists because Founders is structurally a superset of Builders in the Activate model, and AWS does not double-fund the same program intent.
The practical implication for YC founders: the $5K is the entire self-serve Activate position. The next move upward is the partner-filed Founders track, which can add up to $20K incremental (reaching the $25K Founders ceiling), and the Bedrock POC track if there is an AI workload ($10K–$50K independent). Filing for Builders separately is wasted time — the application will be denied within hours and no credit will issue.
The same logic applies to Techstars, Antler, 500 Global, and other accelerators with auto-issuance batch integrations. If the accelerator's standing arrangement issues the $5K Founders credit, a subsequent Builders application is blocked. If the accelerator issues a smaller credit (some regional accelerators issue $1K through the Builders sub-program), the founder can later apply for Founders through the standard mechanic. The check is whether Founders has been issued, not whether any credit has been issued.
Founders frequently conflate the AWS Free Tier with the Builders $1K credit. They are entirely separate programs with different mechanics, different eligibility, and different consumption logic. Critically, Builders stacks on top of Free Tier — combined first-year coverage against billed services can reach approximately $1,200.
The AWS Free Tier has two components. The first is a $200 promotional credit issued to new AWS accounts within the first 6 months of account creation, redeemable against AWS service charges. The second is 12 months of free usage of a specific subset of AWS services up to defined monthly limits — examples include 750 hours/month of t2.micro or t3.micro EC2 usage, 750 hours/month of RDS db.t2.micro or db.t3.micro usage, 5GB of S3 standard storage, 1 million Lambda invocations per month. Beyond the free-tier limits, normal pricing applies.
The Builders $1K is a separate promotional credit issued through the Activate program. It applies against any AWS service consumption that is billed — meaning it applies against the consumption that exceeds Free Tier limits. A founder who stays within Free Tier limits never consumes the Builders credit at all; the credit remains in the account waiting for billed consumption.
Combined first-year coverage works as follows: the Free Tier $200 credit consumes first (it has a shorter expiration window — typically 6 months from account creation). The Free Tier usage allowances consume the equivalent monetary value of the supported services at no charge. The Builders $1K consumes against any remaining billed consumption. Total promotional credit coverage in year one for a new AWS account that also claims Builders: approximately $1,200, plus the value of the Free Tier usage allowances (which can be material — a small app running on t2.micro plus 5GB S3 standard storage operates entirely within Free Tier and costs $0 even without credits).
A practical illustration: a solo founder building a personal-finance SaaS MVP on a single t2.micro EC2 instance (covered by Free Tier hours) plus a small RDS instance (covered by Free Tier RDS hours) plus 3GB S3 storage (covered by Free Tier storage) plus a Lambda function (covered by Free Tier invocations) operates at near-$0/month for the first 12 months. As the workload scales past Free Tier limits — adding a second instance, exceeding the RDS storage allowance, adding CloudWatch metrics — the billed consumption begins. The $200 Free Tier credit covers the first $200 of billed consumption; the Builders $1K covers the next $1,000. Combined: $1,200 of credit coverage layered on top of an undisclosed amount of Free Tier service consumption.
For founders specifically optimizing for "longest possible runway on $0 cost," the Free Tier + Builders combination is the maximum self-serve coverage available without incorporation. Adding Founders $5K (which requires incorporation) extends the total combined coverage to roughly $6,200 of promotional credits plus the Free Tier service allowances.
Most founders who file for Builders eventually layer Founders and partner-filed Founders on top within 6–12 months as their AWS use cases mature. The graduation pattern is the standard trajectory through the Activate ladder for solo founders and bootstrapped teams, and understanding the sequencing helps founders plan their AWS credit position over multi-year horizons.
Month 0 — Builders claim. The founder is pre-incorporation or just incorporated. The use case is a side project or pre-MVP exploration. Burn rate is $80–$200/month. Builders is claimed through the self-serve form, redeemed immediately or held, and begins consuming against AWS bills as the workload starts to generate billed consumption beyond Free Tier limits.
Month 2–4 — Founders claim. The founder has incorporated (often using Stripe Atlas, Clerky, doola, or Firstbase) and the workload has graduated to MVP scale. Burn rate has climbed to $200–$500/month. Founders $5K is claimed through the self-serve form. Approval lands in 3–7 days. The Builders credit continues to consume in parallel until exhausted, at which point Founders takes over.
Month 6–9 — Partner-filed Founders evaluation. The MVP is real, the workload is projectable, and the burn rate has climbed to $700–$1,400/month. The founder evaluates whether the partner-filed Founders track ($25K ceiling) is appropriate. The 18-month projection math: at $1,000/month for 18 months, total projected consumption is $18K, which the reviewer rounds to the $15K–$20K landing within the Founders ceiling. The partner-filed application is filed; credits land in 10–14 days.
Month 10–12 — Bedrock POC or Build for Startups layer. If the product has developed an AI feature on Bedrock, the Bedrock POC track is added ($10K–$50K). If a second workload has emerged (data pipeline, transcoding, internal analytics) that is distinct from the primary product, Build for Startups is added ($15K–$25K typically). These layers stack on top of the partner-filed Founders position.
Month 12+ — Either Portfolio (if institutional funding has been raised) or the next round of partner-filed Founders (single-issuance per legal entity is per sub-program, but partner-filed Founders has more flexibility on re-application than self-serve Founders). Cumulative credit position from a clean graduation pattern over 12 months: $1K Builders + $5K self-serve Founders + $15K partner-filed Founders + $10K Bedrock POC = $31K, against a 12-month combined consumption window of roughly $12K–$15K. The credit surplus carries the company through the entire first year of operation at $0 AWS cost.
The pattern is not universal — many founders compress the timeline (claim Builders and Founders within the same week, then partner-filed within 60 days), and some founders skip Builders entirely (incorporating immediately and starting at Founders). But the underlying logic — small immediate award now, larger partner-filed award once consumption is projectable — is consistent across nearly every successful credit-stacking trajectory.
A common founder objection to the Builders tier: "$1K is meaningless — why bother with the form?" The objection makes sense at the wrong reference frame. Against the $5K Founders comparison or the $25K partner-filed comparison, $1K does look small. Against the actual burn rate at the pre-MVP stage, $1K is 4–6 months of runway. The reframing matters.
The arithmetic is the load-bearing argument here. A solo founder spinning up a new AWS account and building a side project consumes roughly $150–$300/month after Free Tier limits are exhausted. At that burn rate, $1K of credits covers 3.3 to 6.7 months — a full quarter to a full half-year of pre-MVP development. For a side project that may or may not become a real company, this is genuinely meaningful runway, not a token amount.
The misconception comes from anchoring on the wrong number. Founders who have seen $25K, $50K, or $100K credit pools mentioned in startup forums anchor against those numbers and read $1K as small. But the founders for whom those numbers are appropriate are at a different stage entirely — institutional funding, real production workloads, projected burn at $1K–$3K/month or higher. At those stages, $1K is indeed materially insufficient. At the Builders stage, $1K is exactly calibrated to the burn rate of the target applicant.
There is also a stage-pressure dynamic worth surfacing. Founders working at pre-MVP scale often feel anxious about cost — the AWS bill arriving with $200 of charges feels meaningful when there is no revenue covering it. $1K of credits substantially reduces that pressure across the 4–6 month window where the founder is still deciding whether the project is worth pursuing. The psychological value of "no AWS bill for the next quarter" is materially higher than the dollar amount suggests.
The honest framing: if the founder is genuinely at pre-MVP scale and the project might not survive the next 6 months, $1K Builders is the correct ask. If the founder is past pre-MVP — has revenue, has institutional funding, has a real workload — $1K is the wrong ask and a higher pool should be targeted. The framing depends entirely on stage, not on the absolute dollar amount.
A realistic Builders-plus-Founders trajectory for a solo founder. The example anonymizes identifying details but the numbers, timing, and sequencing are representative of the founder profile that lands cleanly on the Builders + Founders combined $6K self-serve position.
The founder is a software engineer based in the US East coast, working full-time at an established tech company, with a side project for a personal-finance SaaS targeting individual consumers. The side project has been in concept for 8 months and the founder is ready to start building. The plan is to launch a closed beta within 4 months, then evaluate quitting the day job based on early traction.
Month 0: The founder creates a fresh AWS account in their personal name. Account creation completes; payment method (a personal credit card) is on file. They apply for the Builders $1K through the self-serve form, citing "building a personal-finance dashboard using DynamoDB, Lambda, API Gateway, and Cognito." The application is auto-approved within 18 hours. The promotional credit code arrives by email; they redeem it the same day. Initial monthly AWS burn: ~$40/month, almost entirely covered by Free Tier allowances.
Month 2: The founder incorporates a single-member LLC in Delaware using Stripe Atlas. Incorporation takes 4 business days and costs $500 including the registered agent. Once incorporated, they create a new AWS account in the company name (the personal account is left as-is, with the Builders credit continuing to consume against the side-project workload). They apply for Founders $5K through the self-serve form, citing the same use case with company entity details. Approval lands in 5 days. The Founders credit is redeemed and posted to the company AWS account.
Month 3–4: The MVP closed beta launches with 18 invited users. AWS burn climbs to ~$280/month — Cognito user pool, DynamoDB on-demand tables, Lambda invocations, S3 for receipt-image storage, CloudFront for the SPA frontend, RDS for analytical reporting. The Builders $1K (on the personal account, hosting the development environment) is at roughly $400 remaining. The Founders $5K (on the company account, hosting the beta) is at roughly $4,400 remaining.
Month 6: Beta has expanded to 80 users. Burn rate on the company account is ~$500/month. The founder has not yet quit the day job but has started monetizing the beta — $7/month per user, $560/month in revenue. The Founders $5K balance is at roughly $3,400 and projected to last through month 12. The personal account Builders credit is exhausted; the development environment has been migrated to the company account.
Month 11: The beta has stabilized at 240 users, $1,680/month in revenue, and AWS burn at ~$650/month. The Founders $5K is at roughly $400 remaining and projected to exhaust at month 12. The founder evaluates whether to pursue the partner-filed Founders track ($25K ceiling) — projected burn for the next 18 months at $1K/month equals $18K, which the reviewer would land at the $15K–$20K range. They submit a partner-filed inquiry and route to a CloudRoute partner.
Total Builders + Founders coverage: $6,000 across 11 months of pre-revenue and early-revenue operation. Total AWS cost to the founder across those 11 months: $0. The Builders + Founders combined pool covered the entire MVP and early-traction phase, and the founder transitions to partner-filed Founders for the next phase with a clean credit history and a partner relationship.
The three lowest-effort AWS funding mechanics for early-stage founders, with the trade-offs that determine which combination is right at each stage. Most solo founders end up using all three in combination over the first 12 months.
| Variable | AWS Free Tier (default) | $1K Builders self-serve | $5K Founders self-serve |
|---|---|---|---|
| Eligibility | Any new AWS account | Any individual with AWS account | Incorporated company (LLC, C-Corp, intl) |
| Application form | Auto-enrolled at account creation | aws.amazon.com/activate (Builders) | aws.amazon.com/activate (Founders) |
| Founder time | 0 min (automatic) | ~3 minutes | ~5 minutes |
| Approval window | Immediate | < 24 hours | 3–7 days |
| Award amount | $200 credit + service allowances | $1K fixed promotional credit | $5K fixed promotional credit |
| Reviewer process | None — automatic | Automated screening | Automated + spot-check |
| Validity | $200 credit: 6 months; allowances: 12 months | 12 months from redemption | 12 months from issuance |
| Stack-friendly with the next tier? | Yes — Builders stacks on top | Yes — Founders stacks on top | Yes — partner-filed stacks on top |
| Best for | First 12 months on AWS, any workload | Pre-incorporation experimentation | MVP-stage with incorporation |
Situation: Solo technical founder building a personal-finance SaaS MVP. Started on a personal AWS account in month 0; incorporated Delaware LLC in month 2 via Stripe Atlas. Planned 4-month closed beta with projected $200–$500/month burn across DynamoDB, Lambda, API Gateway, Cognito, S3, and CloudFront. Wanted both Builders (to cover the pre-incorporation development phase on the personal account) and Founders (to cover the beta phase on the company account) without paying out of pocket.
What CloudRoute did: Month 0: Applied for Builders $1K through the self-serve form on the personal AWS account, citing "personal-finance dashboard with DynamoDB and Lambda" as the use case. Auto-approved in 18 hours. Redeemed the promotional credit immediately. Month 2: Incorporated Delaware LLC via Stripe Atlas. Created a fresh company AWS account. Applied for Founders $5K through the self-serve form on the company account, citing the same use case with entity details. Approved in 5 days.
Outcome: Combined $6K self-serve credit position across two AWS accounts. Builders $1K consumed against personal-account development workload over months 0–4. Founders $5K consumed against company-account beta workload over months 2–11. Total coverage: 11 months of pre-revenue and early-revenue operation at $0 cost. At month 11, founder transitions to partner-filed Founders track for the next consumption window. Customer cost across the Builders + Founders self-serve phase: $0.
engagement windows: Builders < 24h, Founders 5 days · founder time: ~10 minutes total · credits secured: $6K combined · cost to customer: $0
For solo founders, side-project experimenters, and pre-incorporation builders, the Builders $1K is the right immediate ask. For everyone else, the $5K Founders or a partner-filed track is the better target. CloudRoute helps you confirm which tier fits — and routes the partner application if a larger pool applies. Customer pays $0 either way.