AWS credits for On Deck fellows — the post-fellowship partner-filed Portfolio path most ODF graduates never use.

IOn Deck — the community-first fellowship that became an accelerator

On Deck is unusual among institutional accelerators in three ways: it started as a community rather than an investor; it grew through fellowships rather than cohorts; and it restructured aggressively in 2023 toward a tighter set of focused programs. Understanding the trajectory shapes how AWS Activate reviewers read the On Deck signal in 2026.

On Deck was founded in 2019 by Erik Torenberg, David Booth, Brett Goldstein, and a small early team. The original product was On Deck Founders (often abbreviated ODF), a paid fellowship that accepted founders considering starting a company. ODF ran in roughly nine-week cycles with multiple cohorts per year. The cohort size in the early years was a few hundred fellows; by the 2021 peak the program was accepting cohorts of 600 to 800 fellows at a time, with applications running into the thousands per cycle.

The fellowship structure is different from a YC- or Techstars-style accelerator. On Deck did not write investment checks into every fellow; it accepted founders pre-company-formation and provided a community, programming, and access to investors, operators, and other founders. The On Deck Founders Fund — On Deck's investment vehicle — wrote pre-seed checks into a selected subset of ODF participants who incorporated and moved into seed-stage. The community membership and the investment commitment were two distinct things; not every ODF fellow received On Deck Founders Fund investment.

Between 2019 and 2022 On Deck expanded into multiple parallel fellowships across verticals and roles: On Deck ODX (a more cohort-driven, accelerator-adjacent program for selected ODF founders), On Deck Engineers, On Deck AI, On Deck Climate, On Deck No Code, On Deck PMs, On Deck Product Managers, On Deck Designers, On Deck Writers, On Deck Chief of Staff, On Deck Longevity, and others. The constellation peaked at over 20 simultaneous fellowships across various stages of activity. Each fellowship had its own programming, its own community, and its own subset of On Deck-affiliated investors.

In 2023 On Deck restructured. The original community-driven model proved difficult to scale economically, and the leadership team made a strategic pivot toward a smaller set of more focused programs. The flagship post-restructure offering is On Deck Catalyst — an accelerator-style program with selective cohorts of founders, structured more like a traditional accelerator (closer to Techstars in shape) than the early fellowships. Several of the original fellowships were wound down or significantly restructured during this period; the On Deck Founders Fund continued operating as the institutional investment vehicle.

The 2023 restructure is the central operational fact for AWS credit reviewers in 2026. The On Deck name carries institutional recognition because of the 2019–2022 community growth and the steady cadence of post-fellowship seed rounds raised by ODF and ODX alumni. But the specific signal an AWS reviewer reads depends on which fellowship the applicant participated in and when. A 2021 ODF graduate who later raised a seed round from On Deck Founders Fund + a tier-one VC reads differently than a 2024 On Deck Catalyst graduate, who again reads differently than a 2022 On Deck AI participant. The Portfolio path mechanics are the same; the institutional context the reviewer interprets is layered.

IIWhy On Deck is NOT in the AWS Activate Portfolio Sub-Program directly

AWS Activate maintains the Portfolio Sub-Program with a published list of institutional partners. YC, Techstars, and 500 Global are inside that list with multi-year standing arrangements. On Deck is not. The structural reasons matter for how the credit path actually runs.

The Portfolio Sub-Program operates as a standing arrangement between AWS Activate and the participating accelerator. The accelerator commits a defined volume of incorporated portfolio companies routed through Activate each year; AWS commits standing approval thresholds for those companies; the two organizations integrate at the operational level with shared batch lists, automated eligibility verification, and dedicated reviewer flow. YC, Techstars, and 500 Global all operate at this level. The arrangement requires both a stable definition of "portfolio company" and a steady annual volume of those companies for AWS reviewer planning purposes.

On Deck has historically not had this standing arrangement. The reason is structural: On Deck's 2019–2022 fellowship model meant the population of "On Deck portfolio companies" was an ambiguous category. A 2021 ODF cohort included 700 fellows; only a subset incorporated; only a subset of those received On Deck Founders Fund investment; only a subset of those reached the seed stage where AWS credit conversations are most useful. AWS Activate's eligibility model expects a defined portfolio with a clear membership criterion. The fellowship model meant the criterion was fuzzy, the volume was unpredictable, and the standing-arrangement integration was hard to operate at scale.

