$25K AWS credits for bootstrapped founders — the partner-filed Founders ceiling, with no investor in the loop.

IWhy $25K is the right number to chase as a bootstrapped founder

The AWS credit ladder has structural break-points that aren't arbitrary. They correspond to which reviewer queue your application lands in and what signals that queue is calibrated to weigh. For bootstrapped founders, the queue that fits is the partner-filed Founders sub-program, and its documented ceiling is $25K.

Most bootstrapped founders arrive at AWS credits thinking about the published $100K Activate Portfolio number. That number exists, and it's real — but it lives in the Portfolio Sub-Program reviewer queue, which calibrates against institutional-funding signal: a VC partner in the Activate Portfolio Sub-Program submitting on your behalf, or a tier-1 accelerator (Y Combinator, Techstars, 500 Global, MISK, Antler) where the program-of-record has Activate access. Without one of those signals, the Portfolio reviewer queue isn't the right destination — the application either gets rejected outright or gets downgraded to a $25K Founders award after a 14–21 day delay. Either way, the bootstrapped founder ends up at Founders.

The Founders sub-program is the right starting point because its signal calibration matches bootstrapped reality. Reviewers in the Founders queue weigh use-case specificity, projected consumption realism, partner attestation quality, and founder context — not VC backing. They're explicitly running the queue that takes startups with no institutional vouch and funds the AWS portion of the build. The published Founders ceiling is $25K, and that's the number a bootstrapped founder should be planning around.

Below the $25K Founders ceiling, the $5K self-serve Activate Founders tier is the floor — accessible by filling in the public form at aws.amazon.com/startups/credits/ with no partner involved. That floor is fine for early experimentation, but it caps at $5K and is automatically tiered (no reviewer judgement involved). Above the $25K Founders ceiling, the next jump is Portfolio at $100K, which requires the institutional vouch. The space between $5K self-serve and $100K Portfolio is the $25K partner-filed Founders pool — and that's where bootstrapped founders should be filing.

There is no "$50K bootstrapped tier" in Activate documentation. Founders who report a $50K bootstrapped outcome are stacking the $25K Founders award with a $25K Bedrock POC award (Section IV). Founders who report higher than $50K bootstrapped are typically a different shape: $5M+ ARR with $50K+/year AWS spend, accessing the Solution Provider Program rather than chasing credit pools (Section VI). For the typical bootstrapped startup — pre-revenue or sub-$1M ARR, no AI workload — the practical ceiling is the $25K Founders award.

IIWhat reviewer math determines $25K vs the $15K typical award

The Founders sub-program documents a $25K ceiling and tells reviewers to assign awards within a $5K–$25K band based on use-case fit. The typical landing point is $15K. Pushing the award to $25K is a specific exercise — here is what the reviewers are actually weighing.

• Projected monthly consumption realism — Reviewers anchor the credit amount to projected 12–18 month consumption. A bootstrapped pre-seed startup projecting $5K/month reads as inflated and gets downgraded — reviewers know what pre-seed apps actually cost to run. The plausibility zone for the $25K ceiling is $800–$1.6K/month sustained; below that, you land at $15K (which covers the smaller projection); above that, you read as a Portfolio applicant in the wrong queue.
• Itemized AWS service projections — "We'll use a range of AWS services" reads as unscoped and lands at $5K–$10K. "ECS Fargate at $450/month for the API tier, Aurora Serverless v2 at $350/month for transactional storage, S3 at $90/month, CloudFront at $140/month, CloudWatch at $60/month, total $1,090/month projected" reads as scoped and lands at $20K–$25K. The itemization is what makes the projection credible enough for the reviewer to push toward the ceiling.
• Use-case specificity — "A SaaS for SMBs" is vague. "A B2B invoice automation SaaS where customers upload AP documents, we extract line items with Textract, store transaction records in Aurora, and surface reporting dashboards via CloudFront" is specific. The specific version reads as plausible to a reviewer and projects toward the ceiling.
• Partner attestation quality — The ACE record includes a partner-attestation field — a free-text comment from the filing partner. A boilerplate attestation ("Customer is interested in AWS") triggers reviewer suspicion and downgrades the award. An attestation that cites pre-vetting ("Use case validated on a 30-minute discovery call; itemized service projections reviewed against partner cost model; customer has an active AWS account with $X/month current consumption") pushes the award up. Partners who file high volumes of ACE records know which attestation language correlates with ceiling outcomes.
• Founder and team context — Founder background, team size, prior exits, technical depth, time-in-industry — soft signals that move the award within the band. A solo non-technical founder lands at $10K–$15K; a 3-engineer team with a CTO who previously shipped at scale lands at $20K–$25K. Reviewers can't weigh these officially, but in practice they move the dial.
• Accelerator membership (if applicable) — Bootstrapped doesn't mean accelerator-free. NASSCOM 10000 Startups, Flat6Labs, MISK Accelerator, regional accelerator programs — these all skew the award higher even without VC backing. The application captures accelerator membership; reviewers see it; the award skews up by $5K–$10K.
• Existing AWS spend signal — If your AWS account already has $200/month or more of legitimate consumption, reviewers read that as predictive of continued consumption. Empty accounts with no usage history default toward the $15K typical; accounts with 3+ months of consistent spend default toward $20K–$25K.

