AWS credits for Seedcamp portfolio companies — how the European seed VC vouch composes into a $130K–$155K stack.

IWhat Seedcamp actually is — Europe's first seed VC, not a batched accelerator

Seedcamp was founded in London in 2007 by Saul Klein, Reshma Sohoni, and others as a seed-stage investment vehicle specifically targeting European founders at a time when Europe had essentially no institutional seed capital available outside the UK and France. It pre-dates Y Combinator's opening to non-US founders by several years and was the first European entity to operate on a pre-revenue, founder-friendly cheque-size seed model. Its structural choices have evolved meaningfully since 2007 but its position in the European seed ecosystem has remained essentially unchanged: the longest-tenured seed VC on the continent, with the broadest European founder network, the deepest European LP base, and the strongest cross-border European positioning of any single fund.

The original Seedcamp model (2007–2012) was closer to an accelerator format than its current form — Seedcamp Week ran annual cohort selection events where shortlisted European founders pitched to a Seedcamp investment committee, with selected companies receiving a small initial investment and mentorship from a pan-European partner network. Several of Seedcamp's most prominent portfolio investments (TransferWise/Wise in 2011, Erply, Codility, and others) came through Seedcamp Week cohorts during this period.

The current Seedcamp model (post-2017, after several fund cycles) is a continuous-investment seed VC operating from a stable London office with a small investment team and a structured cohort-style portfolio-days rhythm. Investment decisions are made continuously throughout the year; cheque sizes have grown into the £250K–£1M range for typical seed investments, with follow-on participation through Seedcamp's subsequent funds. The cohort-style portfolio days (Seedcamp Days, twice annually; Open Office events monthly) are now portfolio-engagement events for already-funded portfolio companies rather than batch-selection events for prospective investments. The cohort framing is real but it sits on top of an underlying continuous-investment model.

Seedcamp's portfolio as of 2026 includes the following companies that are relevant context for AWS reviewer recognition: UiPath (robotic process automation, NYSE-listed 2021), TransferWise / Wise (cross-border payments, LSE-listed 2021), Revolut (challenger bank, in IPO process 2026), Pleo (Danish expense management, late-stage), Tide (UK SMB neobank, late-stage), Codacy (automated code review), Hopin (events platform, late-stage acquired), TaxScouts, Pollen, Kaedim, and a long tail of approximately 500 portfolio investments across 15+ countries. The portfolio concentration around fintech, dev tools, and B2B SaaS reflects the European founder pattern Seedcamp specifically backs.

The team running Seedcamp as of 2026: Reshma Sohoni and Carlos Espinal as managing partners (Sohoni since founding; Espinal since 2010), with a small partner team and an extensive operating-advisor network covering most European startup ecosystems. The fund structure: Seedcamp Fund V (active for new investments through 2026–2027), Seedcamp Fund IV (follow-on participation), and earlier funds (Seedcamp III, II, I) in distribution mode. LP base: primarily European institutional LPs, family offices, and corporate venture arms; some North American LP participation in later funds.

For the purposes of AWS credit applications, what matters about Seedcamp is the institutional vouch status: Seedcamp is recognized in AWS Activate Portfolio Sub-Program as an institutional voucher, which means a Seedcamp portfolio company qualifies for partner-filed Portfolio tier credits on the basis of being a Seedcamp portfolio company. There is no batch-graduation gating because Seedcamp doesn't run batches in the YC sense; the institutional vouch is continuous, tracking the fund's ownership position rather than a cohort calendar.

IISeedcamp inside AWS Activate Portfolio Sub-Program — what the institutional vouch actually unlocks

AWS Activate has four credit tiers reachable through different routing paths: Founders (self-serve, $1K–$5K), Portfolio (institutional vouch required, $25K–$100K ceiling), Build for Startups (additive workload-specific, +$25K), and Bedrock POC (additive AI-specific, +$25K up to $50K in select cases). For Seedcamp portfolio companies, the institutional vouch unlocks the Portfolio tier on the basis of Seedcamp's Portfolio Sub-Program enrollment.