The 2023 restructure narrowed the surface area. On Deck Catalyst as a more traditional accelerator format produces a clearer portfolio definition (the companies selected for Catalyst cohorts are bounded and identifiable). On Deck Founders Fund as the investment vehicle produces a clearer signal (the companies receiving On Deck Founders Fund investment are bounded and identifiable). But neither of these has, as of mid-2026, translated into On Deck joining the Portfolio Sub-Program directly. The standing arrangement has not been formalised.

What On Deck has instead is what most non-Portfolio-Sub-Program accelerators have: working relationships with AWS partners who file portfolio applications on behalf of selected fellows, particularly fellows who have raised post-fellowship institutional seed rounds. The institutional signal is real — On Deck's name on an ACE submission carries weight, especially when paired with On Deck Founders Fund participation and a tier-one co-investor — but the path runs through partners rather than through a standing arrangement.

The practical implication: On Deck fellows who only redeem the standing fellowship credit code (the $1K–$5K Activate Founders code distributed to certain programs) are stopping at the floor. The partner-filed Portfolio path adds another $50K–$75K when timed against post-fellowship seed-round closure. The path requires an incorporated entity, an active use case, and (for the upper end of the range) post-fellowship institutional VC participation on the cap table.

IIIThe standing AWS Activate code — what fellowships actually distribute

Certain On Deck fellowships distribute a standing AWS Activate credit code to participants. The amount ranges from $1K to $5K depending on the program and the cohort year. The code is real, the redemption process is straightforward, and the runway is meaningful for fellowship-window prototyping — but it is not the auto-issuance that YC has.

The standing code is most consistently distributed in On Deck Founders and On Deck AI; other fellowships have distributed codes in some cohorts and not others, depending on which programs ran the parallel AWS perks bundle. The code is distributed via the fellowship Slack workspace, the cohort portal, or in-person at one of the fellowship-week onboarding sessions. The fellowship operations team at each cohort is responsible for distribution; in some cohorts this is handled by a dedicated platform or community manager, in others by the program lead directly. If you joined a fellowship and have not received a code within the first three weeks, the right contact is your cohort program lead or the platform team running the community operations.

The amount varies by cohort and program. On Deck Founders cohorts have historically received codes at the $5K Activate Founders ceiling. On Deck AI cohorts often receive $5K Activate Founders codes plus a separate Bedrock-specific consideration. Some smaller fellowships have distributed codes at the $1K Builders tier rather than the $5K Founders tier. The variation reflects which AWS perks bundle the fellowship operations team negotiated at the time the cohort was set up; the variation is not a judgment on the cohort quality.

To redeem: you need an AWS account. Many On Deck fellows do not have an AWS account at fellowship start (many have used GCP or Azure in prior roles, or have used a personal AWS account that should not be reused for the company). Create a fresh AWS account using a professional email — ideally your future-company email if the entity is registered, or a placeholder if it is not. 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 fellowship-phase AWS consumption (typically $50–$300/month, given that most On Deck-stage prototyping uses Vercel, Supabase, Linear, Notion, and similar shared infrastructure), the $5K code lasts 12 to 24 months. The runway covers the fellowship window, the immediate post-fellowship period, and often part of the first post-incorporation production-build phase.

Worth knowing: the standing fellowship code and the partner-filed Portfolio path occupy the same Activate program at different ceilings. When Portfolio is approved, it absorbs the Founders tier rather than stacking on top of it. You end up with $50K–$75K Portfolio total, not $50K–$75K Portfolio plus the original $5K Founders. 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.

IVThe realistic On Deck credit stack in 2026

The full post-fellowship stack reaches $95K–$130K via standing fellowship code (absorbed by Portfolio) + partner-filed Portfolio + Build for Startups + Bedrock POC. The pre-fellowship and during-fellowship stack is much smaller — typically $25K–$45K — because the partner-filed Portfolio path opens cleanly only when there is a post-fellowship institutional seed round to anchor the signal.