IIIWhy bootstrapped founders structurally land at Founders, not Portfolio

A frequent question from bootstrapped founders: "I have $1.5K/month in AWS spend, a real product, and 200 customers — why am I capped at $25K when seed-stage startups with no revenue get $100K?" The honest answer is structural, and worth understanding before you submit anything.

AWS's credit allocation is calibrated against longevity signal, not against current product traction. The institutional thesis is that a VC-backed company has been pre-vetted by a partner whose job is identifying companies that will exist in 24 months. AWS reads VC backing as a longevity proxy and unlocks the larger pool because the expected value of giving credits to that company is higher (the company is more likely to still be on AWS in 18 months). A bootstrapped company — even a profitable, well-built one — hasn't been through that institutional vetting, so the longevity signal isn't pre-validated. The reviewer queue defaults to the lower pool.

This isn't a value judgement on bootstrapped companies. It's an actuarial decision about which signal correlates with continued AWS consumption. Bootstrapped startups have a wider distribution of outcomes — some die fast (revenue dries up), some grow steadily, some scale exponentially with no further funding. The institutional-funded distribution is narrower (most VC-backed companies have 18+ months of runway by definition). AWS's credit machine optimizes for the narrower distribution because the credit accounting is simpler.

The structural fix isn't to argue with AWS — it's to file at Founders and stack with Bedrock POC if applicable. The $25K Founders award is structurally yours as a bootstrapped founder; the $100K Portfolio award structurally isn't. Time spent trying to access Portfolio without the institutional vouch is wasted; time spent pushing the Founders award from $15K typical to $25K ceiling pays back directly.

There is one exception: if you've raised an angel round of $250K+ and have one of your angels in a fund that participates in Activate Portfolio Sub-Program, that angel can sometimes vouch for the Portfolio application on behalf of the fund. This is rare in practice — most angel rounds don't have an Activate-eligible fund in the cap table — but it's worth checking. If your cap table includes a check from a fund like Initialized, Lerer Hippeau, Lightspeed, or another Activate-eligible source, ask them about a Portfolio vouch before defaulting to the bootstrapped Founders path.

IVThe bootstrapped + Bedrock POC stack: $25K → $50K without an investor

The single largest cap-table-blind credit pool AWS funds is Bedrock POC. If you're running or planning to run inference on Amazon Bedrock, the Bedrock POC track stacks on top of the $25K Founders award without conflict, taking the realistic bootstrapped ceiling from $25K to $50K — and occasionally higher.

Bedrock POC funding exists because Anthropic, Meta, Mistral, AI21, and Amazon's own Nova team are paying AWS marketing dollars to drive Bedrock adoption. That marketing budget routes into POC funding regardless of whether the consuming startup is VC-backed. The reviewer queue for Bedrock POC is calibrated to POC scope quality, not cap table — which makes it the most accessible large credit pool for bootstrapped founders specifically.

The eligibility test is simple: are you using Bedrock for real inference, with a defined use case, and an evaluation plan that can demonstrate commercial outcome? "Exploring AI for the platform" doesn't qualify. "Replacing human-tagged categorization of customer support tickets with Claude Haiku for 8K tickets/day, evaluating accuracy against the existing tagging baseline over a 90-day measurement window, projected commercial outcome is 60% reduction in support cost per ticket" qualifies. The POC plan is what the reviewer evaluates.