The Activate Founders tier ($5K) is available to any Seedcamp portfolio company through the standard self-serve form at aws.amazon.com/activate — Seedcamp portfolio companies typically claim this during the application window for the larger Portfolio tier, providing immediate credit balance to use during the 12–20 day Portfolio review window. The Founders credit is technically the same Activate program as Portfolio at a lower ceiling, so when Portfolio is approved it replaces the Founders tier rather than stacking — the founder gets $100K Portfolio, not $105K total. The $5K Founders is useful during the application window, not as additive credit on top.

The Activate Portfolio tier ($25K–$100K) requires an institutional vouch. For Seedcamp portfolio companies, the vouch is Seedcamp itself — the application is filed by an AWS partner via the Partner Network ACE (AWS Customer Engagement) system, naming Seedcamp as the institutional sponsor, with the partner providing the supporting documentation (Seedcamp investment date, cheque size if disclosable, current Seedcamp ownership position, Seedcamp board observer or partner contact if applicable). AWS reviewer verifies the Seedcamp portfolio company status against Seedcamp's confirmed portfolio list; approval typically lands within 12–20 days. The Portfolio ceiling is determined by the AWS reviewer based on the application narrative, the use case clarity, the projected AWS spend, and the institutional signal strength — Seedcamp is a recognized voucher, which sits above the average European seed fund but below the highest-recognition voucher tier (a16z, Sequoia, Index Ventures, Atomico).

The Build for Startups tier (+$25K) requires a distinct second workload — a clearly-scoped engineering project separate from the production SaaS infrastructure funded by the Portfolio tier. For Seedcamp portfolio companies, the canonical Build for Startups workloads include: SOC 2 Type II implementation work (for portfolio companies expanding into US enterprise sales), GDPR / ISO 27001 compliance build (for portfolio companies pursuing European enterprise customers), data lake or analytics platform build (for portfolio companies productizing customer data), and observability platform build (for portfolio companies maturing past early product-market fit).

The Bedrock POC tier (+$25K up to $50K) requires a clearly-scoped Generative AI proof-of-concept with defined model selection, evaluation methodology, and projected inference budget. For Seedcamp portfolio companies, the canonical Bedrock POC workloads include: LLM-assisted customer support chat (most common, applies to nearly any B2B SaaS), LLM-assisted document drafting or summarization (for portfolio companies in legal, finance, or regulatory verticals), retrieval-augmented generation for internal knowledge search (for larger portfolio companies with significant internal documentation), and AI agent workflows for repetitive operations (for portfolio companies productizing process automation). The Bedrock POC ceiling sits at $25K for typical applications; $50K is achievable when the projected inference budget justifies it and the evaluation methodology is rigorous.

The stacking math for a Seedcamp portfolio company in 2026: $5K Founders (during the application window) + $75K–$100K Portfolio (Seedcamp institutional vouch) + $25K Build for Startups (distinct workload) + $25K Bedrock POC (AI feature) = $130K–$155K total. The lower band ($130K = $5K + $75K + $25K + $25K, treating Founders as additive during the burn-window which is the realistic interpretation) reflects pre-product-market-fit applications; the upper band ($155K = $5K + $100K + $25K + $25K) reflects strong-narrative applications with the partner pre-loading the Seedcamp signal.

• Activate Founders ($5K) — Self-serve via aws.amazon.com/activate. Available to any Seedcamp portfolio company. Useful during the Portfolio application window for immediate credit balance; technically replaced by Portfolio when Portfolio is approved.
• Activate Portfolio ($25K–$100K) — Partner-filed via ACE with Seedcamp as the institutional voucher. Typical approval window 12–20 days. Approval at $75K–$100K range depends on application narrative quality and use-case clarity.
• Build for Startups (+$25K) — Additive workload-specific tier requiring a distinct second project. Common Seedcamp portfolio scopes: SOC 2 Type II implementation, GDPR / ISO 27001 build, data lake, observability platform.
• Bedrock POC (+$25K up to $50K) — Additive AI-specific tier requiring a scoped POC with defined model, evaluation methodology, projected inference budget. Common Seedcamp portfolio scopes: customer support chat, document drafting, RAG knowledge search, AI agent workflows.

IIISeedcamp vs Y Combinator — three structural differences that change the credit application