VThe pre-fellowship vs post-fellowship distinction

On Deck's credit path runs in two phases with structurally different ceilings. Founders who do not understand the distinction either underclaim during the fellowship (assuming nothing is available) or overclaim post-fellowship (assuming the fellowship alone unlocks Portfolio). The honest answer is in between.

During the fellowship — typically a nine-week ODF cohort or a comparable cohort window for the other fellowships — the available paths are the standing fellowship credit code ($1K–$5K depending on program) and the self-serve Activate Founders ($5K). Both are real and immediately useful for fellowship-phase prototyping. The standing code is bundled with the rest of the fellowship perks (Notion, Linear, Figma, Stripe, OpenAI, and others); the self-serve Founders application takes five minutes and can be filed against a personal or placeholder AWS account.

During the fellowship, the partner-filed Portfolio path is structurally available but not optimal. The partner can file Portfolio with On Deck fellowship participation as the institutional signal, but without a post-fellowship institutional seed round on the cap table the reviewer interprets the signal more conservatively. The application sometimes approves at the lower end of the range ($50K), sometimes downgrades to Founders ($5K), and sometimes is held pending additional institutional context. The expected value of filing during fellowship is therefore lower than the expected value of filing post-fellowship.

Post-fellowship, the picture changes. Once the institutional seed round closes (whether from On Deck Founders Fund, a tier-one VC, or a co-investing syndicate), the partner-filed Portfolio path opens cleanly. The reviewer reads On Deck fellowship participation plus the seed round as a layered institutional signal — On Deck provides the early validation, the seed VC provides the commercial validation, and the partner attestation provides the technical validation. The combination is what supports the $50K–$75K range with above-average approval probability.

The cleanest operational pattern: redeem the fellowship code during the program (24–48 hours, $1K–$5K, fellowship-phase prototyping). File self-serve Founders during or just after the fellowship ($5K, 5 minutes, applied against the personal/placeholder account or the early entity account). Incorporate the company during or just after the fellowship; in most cases this is Delaware C-corp because the seed-stage VC ecosystem expects it. Begin the partner-filed Portfolio conversation as soon as a term sheet is in for the institutional seed round, file in the week the round closes, and approval lands 18 to 25 days later at $50K–$75K. Stack Build for Startups and Bedrock POC in the same filing window.

Common mistake: filing partner-filed Portfolio during the fellowship and assuming the fellowship participation alone provides the institutional signal needed for the upper end of the range. The approval often comes in at $50K rather than $75K, and the application sometimes downgrades entirely. The fix is not to skip the partner-filed path; it is to time it correctly. Wait for the institutional seed round to layer on the signal.

VIOn Deck Founders Fund — institutional signal, not a Portfolio Sub-Program member

On Deck Founders Fund is the investment vehicle through which On Deck writes pre-seed and seed checks into selected fellows. Founders sometimes assume that On Deck Founders Fund participation alone unlocks the Portfolio Sub-Program standing arrangement. It does not — but the participation does materially strengthen the partner-filed Portfolio application.

On Deck Founders Fund operates as a standard early-stage VC fund, with the typical fund mechanics (LP commitments, investment committee, portfolio construction, board observer rights on selected investments). The fund writes pre-seed and seed checks ranging from approximately $100K to $750K depending on the round structure and the company stage. The fund participates in many but not all of the seed rounds raised by On Deck fellowship alumni; many ODF and Catalyst graduates raise seed rounds without On Deck Founders Fund participation.

The institutional signal from On Deck Founders Fund participation is real for AWS credit purposes. AWS reviewers reading a partner-filed Portfolio application with both On Deck fellowship participation and On Deck Founders Fund investment on the cap table interpret this as layered institutional validation. The fellowship name carries community recognition; the Fund name carries investor recognition. The combination supports the upper end of the partner-filed Portfolio range.

But — and this is the central point — On Deck Founders Fund participation alone does not unlock the Portfolio Sub-Program standing arrangement. The Sub-Program requires the standing arrangement at the accelerator level (which On Deck does not currently have); the Fund is a separate entity. A company with On Deck Founders Fund as a lead investor but without any On Deck fellowship participation is treated by AWS reviewers as a seed-stage company with one institutional investor, not as a Portfolio Sub-Program portfolio company.