The floor for bootstrapped Bedrock POC awards is $10K (small scope, single-model evaluation, short measurement window). The typical award for a well-scoped bootstrapped POC is $15K–$25K — enough to fund 60–120 days of meaningful Bedrock inference at moderate volume. The ceiling for bootstrapped POCs with strong commercial-outcome attached is $25K–$30K; ceilings above that are reserved for VC-backed startups with bigger inference budgets.

Stacked with the $25K Founders award, the realistic bootstrapped total is $40K–$50K — $25K Founders + $15K–$25K Bedrock POC. The two ACE records get filed separately (one for Founders, one for Bedrock POC), often by the same partner on the same engagement, and the credits land in your AWS account as two separate balance lines: a general Founders pool ($25K, usable on any AWS service) and a Bedrock-earmarked pool ($15K–$25K, usable specifically on Bedrock inference and the supporting services around it).

A common mistake: founders who don't have an AI use case still try to add Bedrock POC to the stack. Don't. Reviewers can tell when a Bedrock POC plan was retrofitted onto a non-AI startup. The submission gets rejected, and the rejection sometimes triggers extra scrutiny on the parallel Founders application. If you don't have a real Bedrock workload, your bootstrapped ceiling is $25K Founders alone — file that cleanly, get approved, and move on.

VHow the $25K actually spends down across 18 months of bootstrapped operation

VIWhen bootstrapped becomes revenue-funded: the Solution Provider Program transition

Bootstrapped at sub-$1M ARR and bootstrapped at $5M+ ARR are structurally different conversations with AWS. Past a certain threshold, chasing credit pools stops being the right lever — the Solution Provider Program (SPP) and Enterprise Discount Program (EDP) become significantly more valuable.

The transition point sits around $5K/month of sustained AWS spend with predictable growth — typically corresponding to $1M ARR for a SaaS company. Below that threshold, the $25K Founders + Bedrock POC stack is the right play because it materially funds the build during a credit-relevant window. Above that threshold, the credit pool is small relative to your ongoing AWS bill ($25K covers about 5 months of $5K/month spend), and the structural game changes.

The Solution Provider Program is an AWS partner program where an approved partner becomes the reseller of your AWS bill. They take on the customer relationship, get a wholesale discount from AWS, and pass most of that discount through to you. Typical net pass-through: 8–12% off your AWS bill. For a bootstrapped company at $5K/month AWS spend ($60K/year), that's $4.8K–$7.2K/year of savings, compounding over a multi-year reseller contract. For a bootstrapped company at $20K/month AWS spend ($240K/year), that's $19K–$29K/year — equivalent to a fresh Founders award every single year, without any application process.

The Enterprise Discount Program is the direct version: AWS gives you a commitment-based discount in exchange for a multi-year minimum spend commitment. For bootstrapped companies at $10K+/month with predictable growth, EDP discounts of 10–20% are realistic. EDP doesn't require a partner intermediary — you negotiate directly with AWS Sales. The trade-off is the commitment: if your AWS spend drops below your committed minimum, you pay the shortfall. Bootstrapped companies with volatile growth should be cautious here.

Neither SPP nor EDP requires institutional funding. AWS treats revenue as a credible substitute for VC signal in these programs because the revenue is the AWS-customer-relevant signal — AWS Sales cares whether you'll continue spending, not how your equity is structured. This is why bootstrapped-but-profitable companies often end up in better economic positions than VC-backed startups: the VC-backed company gets $100K Portfolio credits once; the bootstrapped-profitable company gets 10–25% off their AWS bill perpetually.

If you're currently sub-$1M ARR, the right sequence is: file the $25K Founders + Bedrock POC stack now, exhaust those credits over the next 12–18 months while growing into the $1M ARR threshold, then transition to SPP or EDP once your AWS spend justifies it. CloudRoute routes the Founders filing today and routes the SPP transition when your revenue clears the threshold; the same partner relationship often spans both phases.

VIIA real bootstrapped $25K + Bedrock POC engagement — start to finish

Here's what the realistic flow looked like for a recent CloudRoute-routed engagement. Same architecture as the typical $25K bootstrapped path; minor variations in timing and award amount.

The startup: 4-person team building B2B agentic-workflow automation for e-commerce ops teams. Bootstrapped from founder savings ($180K runway), pre-revenue at engagement start, two pilot customers in active deployment. Stack: Next.js frontend, Python FastAPI backend on AWS, Aurora Serverless v2 for transactional storage, Claude Sonnet on Bedrock for the agentic reasoning layer, Lambda for tool execution.