The "European YC" shorthand obscures three structural differences between Seedcamp and Y Combinator that materially change how the AWS credit application is filed for a Seedcamp portfolio company vs a YC portfolio company. The shorthand is useful for orienting prospective founders; for the AWS partner filing the ACE record, the underlying structural differences matter.

First, scale and concentration. Y Combinator has invested in 5,000+ companies across roughly 30 batches since 2005 (W26 batch as of 2026 brings the cumulative count above 5,200); Seedcamp has invested in approximately 500 companies since 2007 across continuous investment cycles. The 10x scale difference means the YC voucher carries more reviewer-recognition signal in absolute terms simply because more YC companies have come through the Activate Portfolio queue. The Seedcamp voucher is well-recognized in the EU-West AWS reviewer queue specifically, where most Seedcamp portfolio company applications route, but is less reviewer-recognized in the US-East queue. The practical effect: a Seedcamp portfolio company filing for a us-east-1 primary region may get a clarifying question from the reviewer ("can you confirm Seedcamp's investment date and current ownership position?") that a YC portfolio company filing for the same region would not get. The clarification adds 2–3 days; the Seedcamp partner pre-loads the documentation to minimize the friction.

Second, investment timing and structure. YC invests in batches with a fixed program structure (3-month program, Demo Day at conclusion, standard SAFE terms historically and now a standard direct-investment structure since 2022). The YC batch graduation date is a known cohort signal: an AWS reviewer seeing "YC W26 graduate" can immediately verify the batch list and confirm membership. Seedcamp invests continuously without batches; the Seedcamp portfolio company status is verified against Seedcamp's portfolio page rather than a batch list. The verification is reliable but takes a different mechanic — the AWS partner pre-loads Seedcamp's investment date and current portfolio status into the ACE record, and the reviewer cross-references against Seedcamp's confirmed portfolio page rather than a batch list.