The practical implication: On Deck fellowship participation plus On Deck Founders Fund investment plus a tier-one co-investor is the cleanest layered signal. CloudRoute routes these applications to partners with prior On Deck submission experience because the partner narrative work matters more than for YC or Techstars submissions — the partner explicitly establishes the institutional credibility in the ACE description rather than relying on the standing arrangement to provide automatic verification.

Worth verifying before submission: the precise On Deck Founders Fund cap table position (lead vs participating, board observer vs not, etc.) should be confirmed in the ACE narrative because AWS reviewers occasionally cross-reference. The reviewer is not adversarial about this — they are not trying to disqualify the application — but the cleaner the narrative, the faster the approval.

VIIOn Deck AI — the fellowship most aligned with the Bedrock POC track

On Deck AI is the fellowship most directly relevant to the Bedrock POC sub-program. Participants are typically building AI-native products at the model-inference layer; the post-fellowship Bedrock POC application is structurally well-aligned with what the reviewer expects.

On Deck AI ran multiple cohorts between 2021 and the 2023 restructure, focused on founders building AI-native companies. The cohort composition skewed toward founders with technical depth in machine learning, applied AI, or LLM-based product engineering. Post-restructure, the AI focus has been folded into On Deck Catalyst cohorts that admit AI-native companies, plus selected smaller AI-themed offerings.

For Bedrock POC applications, On Deck AI participation reads cleanly to AWS reviewers. The fellowship signal indicates that the company is part of an AI-focused cohort; the partner narrative scopes the POC against a Bedrock-based use case; the reviewer interprets the layered signal as supportive of the $25K typical approval. For strong applications — a tightly-scoped POC narrative against a clear inference budget, a measurable evaluation methodology, and a defined post-POC roadmap — $50K is achievable.

Some On Deck AI participants apply to the AWS Generative AI Accelerator separately. The Accelerator is administered by a different AWS team with its own selection criteria, and acceptance for On Deck AI alumni runs somewhat below YC and Techstars equivalent acceptance rates — primarily because the Accelerator reviewer pool favors brand-strong accelerator backing, and the On Deck name has less reviewer-side pattern recognition than YC or Techstars. CloudRoute observed approximately 8–10% acceptance for On Deck AI alumni applying to the Accelerator, vs the YC ~15–20% and Techstars ~12–15% rates.

Accepted On Deck AI Accelerator applications land median $200K–$400K awards. Combined with the partner-filed Portfolio + Build + Bedrock POC stack, the upper-bound stack for an accepted On Deck AI Accelerator company reaches $300K to $500K+. The Accelerator path runs in parallel with the partner-filed stack — different administrative track, different scrutiny criteria — and CloudRoute partners advise on Accelerator application scoping while the partner-filed submission is already in review.

For non-AI On Deck fellowships (ODF, Catalyst non-AI tracks, the older role-based fellowships), Bedrock POC is still accessible but the typical approval lands at $15K–$25K rather than $25K–$50K. The reviewer reads the fellowship as generalist rather than AI-specific, and calibrates accordingly. Most non-AI On Deck companies still file Bedrock POC because the application takes 30 minutes of additional founder time and the approval is reliable; the marginal $15K–$25K is high-leverage credit for a B2B SaaS adding AI features.

VIIIThe 2023 restructure — how it changed the signal AWS reviewers read

The On Deck 2023 restructure changed the fellowship landscape materially. Some pre-restructure signals carry less weight now than they did at the time; some have been replaced by the post-restructure On Deck Catalyst signal. AWS reviewers in 2026 read the layered context — which fellowship, which cohort year, what came after.

Pre-restructure (2019–2022), On Deck operated a constellation of fellowships across verticals and roles. The community was large, the cohorts were big, and the signal at the time was "this person is part of an active, well-recognized founder community." AWS reviewers reading a partner-filed Portfolio application from a 2021 ODF alumna with a post-fellowship seed round interpreted the On Deck participation as a meaningful early-stage signal. The Portfolio approval typically landed at $50K–$65K, with stronger applications reaching $75K.

