Antler is the only major global accelerator that accepts founders before team formation, runs a six-month residency in Singapore, Berlin, Sydney, Stockholm, Nairobi, Bangalore, São Paulo, Riyadh and 20+ other cities, then writes pre-seed checks of $100K–$250K into the companies that come out of it. Antler is also the only major global accelerator NOT inside the AWS Activate Portfolio Sub-Program directly — unlike Y Combinator, Techstars, or 500 Global. The standing AWS credit code distributed at residency start ranges from $1K to $5K depending on location; the partner-filed Portfolio path via ACE adds another $50K–$75K on top. This page walks through how Antler portfolio companies actually unlock the full $95K–$130K stack, why the pre-team-formation model creates a specific incorporation-timing gotcha, and which regional follow-on VC patterns shape partner matching.
Antler is structurally different from every other major global accelerator, and that difference shapes how AWS Activate interacts with Antler portfolio companies. Understanding the model is the first step to understanding why the credit path is unusual.
Antler is headquartered in Singapore. It runs residencies in more than 30 cities, including Singapore, Sydney, Melbourne, Berlin, Stockholm, Oslo, Copenhagen, Amsterdam, London, Toronto, New York, Austin, Bangalore, Jakarta, Ho Chi Minh City, Seoul, Tokyo, Nairobi, Lagos, São Paulo, Mexico City, Bogotá, Riyadh, Dubai, and others. Each residency operates a roughly six-month cycle, with one or two cohorts per year per location. At any given moment Antler is running active residencies across half a dozen continents.
The model is the unusual part. Antler accepts individual founders rather than teams. Applicants are not required to have a co-founder, a company, or even a fully-formed idea at the point of acceptance. The first portion of the residency (typically six to eight weeks) is dedicated to co-founder matching and idea exploration: founders work in shared space, run paid exercises with each other, prototype ideas in micro-teams, and converge toward two- or three-person founding teams by the time the back half of residency begins.
Once teams are formed and ideas are scoped, Antler runs an investment committee process. Selected companies — typically 10 to 20 out of the original 50 to 100 founders in a residency — receive pre-seed capital ranging from $100K to $250K depending on the residency location and the commercial profile of the company. Antler's pre-seed check is the source of capital that funds the company's first six to twelve months post-residency, during which the typical Antler-backed company prepares to raise a seed round from regional tier-one VCs.
The pre-team-formation model is the reason Antler is structured differently from YC, Techstars, or 500 Global. YC accepts teams with companies already incorporated; Techstars accepts teams with at least a working prototype; 500 Global tends to accept companies with some traction. Antler accepts solo founders pre-incorporation. By the time a founder is six weeks into Antler, they may have a co-founder, an idea, and the early outline of a company — but the incorporated legal entity does not yet exist for most companies until residency weeks eight through twelve. This timing is the central operational fact that shapes the AWS credit path.
AWS Activate has a Portfolio Sub-Program with a published list of institutional partners. YC, Techstars, and 500 Global are inside that list. Antler is not — despite Antler being a comparable accelerator by check size and graduate count. The structural reason matters.
The Portfolio Sub-Program operates as a standing arrangement between AWS Activate and the participating accelerator. The accelerator commits to certain volume of portfolio companies routed through Activate; AWS commits to standing approval thresholds for those portfolio companies; the two organizations integrate at the operational level (batch lists shared, eligibility verification automated). YC, Techstars, and 500 Global have multi-year standing arrangements at this level.
Antler has not historically had this standing arrangement. The reason is structural: Antler's pre-team-formation model means the "portfolio company" identity does not exist at the start of residency. AWS Activate's eligibility model expects a defined customer record — a company name, an incorporation, a use case. At residency week one, an Antler founder is a person without a company; the customer record AWS wants to verify does not yet exist. This timing mismatch makes the standing arrangement awkward to operate at scale.
What Antler has instead is a growing set of regional AWS partner relationships. Antler Singapore has working relationships with several APAC AWS partners; Antler Berlin works with EU AWS partners; Antler Nairobi works with the small set of partners operating in af-south-1 (Cape Town). These regional partner relationships are the mechanism through which Antler portfolio companies access partner-filed Portfolio applications. The institutional signal is real — Antler's name on an ACE submission carries weight — but the path is partner-filed rather than auto-issued.
The practical implication: Antler portfolio companies who only redeem the standing residency credit code (the $1K–$5K Activate Founders code distributed at residency kickoff) are stopping at the floor. The partner-filed Portfolio path adds another $50K–$75K, and that path is structurally available through Antler's regional partner network. The path requires an incorporated entity and an active use case — both of which exist by the back half of residency for most Antler companies.
Every Antler residency distributes an AWS Activate credit code during residency weeks one to two. The amount varies by location: residencies that operate in regions with active AWS partner ecosystems tend to receive larger codes; residencies in newer regions receive smaller codes. The range is $1K to $5K.
The code is distributed via the residency Slack workspace, the residency portal, or in-person at one of the residency-week onboarding sessions. The Antler partner team at each location is responsible for the distribution; in some locations this is done by the dedicated platform team, in others by the partner team itself. If you joined residency and have not received a code by week three, the right contact is your residency's Platform Lead or the partner running founder support.
To redeem: you need an AWS account. Most Antler founders do not have an AWS account at residency start (many have used GCP or Azure in prior work, or have used a personal AWS account that should not be re-used for the company). Create a fresh AWS account using a professional email — ideally your residency email or a placeholder company domain. Navigate to the AWS Activate Console at aws.amazon.com/activate/. Enter the code in the "Apply credit code" or "Redeem" section. The promotional credit appears in your Billing console within 24 to 48 hours.
Validity: 12 months from redemption. At residency-phase AWS consumption (typically $50–$300/month, given most pre-team-formation prototyping uses Vercel, Supabase, or shared infrastructure), the $1K–$5K code lasts 4 to 12 months. The runway is meaningful for the residency window itself, less so for post-residency scaling.
Worth knowing: the standing residency code and the partner-filed Portfolio path are in the same Activate program at different ceilings. When Portfolio is approved, it absorbs the Founders/Builders tier rather than stacking. You end up with $50K–$75K Portfolio total, not Portfolio + the original $5K. The standing code is operationally useful during the partner-filed application window — you have credits available immediately while the partner-filed Portfolio takes 18 to 25 days to land — but it is not additive to the final ceiling.
The full Antler stack reaches $95K–$130K via standing residency code (absorbed by Portfolio) + partner-filed Portfolio + Build for Startups + Bedrock POC. The ceiling is lower than YC or Techstars because Antler is not in the Portfolio Sub-Program directly, but the path is real and well-trodden once you know the mechanics.
Independent of the residency code. Public form at aws.amazon.com/startups/credits/. Anyone can apply; approval in 24 to 72 hours; credits in account in three to seven days. Award is $5K for most applications. Worth filing in parallel with the partner-filed track because it is fast, the founder time is five minutes, and it does not conflict with subsequent applications.
For Antler founders pre-incorporation, the self-serve Founders application can still be filed against your residency email and a forthcoming-incorporation indication. Some reviewers approve; others wait for incorporation. If your application is held pending incorporation, file again the week the entity is registered.
This is the workhorse track for Antler portfolio companies. An AWS partner with prior Antler-application experience files an ACE record naming Antler as the institutional sponsor and your company as the customer. The partner attestation, combined with Antler's growing recognition with AWS Activate reviewers, supports Portfolio approval at $50K–$75K.
The ceiling is below the $75K–$100K range that YC and Techstars companies receive because Antler is not in the Portfolio Sub-Program directly — the institutional signal is real but requires partner intermediation, which AWS reviewers weight slightly lower than the standing-arrangement signal. The $50K–$75K range is wide because the precise award depends on Antler check size ($100K vs $250K), regional residency dynamics, projected consumption, and the partner's prior track record on Antler submissions.
AWS reviewers calibrate Portfolio award size to projected AWS consumption plus institutional check size. Antler's $100K–$250K pre-seed checks are smaller than YC's standard MFN SAFE ($500K) — this is one of the reasons Antler Portfolio awards land below YC. The projected consumption side of the equation matters too: a B2B SaaS Antler company projecting $3K/month of AWS spend over twelve months supports a $50K Portfolio award; a data-heavy or video-heavy company supports the upper end ($75K).
Filed by partners CloudRoute routes specifically because of prior Antler track record. The first-time partner submitting an Antler application takes longer because the reviewer does not have the pattern recognition; the partners with prior Antler submissions land approvals more consistently and faster.
Layers on top of Portfolio when there is a distinct, separable workload. Antler portfolio companies often have a clearly-scoped workload that justifies a separate Build for Startups application — a vertical compliance push (PDPA in Singapore, GDPR in Berlin, data localization in India), a specific feature build, a migration off whatever residency-stage infrastructure was used (typically Vercel, Render, or a managed Postgres).
Filed by the same partner alongside the Portfolio submission. Submitted as a separate ACE opportunity record describing the discrete workload. Approval lands 14 to 21 days from filing. Antler signal does not push Build awards above the standard $25K ceiling — Build is more workload-driven than signal-driven — but the ceiling itself is consistently attainable for Antler companies with well-scoped workload narratives.
AI-eligible Antler portfolio companies layer Bedrock POC on top. Eligibility: a running or planned workload on Amazon Bedrock (Claude, Llama, Mistral, Titan, Nova). The POC plan needs to be specific — use case, model choice, evaluation methodology, projected inference budget over a defined window.
For non-AI-native Antler companies experimenting with AI features (typical: a B2B SaaS adding an AI assistant feature, an analytics tool adding natural-language query), Bedrock POC typically lands $15K–$25K. The lower end reflects the smaller projected inference budget at Antler pre-seed stage; the upper end is reachable with a tightly-scoped POC narrative.
For AI-native Antler companies (the core product is built on Bedrock or comparable inference), $50K is achievable when the POC scope justifies it. The AI-native Antler companies tend to come out of Antler Berlin, Antler Singapore, and Antler India — the residencies with the densest AI focus in current cohorts.
Bedrock POC credits are earmarked: they fund only Bedrock inference and the directly supporting infrastructure (OpenSearch for vector search, S3 for prompt logs, Lambda for orchestration, Bedrock guardrails). They do not cover general EC2 or RDS.
Antler companies in the first few weeks of residency (pre-incorporation, pre-co-founder-matching) cannot file partner-filed Portfolio because there is no incorporated customer record yet. During this window the available path is self-serve Founders only — $5K against the founder's personal AWS account, used for prototyping. The partner-filed Portfolio path opens once the entity is incorporated, typically in residency weeks eight to twelve.
Antler's pre-team-formation model creates a credit-path timing pattern that does not exist for YC, Techstars, or 500 Global. Founders who do not understand the timing miss six to eight weeks of credit windowing.
At Antler residency week one, the founder population is unsorted. A typical residency starts with 50 to 100 individual founders, none of whom have an incorporated company yet at the residency. Co-founder matching, idea exploration, and team formation happen across residency weeks one through eight. By residency week six or seven, most founders have converged toward a co-founder and an idea; by weeks eight to twelve, the resulting teams have incorporated entities (usually a Singapore Pte Ltd, a Delaware C-corp, a UK Ltd, a German GmbH, or the local equivalent, depending on residency location and target market).
AWS Activate applications — both self-serve Founders and partner-filed Portfolio — require a registered business entity. The application form asks for company name, registration number, registered address, and tax ID. Until the entity is incorporated, none of these fields can be completed honestly. Partner-filed Portfolio through ACE requires an even more substantive customer record: registered entity, AWS account ID owned by the entity, use case description, named technical contact at the entity.
The implication for Antler founders: the first six to eight weeks of residency typically cannot access the partner-filed Portfolio path because there is no entity. The standing residency credit code can be redeemed against a personal AWS account or a placeholder account if necessary, but the higher-ceiling partner-filed path is gated on incorporation. The credit timeline effectively starts mid-residency.
The right operational pattern: monitor your incorporation timeline closely. The week incorporation is completed (entity registered, bank account opened, tax ID issued), submit a CloudRoute inquiry. Partner-filed Portfolio can be filed within five to seven days of incorporation. Approval lands 18 to 25 days later. If incorporation happens in residency week ten, credits are in your account by residency week thirteen or fourteen — late residency or just-post-residency, which is exactly when your need for production-class AWS infrastructure is starting.
Common mistake: deferring credit applications until "after Antler investment committee" or "after the round closes" or "after we incorporate properly in Delaware." All of these defer the application by months. Incorporation in any reasonable jurisdiction is sufficient to start the partner-filed Portfolio path; you can re-domicile later if your final structure differs. Waiting for the perfect structure costs credit windowing.
A common Antler founder question: "I have a co-founder and an idea, but we haven't incorporated yet. Can we start the credit path?" The honest answer: self-serve Founders against your personal AWS account, yes. Partner-filed Portfolio, no — the partner needs a registered entity for the ACE record. Plan incorporation for residency week eight to ten, and have the credit conversation ready to start the same week.
Antler operates residencies in more than 30 cities. Each residency is structurally identical from the AWS Activate perspective — partner-filed Portfolio is the path — but the regional AWS partner ecosystem, regional follow-on VC landscape, and regional AWS region selection differ. The location of your residency shapes which partner you should be routed to.
Antler Singapore is the APAC hub and the largest residency by graduate count. Singapore-based Antler portfolio companies typically route to ap-southeast-1 (Singapore) for production workloads, occasionally with multi-region setup into ap-southeast-3 (Jakarta) or ap-northeast-1 (Tokyo) depending on customer base. Singapore Antler portfolio companies often raise follow-on rounds from Peak XV (Sequoia's Southeast Asia successor), East Ventures, Vertex Ventures, and Wavemaker Partners — the seed-stage scene is dense and competitive. CloudRoute routes Singapore Antler alumni to APAC AWS partners with PDPA compliance experience and prior Antler-application track records.
Antler Berlin anchors the DACH and broader European footprint. Berlin Antler portfolio companies route to eu-central-1 (Frankfurt) for general workloads and eu-west-1 (Ireland) where Ireland-specific data residency is preferred. Follow-on VCs include Speedinvest, HV Capital, Project A, Cherry Ventures — the European seed-stage scene has different rhythm than US scenes (smaller checks, longer diligence). Berlin Antler partners CloudRoute routes are GDPR-experienced and familiar with the seed-stage German VC paperwork rhythm.
Antler Nairobi is the central African residency. Nairobi-based Antler portfolio companies route to af-south-1 (Cape Town) — the only AWS region on the African continent — with multi-region fallback into eu-west-1 for global services not yet available in Cape Town. Follow-on VCs include Future Africa, Partech Africa, Novastar Ventures, and the broader pan-African seed-stage scene. The AWS partner ecosystem in af-south-1 is small but growing; CloudRoute routes Nairobi Antler companies to the specific partners with active af-south-1 deployment experience.
Antler India anchors the Bangalore-led Indian footprint. Bangalore Antler portfolio companies route to ap-south-1 (Mumbai) and increasingly ap-south-2 (Hyderabad) for data localization purposes. Follow-on VCs include the broader Indian VC ecosystem — Peak XV India, Lightspeed India, Nexus Venture Partners, Blume Ventures — plus the increasingly active NASSCOM 10,000 Startups community and corporate VCs from Tata, Reliance, and others. Partners matched to India Antler companies handle the DPDP Act compliance posture and the specific tax structures relevant to Indian incorporations.
Antler LATAM operates São Paulo and Mexico City residencies. São Paulo Antler companies route to sa-east-1 (São Paulo) with us-east-1 fallback. Mexico City Antler companies often route to us-east-1 directly given the proximity and lower-latency commercial logic. Follow-on VCs include KASZEK Ventures, ALLVP, Magma Partners, and the broader LATAM VC scene. Partners matched here are familiar with the LATAM commercial dynamics — billing in USD, USD-denominated AWS spend planning, and the specific compliance requirements (LGPD in Brazil, Mexican fintech regulation if relevant).
Antler MENA operates Riyadh and Dubai residencies. Antler MENA portfolio companies route to me-central-1 (UAE) and me-south-1 (Bahrain) depending on the use case. Follow-on collaboration with regional accelerators (MISK Innovation, Hub71, Flat6Labs) and regional VCs (Raed Ventures, MEVP, Wamda Capital) is common. CloudRoute routes MENA Antler alumni to MENA AWS partners with prior accelerator track records and familiarity with regional payment and compliance posture.
The smaller-graduate residencies (Sydney, Stockholm, Oslo, Toronto, London, Amsterdam, Tokyo, Seoul) follow the same partner-filed Portfolio mechanic as the larger residencies. The credit ceiling and timeline are identical; partner matching differs based on regional ecosystem familiarity. CloudRoute maintains the regional partner list for all Antler residencies and routes accordingly.
Antler Stockholm routes to eu-north-1 (Stockholm) for Nordic data residency preferences. Antler Sydney routes to ap-southeast-2. Antler Toronto routes to ca-central-1 with us-east-1 fallback for cross-border SaaS. Antler London routes to eu-west-2 (London).
Antler's pre-seed check ($100K–$250K) is materially smaller than YC's standard MFN SAFE ($500K). AWS reviewers calibrate Portfolio award size partly on projected consumption and partly on institutional check size; Antler's smaller check is one of the structural reasons Antler Portfolio awards land in the $50K–$75K range rather than YC's $100K range.
The reviewer logic: a $250K-funded company is expected to consume AWS at a different rate than a $500K-funded company. The smaller check correlates with a tighter twelve-month runway, which correlates with smaller projected AWS spend, which calibrates the Portfolio award downward. This is portfolio math, not a judgment on the company quality — it is the same logic AWS applies across all Activate sub-programs.
The implication: Antler-backed companies that raise notable seed rounds shortly after residency see their Portfolio award size approve at the upper end of the range. A seed round closing at $1M to $3M from a tier-one regional VC re-calibrates the projected consumption upward, supporting the $75K end of the Portfolio range rather than the $50K floor.
Antler portfolio companies often raise seed rounds six to twelve months post-residency. The typical pattern: residency ends, the Antler $100K–$250K check funds operations through demo events and early customer development, the company raises a seed round from a regional tier-one VC (Peak XV, Speedinvest, KASZEK, Partech Africa, etc.) in the six-to-twelve-month window after residency, then continues to scale.
The timing of the Portfolio application matters in relation to the seed round. The cleanest pattern: file partner-filed Portfolio just after incorporation (mid-residency or just-post-residency, when the entity is registered and the Antler investment is on the cap table). Approval lands $50K–$75K based on Antler signal + projected consumption. If the seed round closes within the credit application window or shortly after, the credit balance is already in the account when investor diligence begins — the cloud-cost projection in the data room references the credit balance directly.
Alternative pattern: defer the Portfolio application until the seed round closes, file partner-filed Portfolio with the seed round as additional institutional signal, target the upper end of the range. This adds two to three months of delay but may push the award $10K to $20K higher. CloudRoute generally recommends the first pattern (file early) because the credit windowing matters more than the marginal $10K–$20K ceiling lift, but the second pattern is reasonable for founders who prefer to apply once with maximum signal.
Antler, YC, and Techstars are the three most common comparisons in global accelerator AWS credit conversations. The structural differences are real.
The standing credit gap: YC issues an automatic $5K Activate Founders credit at AWS account creation for YC-batch members. Techstars distributes a ~$1K Builders code at batch kickoff. Antler distributes a $1K–$5K Activate Founders code at residency kickoff. The standing credit is broadly comparable in the small ($1K) to medium ($5K) range; YC has the structural advantage of automatic issuance, while Antler and Techstars require manual redemption.
The Portfolio Sub-Program membership: YC and Techstars are members; Antler is not. This is the central structural difference. For YC and Techstars, partner-filed Portfolio approvals land at $75K–$100K against the institutional standing arrangement. For Antler, partner-filed Portfolio approvals land at $50K–$75K against the partner intermediation. The gap is roughly $25K in expected value per application.
The geographical spread: Antler operates 30+ residencies globally, Techstars operates 50+ programs globally, and YC operates centrally in San Francisco with a fully-remote batch model. Antler and Techstars are comparably distributed; YC is concentrated. The partner matching for Antler and Techstars therefore relies more heavily on regional partner ecosystems; the partner matching for YC is more US-centric by default.
The pre-team-formation model: this is unique to Antler. YC accepts teams; Techstars accepts teams; Antler accepts individual founders pre-team-formation. The unique implication for AWS credits is the incorporation timing — Antler portfolio companies cannot access the partner-filed Portfolio path until incorporation, which is typically residency weeks eight to twelve. YC and Techstars companies are incorporated at batch kickoff.
The check size: YC writes $500K MFN SAFE checks. Techstars writes ~$120K convertible note + equity checks. Antler writes $100K–$250K pre-seed checks. The check size affects Portfolio award calibration: larger check, larger projected consumption, higher Portfolio award.
Net realistic stack: YC non-AI companies land $125K–$150K; Techstars non-AI companies land $125K–$150K; Antler non-AI companies land $95K–$130K. For AI-native companies, YC and Techstars can reach $400K+ via Generative AI Accelerator; Antler AI-native companies have access to the same Accelerator path but with somewhat lower acceptance rates because the Antler signal is less recognized by Accelerator reviewers (the Accelerator favors brand-strong accelerator backing).
| Variable | Y Combinator | Techstars | Antler |
|---|---|---|---|
| Standing Activate credit | $5K (automatic) | ~$1K (code redemption) | $1K–$5K (code redemption, location-dependent) |
| Portfolio Sub-Program member? | Yes (long-standing) | Yes | No (partner-intermediated) |
| Portfolio approval ceiling (partner-filed) | $75K–$100K | $75K–$100K | $50K–$75K |
| Approval probability (Portfolio) | ~85% | ~75–80% | ~70–75% |
| Typical Build for Startups | $25K ceiling | $15K–$25K | $25K ceiling |
| Bedrock POC (non-AI) | $25K typical | $25K typical | $15K–$25K typical |
| Bedrock POC (AI-native) | $50K achievable | $50K achievable | $50K achievable for strong applications |
| Model | Teams accepted, pre-incorporated | Teams accepted, pre-prototype | Solo founders accepted, pre-team-formation |
| Check size | $500K MFN SAFE | ~$120K note + equity | $100K–$250K pre-seed equity |
| Geographic concentration | San Francisco (remote batches) | 50+ global programs | 30+ global residencies |
| Realistic non-AI stack | $125K–$150K | $125K–$150K | $95K–$130K |
Residency week one or two — Standing residency credit code distributed via Antler Slack or platform portal. Redeem against a personal or placeholder AWS account; credits land in 24 to 48 hours. Use for residency-stage prototyping.
Residency weeks one through eight — Co-founder matching, idea exploration, no partner-filed path available because there is no incorporated entity yet. Self-serve Founders ($5K) can be filed against the founder's personal account if useful.
Residency weeks eight to twelve — Incorporation completes (Singapore Pte Ltd, Delaware C-corp, UK Ltd, German GmbH, or local equivalent). Entity registration confirmed, AWS account migrated or recreated under the entity name. This is the trigger week for the partner-filed Portfolio path.
Day 0 (incorporation week) — Submit a CloudRoute inquiry indicating Antler portfolio company status and residency location (Singapore, Berlin, Nairobi, Bangalore, São Paulo, Riyadh, etc.).
Day 1 — Routed within 24 hours to a partner with prior Antler-application experience, matched on region (APAC/EU/Africa/India/LATAM/MENA) and vertical (B2B SaaS/AI/marketplace/fintech).
Day 2 — Discovery call (30 minutes). Partner confirms residency membership, scopes Portfolio + Build for Startups + Bedrock POC applicability. Verifies incorporation status and AWS account setup.
Day 3–5 — You provide company info, AWS account ID, use case paragraphs, deck, and Antler residency confirmation. ~45 minutes total founder time.
Day 6–7 — Partner files three ACE records (Portfolio + Build for Startups + Bedrock POC if AI) within the same business week. Each names Antler as the institutional sponsor and your residency cohort as eligibility evidence.
Day 14–20 — Portfolio approval lands first ($50K–$75K). Build for Startups by Day 18–22 ($15K–$25K). Bedrock POC by Day 20–25 ($15K–$25K, $50K if AI-native).
Day 18–25 — Full stack visible in AWS Billing dashboard under "promotional credits." $95K–$130K total auto-applies against monthly invoice.
Optional Day 60+ (AI-native Antler only) — Apply to Generative AI Accelerator. Selection in 60–90 days; additional $200K–$500K for accepted AI applications.
The partner's role for an Antler portfolio company is structurally similar to other partner-filed engagements, with three Antler-specific patterns worth flagging.
They file the ACE records — Portfolio, Build for Startups, Bedrock POC if applicable — naming Antler as the institutional sponsor and your residency cohort as the eligibility evidence. Because Antler is not in the standing Portfolio Sub-Program, the partner narrative work matters more than it does for YC or Techstars submissions: the partner explicitly establishes the institutional credibility in the ACE description rather than relying on automated verification.
They vet the use case and Antler context before filing. Antler companies are typically very early-stage at incorporation week one; the partner sanity-checks whether the use case as described matches what the ACE reviewer is going to want to see. This is more important for Antler than for later-stage applications because Antler companies tend to have less polished commercial narratives at filing time.
They act as the named technical partner on the file. The reviewer cross-references partner history; partners with prior Antler approvals are recognized and the file moves faster.
They provide the actual AWS implementation if you want it — production account setup, IAM and VPC, the migration off whatever residency-stage infrastructure you used (Vercel, Render, a managed Postgres, sometimes Supabase or PlanetScale), observability, and deployment pipelines. Most Antler portfolio companies want this because the post-residency window is fundraising-intense and cloud-engineering bandwidth is limited.
They provide a co-branded readiness assessment — a written document showing the partner-built infrastructure, the trade-offs, what to monitor. This deliverable is useful for incoming investors during seed-round diligence.
Pattern 1 — The residency-end demo migration. Some Antler partners run a short pre-residency-end implementation sprint, moving the company's working prototype from residency-stage infrastructure to production-class AWS infrastructure with autoscaling and a real domain. The credits cover the cloud cost; the founder time is minimal. Useful for companies whose investor demos at the end of residency benefit from looking production-ready.
Pattern 2 — The seed-round-prep cloud-posture write-up. Other Antler partners focus the engagement on data-room readiness for the post-residency seed round: cost-projection documents, infrastructure-roadmap documents, security posture summaries, compliance-readiness narratives (PDPA for Singapore companies, GDPR for Berlin companies, DPDP for India companies). The credits cover the cloud cost during the diligence window; the partner output makes the cloud story tight for due diligence.
Pattern 3 — The Antler-investment-committee compliance prep. Some residencies have specific compliance hurdles before Antler invests (sometimes a data-handling review, sometimes a security posture check for B2B applications). Some Antler partners help with this directly — the work happens during residency, the credits cover the implementation cost, and the readiness output supports the investment committee narrative.
What stopping at the residency code vs pursuing the full path actually costs.
| Variable | Standing residency code only | Full Antler stack |
|---|---|---|
| Total credits | $1K–$5K | $95K–$130K |
| Application time | ~5 min (paste code) | ~30 min (partner-filed) + 10 min (Build) + 30 min (Bedrock POC) |
| Wall-clock to balance | 24–48 hours | 18–25 days from inquiry |
| Runway covered | 4–12 months at residency-stage burn | 14–22 months at post-residency burn |
| Bedrock workload supported | Limited (general pool) | Dedicated Bedrock POC pool |
| Generative AI Accelerator eligibility | Yes (separate path) | Yes; can pursue in parallel |
| Cost to founder | $0 | $0 |
| Reviewer scrutiny | Code redemption only | Higher (no standing arrangement; partner provides verification) |
Situation: Antler Singapore SEA-batch graduate. Three-person founding team formed during residency. Post-residency $1M seed round from East Ventures closing concurrent to the engagement. B2B SaaS product targeting Indonesian SMEs (workforce management); needed ap-southeast-1 production setup with multi-region capability into ap-southeast-3 (Jakarta) for PDPA-equivalent Indonesian data handling. Residency-stage infrastructure was running on Vercel + Supabase; needed real cloud architecture before the seed round closed and before scaling customer onboarding.
What CloudRoute did: Routed within 18 hours to an APAC partner with prior Antler Singapore Portfolio approvals and ap-southeast-1 + ap-southeast-3 deployment track record. Partner filed Portfolio ($75K, upper end of Antler range given the East Ventures seed signal landing concurrent), Build for Startups ($25K for the Indonesian compliance and customer-onboarding workload as a distinct project), Bedrock POC ($25K for a Bahasa Indonesia customer support agent feature on the post-launch roadmap). All three filed within the same business week, two weeks after incorporation as a Singapore Pte Ltd.
Outcome: Stacked credits applied within 19 days: $125K total. Production AWS account live in 11 days, ap-southeast-1 primary with ap-southeast-3 replica. Indonesian SME onboarding launched 4 weeks post-incorporation. East Ventures seed round closed 3 weeks after credit approval; data room included confirmed $125K AWS credit balance, partner readiness assessment, and PDPA-equivalent compliance documentation. Total founder time across credit application + partner setup: ~11 hours.
engagement window: 4 weeks · founder time: ~11 hours · credits secured: $125K · cost: $0
CloudRoute routes Antler portfolio companies to AWS partners with prior Antler-application track records, matched on residency location (Singapore, Berlin, Nairobi, Bangalore, São Paulo, Riyadh, and others) and vertical (B2B SaaS, AI, marketplace, fintech). Customer pays $0; AWS funds the engagement.