Third, geographic concentration and reviewer-queue routing. YC's portfolio is roughly 70%+ US-incorporated (Delaware C-Corp) with primary US operations; Seedcamp's portfolio is roughly 85%+ European-incorporated (UK Ltd, German GmbH, Estonian OÜ, French SAS, Dutch BV, and others) with primary European operations. The geographic split routes most Seedcamp portfolio company applications to the EU-West AWS reviewer queue (handled out of AWS's Dublin and London teams), while YC portfolio company applications route primarily to the US-East queue. The EU-West queue is reviewer-trained on EU GDPR, UK GDPR, FCA, BaFin, AFM, AMF, and the broader European compliance vocabulary; the partner pre-loads this language into the Seedcamp portfolio company's ACE record rather than the US-style SOC 2 + HIPAA language that the YC application would carry.

The mechanics of the application are otherwise identical between the two cases — same ACE form structure, same approval timelines (12–20 days for Portfolio), same Build for Startups and Bedrock POC additive tiers. The differences live in the application narrative vocabulary and the documentation pre-loading. For a Seedcamp portfolio company, the partner-filed application reads as a European seed-stage company with continuous-investment Seedcamp backing; for a YC portfolio company, the partner-filed application reads as a US-incorporated seed-stage or Series-A company with cohort-graduation YC backing.

IVSeedcamp vs Entrepreneur First — investing post-team vs investing pre-team

Entrepreneur First (EF) is the other prominent London-based early-stage venture entity often grouped with Seedcamp in European founder conversations. EF and Seedcamp serve overlapping geographies but operate on fundamentally different timing — EF invests pre-team-formation through its Founders Cohorts; Seedcamp invests post-team-formation in already-incorporated companies with a defined product direction. The distinction matters for AWS credit applications because the credit eligibility timing differs accordingly.

EF's model: select individual founders ("EF Founders") into 6-month Founders Cohorts running in London, Paris, Berlin, Bangalore, Singapore, Toronto, and other locations. During the cohort, founders identify a co-founder, develop a thesis, validate the thesis against customer discovery, and incorporate a company. EF's investment typically lands at company incorporation, with a follow-on at Demo Day if the company progresses. The EF cohort produces newly-incorporated companies; AWS credit eligibility through Activate Founders ($5K self-serve) becomes available immediately upon AWS account creation; AWS credit eligibility through Activate Portfolio ($100K partner-filed) becomes available once EF has formally invested and the EF institutional vouch is documentable.

Seedcamp's model: invest in already-incorporated companies that approach Seedcamp through the standard inquiry pathway (Seedcamp website, Seedcamp Days application, warm introduction from the Seedcamp network), with a typical investment cheque of £250K–£1M in exchange for equity. The company is already incorporated when Seedcamp invests; the company already has a defined product direction; the company already has a team in place. AWS credit eligibility through Activate Portfolio is available immediately upon Seedcamp's investment closing and the partner-filed application being submitted.

For founders deciding between the two routes, the EF path makes sense for individual technical founders without an existing co-founder or company; the Seedcamp path makes sense for already-formed teams with a defined direction. The AWS credit calculus is downstream of this decision: EF founders access credits sequentially (Founders during cohort, Portfolio after EF investment closes); Seedcamp founders access credits immediately after Seedcamp investment closes. The total credit ceiling is essentially the same in both cases ($130K–$155K for the realistic stack); the timing differs by 6–9 months reflecting the EF cohort timeline vs the Seedcamp direct-investment timing.

For Seedcamp portfolio companies specifically, the AWS partner pre-loading the ACE record should reflect Seedcamp's direct-investment structure: investment date documented, cheque size disclosable to AWS reviewer (Seedcamp typically discloses cheque size in the relevant founder agreement), Seedcamp's board observer or partner contact named if applicable, Seedcamp's position in the broader cap table noted. The application narrative reads as a post-team-formation European seed-stage company with direct Seedcamp investment, not as a cohort graduate.

VThe cross-border European founder pattern that Seedcamp specifically backs

Seedcamp's portfolio reveals a distinctive founder pattern that the AWS partner should encode into the application narrative: cross-border European teams operating across multiple jurisdictions, often with founder backgrounds from multiple European countries, with customer bases spanning the EU and UK from incorporation onward. This pattern affects the AWS region selection, the compliance vocabulary, and the Bedrock model variant selection.

Looking across the Seedcamp portfolio, a recurring founder pattern emerges: technical co-founder from Estonia, Lithuania, or Latvia (the Baltic developer pipeline that produced TransferWise, Pipedrive, Bolt, and others); commercial co-founder from London, Paris, or Berlin (the European commercial cluster); incorporation in the UK (London company) or in one of the EU jurisdictions (Estonian e-Residency company, German GmbH, Dutch BV, French SAS). The team operates remotely across European offices or fully-remote with quarterly in-person sessions; customer base spans the UK and EU from early on; revenue currency mix includes EUR, GBP, and occasionally USD as the company expands into US enterprise sales.

This pattern affects the AWS region selection in a specific way. A Seedcamp portfolio company with a UK-incorporated parent and a cross-EU customer base typically deploys to eu-west-1 (Ireland) as the primary region rather than eu-west-2 (London), because eu-west-1 has the deepest AWS service catalog in Europe, the lowest aggregate latency to a cross-EU customer footprint, and is covered by both the EU GDPR framework directly and the UK GDPR framework via the 2025-renewed EU-UK adequacy decision. Seedcamp portfolio companies with primarily UK customer bases or with UK enterprise customer commitments default to eu-west-2 (London) instead, but the cross-EU founder pattern pushes toward eu-west-1 more often than the general UK startup population.

The compliance vocabulary in the application narrative reflects this pattern: dual EU GDPR + UK GDPR coverage, AWS DPA referenced as the joint Article 28 contract for both regimes, data residency framed as "within the EU and UK under the 2025-renewed adequacy decision" rather than as a single-jurisdiction commitment, secondary region documented as the alternate EU or UK region for exit-path purposes. The partner pre-loads roughly 200 words of compliance language reflecting the cross-border European framing rather than the single-jurisdiction language a US or UK-only startup would carry.

The Bedrock model variant selection follows the same cross-border framing. As of 2026, Amazon Bedrock offers EU-resident model variants for Claude (Sonnet 4, Opus 4, Haiku), Llama 3.x, Amazon Nova, and Mistral Large 2 in both eu-west-1 (Ireland) and eu-west-2 (London). For a Seedcamp portfolio company with a cross-EU customer base, the EU-resident model variant in eu-west-1 is typically the default — inference requests stay within the EU, the model latency to the European customer footprint is favorable, and the compliance commitment to European customers is straightforward. For Seedcamp portfolio companies with substantial UK customer concentration, the UK-resident variant in eu-west-2 may make more sense.

The Build for Startups workload often reflects the cross-border pattern as well. Seedcamp portfolio companies expanding from a single-country product launch into pan-European customer bases frequently scope the Build for Startups workload around a multi-region deployment build — replicating the production workload from a single EU region into a secondary region for latency or DR purposes, implementing the cross-region replication logic, configuring AWS Global Accelerator or Route 53 latency-based routing, documenting the multi-region operational runbook. This is a discrete engineering project separable from the underlying single-region SaaS infrastructure funded by the Portfolio tier.

VISeedcamp Open Office, Seedcamp Days, and what the cohort-style events signal

Seedcamp's cohort-style portfolio engagement events are not the YC-style batch program, but they do produce a portfolio-cohort signal that AWS reviewers and AWS partners use as a routing input. The events themselves don't gate credit eligibility — Seedcamp portfolio company status does — but they shape the partner's pre-loading of the ACE record and influence the timing of the application.

Seedcamp Days run twice annually (typically late spring and late autumn) as 2-day portfolio events in London with all active Seedcamp portfolio companies invited. The agenda includes investment-stage discussions (seed to Series-A transition coaching), operating-focused workshops (sales, hiring, fundraising mechanics), and Seedcamp's partner-network introductions (downstream VCs, AWS and other corporate partners, operating advisors). The Seedcamp Days cohort has roughly 50–80 portfolio companies attending each event; the Seedcamp investment team uses the event to track portfolio progress and route portfolio companies to relevant network resources.

Seedcamp Open Office events run roughly monthly in London as smaller, drop-in office hours for portfolio companies needing specific support — fundraising introductions, customer introductions, operational coaching, compliance and legal navigation. The Open Office cadence is the Seedcamp portfolio-engagement rhythm in between the larger Seedcamp Days events; portfolio companies dropping into Open Office typically come with a specific ask rather than a general check-in. The Open Office attendance is generally 5–15 portfolio companies per event, with Seedcamp partners available across the day.

For an AWS partner pre-loading a Seedcamp portfolio company's ACE record, the relevant signal from these events is the portfolio-engagement timing: a Seedcamp portfolio company that has recently attended Seedcamp Days and received fundraising or operating-stage coaching is typically further along in product-market fit signal than a pre-Seedcamp-Days portfolio company. The partner doesn't cite event attendance directly in the application narrative — that would be too informal a signal for the AWS reviewer — but the partner uses the timing to calibrate the strength of the application narrative around traction and projected AWS spend.

For Seedcamp portfolio companies themselves, the credit application timing often aligns with the immediate post-investment window (apply within the first 60 days of the Seedcamp investment closing) rather than aligning with Seedcamp Days or Open Office. The reason is straightforward: credits compound from issuance, the AWS spend ramp typically follows the seed-stage product development timeline, and the application doesn't depend on portfolio-engagement event attendance. Some Seedcamp portfolio companies wait until after their first Seedcamp Days appearance to file the credit application because Seedcamp Days produces additional partner introductions including to AWS partners, but the wait is opportunistic rather than structural.

Seedcamp portfolio companies that have raised follow-on funding from downstream European VCs (Index Ventures, Atomico, LocalGlobe, Hoxton, Octopus, Notion, Episode 1, Northzone, Balderton) following the Seedcamp seed round can stack the institutional voucher signal: the Activate Portfolio application can name both Seedcamp (as the seed investor) and the follow-on lead VC (as the institutional voucher), which strengthens the application narrative for the AWS reviewer. The combined voucher signal pushes Portfolio approval toward the upper $100K ceiling more frequently than the Seedcamp-only vouch.

VIIThe realistic Seedcamp portfolio credit stack — $130K–$155K with the layer breakdown

The realistic credit stack for a Seedcamp portfolio company in 2026 reaches $130K–$155K across four Activate tiers. The lower band ($130K) reflects pre-product-market-fit applications with limited traction; the upper band ($155K) reflects strong-narrative applications with the partner pre-loading the Seedcamp signal and the cross-border European framing. The stack composes the same way regardless of the Seedcamp portfolio company's specific vertical or country of incorporation.

Layer 1: Activate Founders ($5K self-serve). The standard $5K Founders tier is available to any AWS account holder via the aws.amazon.com/activate self-serve form. For Seedcamp portfolio companies, this is filed immediately upon AWS account creation, providing $5K of credit balance to use during the 12–20 day Portfolio application review window. The Founders credit is technically replaced by Portfolio when Portfolio approves, but the burn window means the $5K is consumed against AWS spend before Portfolio lands — so it functions as additive credit during the application window even though it doesn't add to the Portfolio ceiling.

Layer 2: Activate Portfolio ($75K–$100K, partner-filed). The Portfolio tier is filed by an AWS partner via ACE with Seedcamp as the institutional voucher. The partner pre-loads the application with Seedcamp investment date, current Seedcamp ownership position, the Seedcamp portfolio company's primary AWS region (typically eu-west-1 Ireland for cross-border European founders, eu-west-2 London for UK-focused founders), the EU GDPR + UK GDPR joint compliance language, projected monthly AWS spend, and the use-case narrative. Approval typically lands within 12–20 days. The ceiling lands at $75K for pre-product-market-fit applications and at $100K for stronger-narrative applications.

Layer 3: Build for Startups (+$25K). The Build tier is additive to Portfolio when there is a clearly-scoped discrete second workload. For Seedcamp portfolio companies, the canonical Build scopes are: SOC 2 Type II implementation (for portfolio companies expanding into US enterprise sales), GDPR or ISO 27001 compliance build (for portfolio companies pursuing European enterprise customers requiring formal compliance attestation), multi-region deployment build (for portfolio companies expanding from single-country product launches into pan-European customer bases), and data lake or analytics platform build (for portfolio companies productizing customer data). The Build application is filed in the same week as Portfolio; approval typically lands within 14–16 days.

Layer 4: Bedrock POC (+$25K, up to $50K for select applications). The Bedrock POC tier is additive to Portfolio + Build when there is a clearly-scoped Generative AI proof-of-concept. For Seedcamp portfolio companies, the canonical Bedrock POC scopes are: LLM-assisted customer support chat (the broadest applicable POC), LLM-assisted document drafting or summarization (for portfolio companies in legal, finance, or regulatory verticals), retrieval-augmented generation for internal knowledge search, and AI agent workflows for repetitive operational tasks. The POC must specify model selection (typically Claude Sonnet 4 with the EU-resident variant in eu-west-1), evaluation methodology (typically N=200–500 historical cases with a gold-standard reference), and projected inference budget. Standard Bedrock POC ceiling is $25K; $50K is achievable when the projected inference budget justifies the upper tier.

Total typical stack composition: $5K (Founders, burn-window only) + $100K (Portfolio, upper band) + $25K (Build for Startups) + $25K (Bedrock POC) = $155K upper band. Lower band: $5K + $75K (Portfolio, lower band) + $25K + $25K = $130K. Time-to-balance: 12–20 days from the partner filing the ACE records to the credit balance appearing in the AWS Billing console. Customer cost: £0 / €0 / $0 — the partner is compensated by AWS via the AWS Partner Network engagement funding, not by the founder.

VIIIAn anonymized Seedcamp portfolio company engagement — what the full path looked like

The following is an anonymized representation of a Seedcamp portfolio company engagement routed through CloudRoute in the past 12 months. Identifying details (company name, specific cheque size, named investors, specific customer list) are removed; the structural details (region selection, compliance vocabulary, credit stack composition, timing) are accurate to the engagement profile.

Company profile. Estonian OÜ incorporated company with London commercial presence; 7 engineers split between Tallinn (4) and London (3); Seedcamp seed investment closed Q3 2025 in the £400K range with Seedcamp leading and three angels participating; building a B2B SaaS platform for European mid-market HR teams covering employee onboarding, performance management, and compensation review workflows. Existing AWS spend at the time of CloudRoute inquiry: $1.8K/month across eu-west-1 (Ireland) for the production workload and a small eu-west-2 (London) edge layer for UK customer latency. Primary customer base: UK + 4 EU countries (Germany, Netherlands, Sweden, Estonia) with 9 active enterprise customers and a strong pipeline into the broader Nordic and DACH regions.

The triggering reason for the inquiry. The founder team had been processing the standing $5K Activate Founders credit through self-serve and was approaching the burn-out date on the Founders credit (8 months in). The Seedcamp partner who had introduced AWS specifically had mentioned that "Seedcamp portfolio companies usually qualify for more" but hadn't walked through the specific Portfolio + Build + Bedrock POC mechanics. The founder reached out to CloudRoute via the standard inquiry form citing "Seedcamp portfolio company looking for the full credit stack" as the inquiry framing.

The CloudRoute matching mechanic. Routed within 22 hours to an EU-West Premier-tier AWS partner with documented Seedcamp portfolio engagement history (4 prior Seedcamp portfolio company engagements over the prior 24 months), eu-west-1 production deployment experience, and cross-border European compliance vocabulary fluency. Discovery call (30 minutes) confirmed Portfolio + Build for Startups + Bedrock POC as the three target tiers — Portfolio for the production SaaS, Build for Startups for a planned SOC 2 Type II implementation (US enterprise sales expansion planned for late 2026), Bedrock POC for an LLM-assisted performance review drafting feature.

The application filing. Partner filed three ACE records on day 5 of the engagement: Portfolio with Seedcamp as the institutional voucher and an EU GDPR + UK GDPR joint compliance addendum, Build for Startups with the SOC 2 implementation scope framed as the discrete workload (multi-account AWS Organization restructure, customer-managed KMS, CloudTrail multi-year retention in a log-archive account, GuardDuty + Security Hub + Inspector integration, AWS Backup with documented RPO/RTO, IAM Identity Center), Bedrock POC with the performance review drafting POC scope (Claude Sonnet 4 EU-resident variant in eu-west-1 for the primary reasoning, Amazon Titan Embeddings for the RAG layer, N=300 historical performance reviews with HR-reviewed gold-standard versions, 60-day POC window).

The approval outcome. Portfolio approved at $100K on day 14 (upper band; the application narrative around the cross-border European customer base and the Seedcamp + follow-on angel signal pushed toward the upper ceiling). Build for Startups approved at $25K on day 15. Bedrock POC approved at $25K on day 17 (the application requested $25K rather than the $50K upper tier, reflecting the modest projected inference budget at POC scale). Total credit balance applied: $155K (with the $5K Founders consumed during the application window). Customer cost throughout the engagement: £0.

The downstream usage pattern. The Portfolio $100K covered the production SaaS infrastructure scaling through the 24-month validity window — the EKS cluster, the RDS Aurora PostgreSQL instances, the S3 storage for HR document upload, the CloudFront delivery layer, the Lambda async workflow processors. The Build for Startups $25K covered the SOC 2 Type II implementation work over a 14-week engineering engagement window (multi-account restructure complete week 6, KMS hierarchy complete week 8, CloudTrail and security tooling complete week 10, IAM Identity Center complete week 12, incident response runbook tested week 14). The Bedrock POC $25K covered the performance review drafting POC over a 60-day evaluation window followed by a production launch of the feature for the existing customer base. By the 18-month mark, the founder team had renewed the Portfolio credit balance once (an additional 12-month renewal cycle) and the company had expanded the customer base from 9 to 23 enterprise customers, with US enterprise sales expansion underway following the SOC 2 Type II audit completion.

What the engagement signals about the Seedcamp pathway. The structural details — Seedcamp institutional vouch sufficient for $100K Portfolio approval, cross-border European founder pattern reflected in the application narrative, EU-resident Bedrock model variant selected for the European customer base, partner with documented Seedcamp portfolio engagement history routing through the EU-West AWS reviewer queue — are representative of the typical Seedcamp portfolio company engagement. The customer cost is £0 throughout; the partner is compensated by AWS via the AWS Partner Network engagement funding. The time-to-balance is 14–17 days from filing, which is consistent with the broader EU-West Portfolio approval timeline.