In 2026, that same 2021 ODF participation is read differently. The restructure means that the specific fellowship the applicant participated in may no longer be operating in its original form. The reviewer reads "2021 ODF participation" as a historical signal rather than an active institutional signal — meaningful, but weighted less than current institutional participation. For a 2021 ODF alumna who raised a seed round in 2023 and is now applying for partner-filed Portfolio in 2026, the application still goes through, but the partner narrative needs to lean more on the post-fellowship trajectory (the seed VCs, the commercial traction, the AWS consumption projection) than on the fellowship name alone.

Post-restructure (2023–present), the signal is sharper. On Deck Catalyst cohorts produce a clearer portfolio definition; the post-restructure Catalyst alumna applying for partner-filed Portfolio reads to the AWS reviewer as a current institutional signal. The Portfolio approval calibrates similarly to the pre-restructure $50K–$75K range, but with somewhat higher approval probability because the institutional context is more recognizable in the current period.

On Deck AI specifically — the pre-restructure AI fellowship cohorts — sit in an interesting position. The fellowship is no longer running in its original form, but the alumni network and the On Deck AI naming carry recognition for Bedrock POC submissions. Reviewers familiar with the AI-focused 2022–2023 cohorts read the participation as a relevant AI-native signal. Newer AI-native founders coming out of On Deck Catalyst with an AI focus get the same signal interpretation under a different fellowship name.

The pre-restructure smaller fellowships (On Deck Engineers, On Deck PMs, On Deck No Code, On Deck Climate, On Deck Writers, On Deck Designers, and others) are now less directly relevant to credit applications. A 2022 On Deck Engineers participant who founded a company two years later and is now applying for credits typically does not lean on the Engineers fellowship participation in the partner-filed application — the relevance gap is too wide. The partner narrative leans instead on the company's post-Engineers trajectory and the post-fellowship institutional signal from the seed round.

Worth knowing: the partner narrative is where the 2023 restructure context gets handled. CloudRoute routes On Deck applications to partners who understand the restructure timeline and can write the ACE description with the appropriate weighting — heavier emphasis on current institutional context, lighter emphasis on historical fellowship participation when the fellowship is no longer in its original form, and explicit treatment of the On Deck Catalyst signal where applicable.

IXOn Deck vs YC, Techstars, 500 Global, and Antler — credit stacking compared

On Deck, YC, Techstars, 500 Global, and Antler are the most common comparisons in global accelerator AWS credit conversations. The structural differences are real and matter for what credits are realistically available.

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. 500 Global distributes Activate codes at varying tiers depending on cohort. Antler distributes $1K–$5K Activate Founders codes at residency kickoff. On Deck distributes $1K–$5K Activate Founders codes to certain fellowships (ODF and ODF-adjacent programs at $5K, smaller fellowships sometimes at $1K). The standing credit is broadly comparable in the small ($1K) to medium ($5K) range across all five accelerators; YC has the structural advantage of automatic issuance, while Techstars, 500 Global, Antler, and On Deck all require manual code redemption.

The Portfolio Sub-Program membership: YC, Techstars, and 500 Global are members; Antler and On Deck are not. This is the central structural difference. For YC, Techstars, and 500 Global, partner-filed Portfolio approvals land at $75K–$100K against the institutional standing arrangement. For Antler and On Deck, partner-filed Portfolio approvals land at $50K–$75K against partner intermediation. The gap is roughly $25K in expected value per application.