The credit ask: $25K Founders for the platform infrastructure (compute, database, CDN, observability), $20K Bedrock POC for the agentic reasoning workload. Total target: $45K.

The Founders ACE record: Partner filed on day 5 of engagement. Itemized projections: ECS Fargate at $420/month, Aurora Serverless v2 at $310/month, CloudFront + S3 at $130/month, Lambda + Step Functions at $180/month, CloudWatch + log retention at $80/month, total $1,120/month projected. Use case described as "B2B SaaS for e-commerce operations automation, currently in pilot with two design partners, projected GA Q3 2026 with 30-target-customer cohort." Partner attestation cited pre-vetting on a 45-minute discovery call and verification of current pilot deployment.

The Bedrock POC ACE record: Filed in parallel on day 5. POC plan described Claude Sonnet for agentic reasoning across an inventory-restocking workflow, evaluation against human-tagged baseline over a 60-day measurement window, projected commercial outcome of "70% reduction in human ops time per restock decision." Partner attestation cited the existing pilot deployments as evidence of real workload (not exploratory). Projected Bedrock inference at 4M tokens/day across the active pilot cohort, scaling to 25M tokens/day at GA.

The outcomes: Founders approved at $25K (full ceiling) on day 11. Bedrock POC approved at $20K on day 13. Total credit balance: $45K, split across the general pool ($25K) and the Bedrock-earmarked pool ($20K). Both credits landed in the same AWS billing console under "promotional credits" with distinct line items.

The follow-through: The startup burned the Founders pool over 16 months (slightly slower than projected because they migrated to Graviton compute and saved ~15% on the compute line). Bedrock POC pool burned over 5 months as the agentic workload scaled to GA. By the time both pools were exhausted, the startup had reached $90K ARR with $1.4K/month AWS spend — too small for SPP transition but planning the move once they crossed $1M ARR.

The economics: Founder time across the engagement was approximately 3.5 hours total (CloudRoute inquiry, discovery call, document submission, follow-up). Wall-clock from CloudRoute inquiry to credits-in-account was 14 days. Cost to the founder was $0. The partner was paid by AWS's ACE-attribution and APN-funding programs; CloudRoute was paid a commission by the partner from their AWS funding. The founder never saw an invoice from anyone.

VIIIThe 14-day path from inquiry to $25K bootstrapped Founders approval

This is the path-of-least-resistance flow. Bedrock POC adds 2–4 days to the wall-clock if you're stacking it; otherwise the timeline is identical.

Day 0 — Submit a CloudRoute inquiry. State that you're targeting partner-filed Founders for the $25K ceiling, bootstrapped (no institutional funding), and whether you have a Bedrock workload to stack. ~3 minutes.

Day 1 — Routed within 24 hours to a partner who works with bootstrapped startups specifically. Bootstrapped routing is different from generic Activate routing; partners who file high volumes of bootstrapped Founders ACE records understand the reviewer math.

Day 1–2 — In parallel, file the self-serve Activate Founders application at aws.amazon.com/startups/credits/. The $5K self-serve lands in 3–5 days and bridges your AWS consumption during the partner-filed application window. The self-serve and partner-filed pools don't conflict.

Day 2 — 30–45 minute discovery call with the partner. Confirms eligibility, itemizes AWS service projections against partner cost model, defines the use case description, decides whether to stack Bedrock POC.

Day 3–4 — You provide company info, AWS account ID, deck (10 slides), use case paragraph, projected service usage. Time investment: ~25 minutes.

Day 5 — Partner files the Founders ACE record. If Bedrock POC is in scope, partner files the second ACE record in parallel. Both records go into the same reviewer queue and are typically reviewed within 2 days of each other.

Day 8–10 — AWS reviewer assigns the application. Bootstrapped Founders applications with itemized projections and clear use cases typically land in the $20K–$25K range. Bedrock POC applications with defined evaluation methodology typically land at $15K–$25K.

Day 11–14 — Credits land in your AWS billing console under "promotional credits." Founders credits are usable across all AWS services with 12-month validity. Bedrock POC credits are earmarked for Bedrock inference and supporting services with a 6-month POC measurement checkpoint.

Total founder time: ~30 minutes for Founders alone; ~50 minutes if stacking Bedrock POC. Wall-clock: 14 days. Cost: $0.