IMMERSIVE COMMONS/ FT10
The Vault · Hyperscaler / infra cloud · unproven

AWS Activate

Three tiers with very different gates: $1,000 self-serve for bootstrapped founders, $100,000 for portfolio companies with an Activate Provider Org ID, and up to $300,000 for AI/foundation-model companies.

First-try successnot yet measuredNo one has reported running this yet. Below 5 answers a “rate” is one person’s experience wearing a percent sign, so we publish nothing rather than something false.

Ran this? Answer two questions — did it work first try, and if not, which step broke — via the ic_vault_feedback_submit MCP tool or POST /api/vault/feedback. An entry with no answers has no rate, and that is the honest state, not a placeholder.

Offers

3 distinct offers under one brand name, each behind its own gate.

AI / foundation-model tier

AI/foundation-model tier up to $300,000.

How you get in
partner-gated
Published ceiling
$300,000
Contact
AWS Activate portal

Apply ↗

Portfolio tier

Up to $100,000 (+$10K Business Support).

How you get in
partner-gated
Published ceiling
$100,000
Contact
AWS Activate portal

Apply ↗

Founders tier

Founders tier: up to $1,000 (self-serve).

How you get in
self-serve
Published ceiling
$1,000
Contact
AWS Activate portal

Apply ↗

Who this is for

Founders: bootstrapped, active AWS account, website, <10yr. Portfolio: Seed/Series A funding within last 12 months + an Organization ID from an AWS Activate Provider.

To have this checked against your own facts, call ic_vault_match. It answers in three values — you qualify, you do not, or we cannot tell from what the vendor publishes — and it will never report “you qualify” while any gate is unknown.

Traps

Every one of these cost real time. Ordered by how early they bite.

  • T1 — IC's Activate-Provider move is an OPERATOR lever, not your prerequisite

    Becoming an AWS Activate PROVIDER is something IC does to issue its cohort an Org ID. It runs in the opposite direction from an applicant prerequisite and is deliberately NOT modelled as one. Verbatim from the source: *"IC lever: become an AWS Activate PROVIDER (accelerator/incubator/community org) to issue your cohort an Org ID that unlocks the Portfolio tier. Provider application is self-serve online (AWS Builder ID + Activate profile). A source claiming Providers are VC-only was rejected in verification."*

    Source: data/credits.ts AWS Activate .note · docs/vault/SCHEMA.md § 4

  • T2 — The NVIDIA Inception edge is claimed by only one side

    NVIDIA Inception's value string claims it unlocks "elevated AWS tiers". This entry never mentions Inception, and AWS's own stated gate is an Org ID from ANY Activate Provider — Inception is at most one route among several, not the gate. The edge is modelled `one-sided` on the Portfolio and AI tiers so it is walkable, but treat it as unverified until AWS corroborates it.

    Source: data/credits.ts NVIDIA Inception .value · docs/vault/SCHEMA.md § 4

  • T3 — The Founders tier requires being BOOTSTRAPPED

    Raising anything disqualifies you from the $1,000 self-serve tier — it does not upgrade you. The Portfolio tier is a different application with a different gate.

    Source: data/credits.ts AWS Activate .eligibility

  • T4 — No gate is published for the $300,000 AI tier

    The source names the tier and its ceiling and states no eligibility for it. Its tier-level `eligibility` is deliberately absent rather than guessed.

    Source: data/credits.ts AWS Activate .value vs .eligibility

Sources

  • data/credits.ts — "AWS Activate" .value (verbatim) data/credits.ts — Founders tier: up to $1,000 (self-serve). Portfolio tier: up to $100,000 (+$10K Business Support); AI/foundation-model tier up to $300,000.
  • data/credits.ts — "AWS Activate" .note (verbatim) data/credits.ts — IC lever: become an AWS Activate PROVIDER (accelerator/incubator/community org) to issue your cohort an Org ID that unlocks the Portfolio tier. Provider application is self-serve online (AWS Builder ID + Activate profile). A source claiming Providers are VC-only was rejected in verification.
  • CREDITS_META.lastUpdated — a lower bound on last_verified data/credits.ts — The file records 2026-07-07 as when the FILE was updated, not when this entry was individually re-checked.
  • AWS Activate — apply page ↗

Facts last re-checked 2026-07-07 (from the source itself). No material change observed since — which is not the same as none having happened.

Link your terminal

Connecting to relay

Run this in the terminal where Claude Code lives. Your session then sees the tools below and runs them in this tab, as you. Anything consequential asks you here first.

Asking the relay for a code.

0 tools on this page:

What your terminal can see: the text on this page that you can see, minus dialogs and anything the page marks private, plus the URL and title. Never your sign-in.

This code is for this tab only and stops working when you close it. The relay never sees your sign-in; tools run here, in your browser.

Your terminal wants to run a tool