The check size and institutional context: YC writes $500K MFN SAFE checks. Techstars writes ~$120K convertible note + equity checks. 500 Global writes $150K–$200K equity checks. Antler writes $100K–$250K pre-seed checks. On Deck Founders Fund writes $100K–$750K checks (variable; not every fellow receives the Fund's investment). The check size and the participation pattern affect Portfolio award calibration, but the structural Portfolio Sub-Program membership matters more than the check size in determining the realistic approval ceiling.

The model: YC accepts teams pre-incorporated, runs concentrated batches in San Francisco. Techstars accepts teams with at least a working prototype, runs 50+ programs globally. 500 Global accepts companies with some traction, runs multiple programs globally. Antler accepts solo founders pre-team-formation, runs 30+ residencies globally. On Deck accepts founders pre-incorporation in a community-first fellowship format (pre-restructure) or in a more traditional Catalyst format (post-restructure). Each model has its own credit-application timing pattern. The On Deck pattern is anchored by the pre-fellowship vs post-fellowship distinction; the Antler pattern by the pre-team-formation incorporation gotcha; the YC pattern by the standing arrangement that makes most paths automatic.

Net realistic stack: YC non-AI companies land $125K–$150K. Techstars non-AI companies land $125K–$150K. 500 Global non-AI companies land $115K–$140K. Antler non-AI companies land $95K–$130K. On Deck non-AI post-fellowship companies land $95K–$130K. The Antler and On Deck stacks are functionally comparable because both face the same Portfolio Sub-Program membership gap.

For AI-native companies: YC and Techstars AI applicants can reach $400K+ via Generative AI Accelerator with 15–20% acceptance. Antler and On Deck AI applicants have access to the same Accelerator path with 8–12% acceptance. The Accelerator favors brand-strong accelerator backing, and the Portfolio-Sub-Program-member accelerators read more strongly to Accelerator reviewers than the non-member accelerators do.

XThe 25-day On Deck stack timeline

Fellowship week one or two — Standing fellowship credit code distributed via On Deck Slack or program portal (for fellowships that participate in the AWS perks bundle, primarily ODF and On Deck AI historically). Redeem against a personal or placeholder AWS account; credits land in 24 to 48 hours. Use for fellowship-stage prototyping.

Fellowship duration (typically nine weeks) — Self-serve Activate Founders ($5K) filed in parallel against the personal or early-entity AWS account. Bedrock POC may be filed in parallel for On Deck AI participants if a clearly-scoped POC narrative exists at fellowship time.

Post-fellowship (incorporation phase) — Delaware C-corp incorporation. AWS account migrated or recreated under the entity name. Initial customer development, demo events, term sheet conversations begin.

Day 0 (term sheet signed for institutional seed round) — Submit a CloudRoute inquiry indicating On Deck portfolio company status (which fellowship, which cohort year, post-fellowship VC names, current cap table).

Day 1 — Routed within 24 hours to a partner with prior On Deck-application experience, matched on vertical (B2B SaaS, AI, marketplace, fintech) and post-fellowship VC familiarity.

Day 2 — Discovery call (30 minutes). Partner confirms fellowship membership, scopes Portfolio + Build for Startups + Bedrock POC applicability. Verifies incorporation status, AWS account setup, and term sheet timing.

Day 3–5 — You provide company info, AWS account ID, use case paragraphs, deck, On Deck fellowship confirmation, term sheet or recent funding documentation. ~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 On Deck as the fellowship sponsor, the institutional seed VC as the commercial validation, and your company as the customer.

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, $25K–$50K if AI-native or On Deck AI participant).

Day 18–25 — Full stack visible in AWS Billing dashboard under "promotional credits." $95K–$130K total auto-applies against monthly invoice.

Optional Day 60+ (On Deck AI or AI-native On Deck Catalyst alumna only) — Apply to Generative AI Accelerator. Selection in 60–90 days; additional $200K–$400K for accepted applications.

XIWhat On Deck fellows typically get wrong about AWS credits

• Assuming On Deck fellowship participation alone unlocks Portfolio — The most common mistake by a wide margin. On Deck fellows assume the fellowship name on the ACE submission is sufficient to support the partner-filed Portfolio range. It is not — the Portfolio Sub-Program standing arrangement does not exist for On Deck, and the partner-mediated path requires layered institutional signal (fellowship + post-fellowship seed VC) to support the upper end of the range. Fix: time the partner-filed Portfolio application against the post-fellowship institutional seed round, not against the fellowship itself.
• Stopping at the standing fellowship credit code — On Deck fellows often redeem the $1K–$5K fellowship code, use it during the fellowship, and never realize the partner-filed $50K–$75K Portfolio path exists post-fellowship. The standing code is bundled with the other fellowship perks (Notion, Linear, Stripe, OpenAI) and reads as the AWS perk in full. Fix: file partner-filed Portfolio within four weeks of the institutional seed round closing.
• Failing to layer Bedrock POC for On Deck AI graduates — On Deck AI participants who file only Portfolio leave $25K–$50K of Bedrock POC on the table. The Bedrock POC track is separate from Portfolio; both should be filed in the same week by the same partner. The On Deck AI signal supports the upper end of the Bedrock POC range when paired with a tightly-scoped POC narrative.
• Not coordinating with the post-fellowship seed-round timing — Some On Deck fellows file the partner-filed Portfolio application either too early (before the term sheet is signed, which weakens the institutional signal) or too late (months after the round closes, when the credit windowing is already lost). The cleanest timing is the week the term sheet is signed, with the partner filing the same week.
• Assuming On Deck Founders Fund participation alone provides the Portfolio Sub-Program signal — On Deck Founders Fund is an institutional VC investment vehicle, but it is not a Portfolio Sub-Program member at the accelerator level. A company with On Deck Founders Fund as an investor but without any On Deck fellowship participation reads to AWS reviewers as a seed-stage company with one institutional investor, not as a Portfolio Sub-Program portfolio company. The fellowship participation is what layers in the accelerator-level signal.
• Filing partner-filed Portfolio with stale historical fellowship signal — A 2021 ODF alumna who waited until 2026 to apply for partner-filed Portfolio sometimes leans heavily on the 2021 fellowship participation in the application narrative. AWS reviewers in 2026 read pre-restructure historical fellowship participation as weaker signal than current institutional participation. The fix is to lean the partner narrative more on the recent commercial trajectory (the seed VCs, the AWS consumption projection, the company's scaling traction) than on the historical fellowship name.
• Filing through a partner with no On Deck track record — On Deck applications carry more reviewer scrutiny than YC or Techstars because the institutional verification is partner-mediated rather than standing. Partners with prior On Deck submissions land approvals more consistently because the reviewer pattern recognition reduces friction. Partners new to On Deck take longer per application and sometimes see downgraded awards. CloudRoute routes specifically to On Deck-experienced partners.
• Burning fellowship credits on services that Portfolio will replace anyway — Similar to the YC and Techstars pattern: the standing fellowship code and Portfolio are in the same Activate program at different ceilings. Portfolio absorbs the standing tier rather than stacking. The fellowship code is operationally useful during the partner-filed application window — credits to use while waiting 18 to 25 days for Portfolio — but it is not additive to the final ceiling.
• Confusing On Deck Catalyst with On Deck Founders for credit purposes — Some applicants conflate the post-restructure On Deck Catalyst (accelerator-style, selective cohorts) with the pre-restructure On Deck Founders (community-first, large cohorts). The ACE narrative should specify which program and which cohort year. The credit ceilings are the same across the programs, but the partner narrative differs based on whether the program is current or historical.

XIIWhat a CloudRoute-routed AWS partner does for an On Deck portfolio company

The partner's role for an On Deck portfolio company is structurally similar to other partner-filed engagements, with three On Deck-specific patterns worth flagging.

They file the ACE records — Portfolio, Build for Startups, Bedrock POC if applicable — naming On Deck as the fellowship sponsor and the post-fellowship institutional seed VC as the commercial co-signal. Because On Deck 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, On Deck context, and seed-round timing before filing. On Deck companies are typically very early-stage at the partner-filing moment (just-incorporated, term sheet just signed); the partner sanity-checks whether the use case as described matches what the ACE reviewer is going to want to see, and whether the seed-round timing supports the upper end of the Portfolio range.

They act as the named technical partner on the file. The reviewer cross-references partner history; partners with prior On Deck approvals are recognized and the file moves faster. The first-time On Deck partner takes longer because the reviewer does not have the pattern recognition.

They provide the actual AWS implementation if you want it — production account setup, IAM and VPC, the migration off whatever fellowship-stage infrastructure you used (Vercel, Render, Supabase, PlanetScale, a managed Postgres provider), observability, and deployment pipelines. Most On Deck portfolio companies want this because the post-fellowship 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 and during the post-seed window when Series-A conversations begin.