AWS credits for Station F residents — the $5K self-serve, the partner-filed Portfolio path, and the cross-program signal stacking unique to a campus that hosts 30+ accelerators under one roof.

IWhat Station F actually is — and why the campus model changes how the AWS Activate signal works

Most accelerators are single-program operations: Y Combinator runs the YC batch, Techstars runs a Techstars batch, Plug and Play runs Plug and Play cohorts. Station F is the opposite — a physical campus that houses 30+ separately operated programs, each with its own selection criteria, mentor network, demo day, and institutional backers. Understanding which program a Station F resident belongs to is more important than the campus residency itself when filing an AWS Activate application.

Station F opened in June 2017 in a converted railway freight depot (Halle Freyssinet) in the 13th arrondissement of Paris. The campus was funded by Xavier Niel (founder of Free / Iliad, one of France's most active tech investors) with a stated investment of €250M for the renovation and infrastructure. The architectural footprint — 34,000 square meters, three central halls (Share, Create, Chill) and a dedicated event space — was designed to physically co-locate the diverse startup activity that had previously been distributed across smaller Paris incubators (TheFamily, Le Camping, Numa, 50 Partners).

The campus model is the central operational fact. Station F itself directly operates two programs: the Founders Program (general accelerator, 200 startups per cohort, 12-month residency, sector-agnostic) and the Fighters Program (entrepreneurship for under-resourced founders, similar duration, mission-driven selection). The remaining 30+ programs are run by external partners under residency agreements: Meta hosts the Startup Lab, Microsoft operates the AI Factory, Google for Startups runs its Paris incubator from Station F, HEC Paris runs its Incubator from a dedicated Station F space, Daphni operates the Daphni Yellow program, and many more.

A startup at Station F is therefore in one of three configurations: (1) a Founders Program or Fighters Program resident, operated directly by Station F; (2) a partner-program resident, operated by Meta / Microsoft / HEC / Google / Daphni / etc., with Station F providing the physical infrastructure but not the program substance; or (3) very rarely, a cross-program resident — a startup admitted to two Station F-hosted programs simultaneously. The cross-program configuration is the most interesting from a credit-application perspective and is covered in section VII below.

For AWS Activate purposes, the campus residency itself generates a recognizable cohort signal — EU-Central reviewers see "Station F resident" in the partner-filed narrative and recognize the campus as a substantive ecosystem marker. But the campus residency is not a Portfolio Sub-Program vouch in the way YC batch membership or Techstars batch membership are. The institutional signal that unlocks the Portfolio tier comes from the underlying program (or, more commonly, from the VC funding round that closed during or shortly after the program).

This distinction matters because it determines which credit ceiling a Station F resident can realistically file for. A Founders Program resident with no VC backing has a different credit ceiling from a Meta Startup Lab resident with Meta-adjacent strategic backing, which has a different ceiling from a Daphni Yellow resident with Daphni Seed money already in the bank. The application narrative reads differently in each case, and the partner who files the ACE record needs to know the program-specific context.

IIThe 30+ accelerator programs at Station F — what each one signals to AWS Activate

No single 2026 page can list all 30+ programs definitively because the roster shifts year to year (some partners exit, new ones join, programs rebrand). The list below covers the largest and most credit-application-relevant programs, with notes on what each signals when it appears in a partner-filed ACE narrative.

The roster splits roughly into four buckets: Station F's own programs (Founders Program, Fighters Program, Future 40 designation), corporate-partner programs (Meta, Microsoft, Google, L'Oréal, LVMH, BNP Paribas, and others), VC-partner programs (Daphni Yellow, Hexa, and several others where a VC runs a residency program from Station F), and academic-partner programs (HEC Paris Incubator, École Polytechnique, École 42-adjacent residencies). The credit-application signal varies meaningfully by bucket.

Station F Founders Program. The in-house general accelerator. Selection is competitive (~3% acceptance from ~6,000 annual applications). The program is sector-agnostic, 12-month residency, with structured mentorship from Station F staff and the broader resident network. Founders Program membership is the strongest "pure Station F" signal — the partner narrative reads "Founders Program 2026 cohort," and the EU-Central reviewer queue treats this as comparable to a mid-tier French accelerator graduation. It supports $5K Activate Founders self-serve cleanly and $25K–$50K Portfolio partner-filed when the use case is well-scoped. Reaching $100K Portfolio typically requires a VC funding signal layered on top of Founders Program membership.

Station F Fighters Program. Entrepreneurship program for under-resourced founders (immigrants, founders without prior network access, founders from underrepresented backgrounds). Smaller cohort, more intensive support. AWS Activate treats Fighters Program membership identically to Founders Program for credit-application purposes. The narrative typically frames the company's mission-driven trajectory alongside the technical workload.

Station F Future 40. Not a residency program but a designation — Station F's annual selection of its 40 most-promising current and recent residents. Future 40 status is the strongest pure-Station F signal an application can carry. The partner narrative referencing "Future 40 2026 cohort" reads to the EU-Central reviewer as comparable to French Tech 120 designation. Future 40 designation supports Portfolio approvals at the upper end of the partner-filed range ($75K–$100K) more reliably than baseline Founders Program membership.

Meta Startup Lab. The Paris-based Meta program (previously branded "Facebook Startup Lab," rebranded after Meta's 2021 corporate name change). Focuses on companies building on Meta platforms (Instagram, WhatsApp, Messenger, Reality Labs / Quest) or in AR/VR adjacent verticals. Cohort size is small (typically 15–25 startups). The Meta Startup Lab signal is recognizable to AWS reviewers because the Meta-AWS coopetition dynamic is well understood — companies in Meta Startup Lab often have a clear platform-API integration story that maps to specific AWS service consumption (Bedrock for Meta-adjacent ML workloads, CloudFront for content distribution, Kinesis for telemetry). Portfolio applications from Meta Startup Lab residents land at $50K–$100K depending on the funding signal.

Microsoft AI Factory. Microsoft's Paris AI-focused program at Station F. The program emphasis is on AI startups building with Microsoft's AI stack (Azure OpenAI Service, Microsoft Copilot platform, Fabric). The AWS Activate dynamic here is interesting: Microsoft AI Factory residents often run dual-cloud workloads (Azure for the Microsoft-platform-aligned features, AWS for the rest), and the AWS partner-filed application narrative typically scopes only the AWS-resident workload (Bedrock POC for non-Azure AI inference, general SaaS infrastructure for the multi-tenant platform). The Microsoft AI Factory signal in the AWS narrative is positive — it reads as a sophisticated AI startup with clear architectural decisions about which workloads live on which cloud — but the application has to be scoped carefully to the AWS-resident portion.

HEC Paris Incubator. The incubator operated by HEC Paris (one of France's most prestigious business schools) from a dedicated Station F space. Selection is dominated by HEC alumni and current HEC students. The HEC Paris Incubator signal is recognized in the application narrative — HEC is a well-known European institution and the affiliation reads positively. Portfolio applications from HEC Paris Incubator residents follow the general Station F pattern: $50K–$100K depending on the funding signal layered on top.

Google for Startups. Google's Paris-based program at Station F (part of Google's global Google for Startups network). Similar dynamic to Microsoft AI Factory — companies in Google for Startups often consume Google Cloud for the Google-platform-aligned workloads and AWS for the rest, particularly for non-Google-Cloud-resident AI workloads. The AWS partner-filed application scopes the AWS-resident workload specifically.

Daphni Yellow. The residency program operated by Daphni (Paris-headquartered VC, seed-to-Series-A focused) at Station F. Daphni Yellow residents typically have a Daphni Seed check (~€500K–€2M) already closed or in late-stage diligence at program entry. This is the strongest VC-backed Station F program signal — Daphni Yellow + Daphni Seed → Portfolio approval at $100K is a routine pattern, because the funding signal is already in place and the cohort signal layers on top. The partner narrative typically reads "Station F resident via Daphni Yellow 2026 cohort, Daphni Seed €1.5M closed Q1 2026."

Hexa (formerly eFounders). The B2B SaaS startup-studio model. Hexa is technically headquartered outside Station F but maintains residency presence and graduate companies often re-engage with Station F's broader ecosystem. Hexa-graduated companies have particularly strong AWS partner connectivity because Hexa's portfolio companies (Front, Aircall, Forest, Spendesk, etc.) have established AWS architecture patterns. Hexa-graduates landing at Station F for post-studio scale-up have $75K–$100K Portfolio approval reliability.

Corporate vertical programs. Several large French corporates run vertical-focused programs at Station F: L'Oréal (beauty-tech), LVMH (luxury-tech), BNP Paribas (fintech), Total (energy transition), Vinci (construction-tech). These programs are smaller and more vertical-specific. The corporate-program signal in the AWS application narrative is positive when the vertical match is clear — a fintech startup in BNP Paribas's program with an obvious banking-adjacent use case reads as well-positioned for partner-filed Portfolio at $75K–$100K.

IIIHow Station F residency translates into AWS Activate reviewer recognition

AWS Activate reviewers do not formally weight Station F residency the way they weight Portfolio Sub-Program VC backing. But Station F residency reliably appears in the partner-filed narrative for Paris-HQ applications, and the EU-Central reviewer queue has seen enough of these submissions over the past several years to recognize the signal. The mechanics of that recognition matter for understanding why the same campus residency reads differently across different applications.

AWS Activate's reviewer queues are regional: applications from EU-headquartered companies route to the EU-Central queue (Dublin, Munich, Paris staff predominantly), applications from North American companies route to a US queue, and so on. The EU-Central queue has seen Station F residency referenced in Paris-HQ applications since shortly after the campus opened in 2017. By mid-2026, "Station F resident via [program name]" is a phrase the queue recognizes immediately.

The recognition is not formal — there is no Station F entry in the AWS Activate documentation as an institutional partner. It is operational: EU-Central reviewers see the phrase, recognize it, and assign the application appropriate weight. The weighting depends on the program named alongside the campus residency. "Station F resident via Founders Program" reads as a recognized French accelerator graduation. "Station F resident via Meta Startup Lab" reads as a Meta-platform-adjacent startup. "Station F resident via Daphni Yellow with Daphni Seed €1.5M closed" reads as a VC-backed startup with cohort signal layered on top.

The institutional vouch for Portfolio tier still flows through the underlying program or funding signal — Station F residency itself reinforces but does not constitute the vouch. This is the structural difference from Techstars (which sits in the Portfolio Sub-Program as a single accrediting entity) and from YC (which has automatic $5K Founders distribution at AWS account creation for batch alumni). Station F has neither of those formal arrangements, but the campus residency is recognized operationally.

For a startup whose only institutional signal is Station F residency itself — typically a Founders Program or Fighters Program resident at the start of the program, before any VC funding has closed — the credit-application path is: Activate Founders $5K self-serve immediately (any AWS account holder can claim this), partner-filed Activate Founders at $5K–$25K through ACE for the use-case-specific narrative, and Bedrock POC at $25K if there is a defined AI workload. The Portfolio tier becomes accessible once the funding signal lands (VC seed close, Bpifrance Prêt Innovation, or institutional grant).

For a startup with both Station F residency and a VC funding signal already in place, the partner-filed Portfolio path opens. The narrative reads "Station F resident via [program name], [VC name] Seed/Series-A [amount] closed [quarter]." The reviewer treats this as comparable to a US YC + a16z-Seed combination — the cohort signal and the funding signal stack, and Portfolio approval at $75K–$100K becomes the realistic landing.

IVThe realistic Station F credit stack — $80K–$130K composition with worked examples

The headline range — $80K–$130K — covers most 2026 Station F residents with a credible AWS-resident workload and at least one institutional signal beyond pure campus residency. The composition varies by which Station F program the resident is in, by whether VC backing is already in place, and by whether the workload includes an AI component eligible for Bedrock POC.

The components of the Station F credit stack are the same components available to any other Paris-HQ startup — what changes is the approval probability and the size of the eventual award at each tier.

Component 1 — Activate Founders self-serve ($5K). Any startup with an AWS account can claim the standing $5K Activate Founders credit. The redemption is a self-serve form on the AWS Activate console. Station F residents claim this on day one of program entry (or earlier, if they already have an AWS account). This is the floor; no partner involvement required.

Component 2 — Partner-filed Founders or Portfolio ($25K–$75K). The middle band depends on which Station F program the resident is in and what funding signal accompanies the cohort signal. A Founders Program resident with no VC backing typically lands $25K partner-filed (Activate Founders at the upper end of partner-filed). A Daphni Yellow resident with Daphni Seed closed typically lands $75K–$100K (Activate Portfolio at the middle-to-upper range). The variation is what drives the headline range.

Component 3 — Build for Startups (+$25K). Layers on top when there is a discrete production-engineering workload distinct from the general SaaS infrastructure scope. For Station F residents, the most common Build for Startups workloads are: CNIL-aligned data residency migration (when moving production to eu-west-3 from a non-EU previous cloud), production observability and incident response setup, multi-tenant platform architecture build, or AI gateway and evaluation infrastructure for AI startups. The partner files Build for Startups as a separate ACE opportunity record describing the discrete workload; $15K–$25K is the typical award.

Component 4 — Bedrock POC (+$25K). Earmarked for Amazon Bedrock inference and the supporting infrastructure (S3 for prompt logs, OpenSearch for vector search, Lambda for orchestration). For Station F AI residents (concentrated in Microsoft AI Factory, the Mistral-adjacent cohort, and AI-focused Founders Program tracks), Bedrock POC is the natural fit. Mistral Large 2 on Bedrock in eu-west-3 is the dominant pattern for Paris-HQ AI startups in 2026 — the model is French-trained, the hosting is EU-resident, the latency is intra-Paris, and the partner-filed narrative encodes all three points cleanly.

Worked example — Founders Program, no VC, no AI: $5K self-serve + $25K partner-filed Founders + $25K Build for Startups (production setup workload) = $55K (≈€50K). Bedrock POC not applicable. Total founder time across application: ~3 hours.

Worked example — Founders Program, no VC, AI workload: $5K self-serve + $25K partner-filed Founders + $25K Build for Startups + $25K Bedrock POC (Mistral Large 2 inference for a defined POC scope) = $80K (≈€73K). Total founder time: ~4 hours.

Worked example — Daphni Yellow with Daphni Seed, AI workload: $5K self-serve + $75K partner-filed Portfolio + $25K Build for Startups + $25K Bedrock POC = $130K (≈€119K). The Portfolio approval at the upper end is supported by Daphni Seed funding signal alongside Daphni Yellow cohort signal. Total founder time: ~4 hours.

Worked example — Future 40 designation + Series-A close, AI workload: $5K self-serve + $100K partner-filed Portfolio + $25K Build for Startups + $50K Bedrock POC (achievable when AI workload is well-scoped) = $180K (≈€165K). This exceeds the standard $80K–$130K Station F headline range and approaches the full French Series-A ceiling documented separately on the France reference page.

VThe Paris ecosystem density advantage — how Station F's neighborhood concentrates AWS partner availability

Beyond the campus residency itself, Station F sits inside the densest single concentration of AWS partner activity in France. The 13th arrondissement and the immediately adjacent areas (12th, 5th, broader central Paris) host the Paris offices of most French Premier-tier AWS partners and a meaningful subset of the European AWS partner network. This concentration shortens the partner-matching and partner-onboarding loop for Station F residents.

AWS partners with French Premier-tier or Advanced-tier accreditation cluster in Paris because the partner business follows the customer base. French enterprise headquarters are predominantly Paris-headquartered; the consulting talent pool is Paris-anchored; the AWS sales team for France works out of the Paris office. The result is that Station F residents can access in-person partner discovery, on-site solutions-architect engagement, and shared-office working sessions without scheduling friction.

The density matters concretely for credit applications in three ways. First, the partner-matching window is shorter — CloudRoute routes Station F resident inquiries to Paris-headquartered partners in under 24 hours typically, often under 12 hours during business days, because the partner pool is geographically immediate. Second, the discovery call frequently happens in person at Station F itself — Station F provides meeting space for residents and visitors, and partners can come on-site for the use-case scoping call. Third, the subsequent partner engagement (AWS account setup, eu-west-3 architecture configuration, CNIL-aligned data residency posture, Bedrock POC scoping) benefits from continued in-person collaboration when the partner office is within Paris metro distance.

The Mistral AI office in Paris (Mistral was founded in 2023, headquartered in Paris with its main office near Place Vendôme, ~3 km from Station F) is a separate ecosystem factor that interacts with Station F density. Paris-HQ AI startups building on Mistral foundation models often interact with Mistral's developer relations team and Mistral-aligned engineering community. For AWS-resident workloads using Mistral on Bedrock, the geographic adjacency translates into easier access to Mistral-specific guidance during the Bedrock POC scoping phase.

The Bpifrance Hub at Station F (Bpifrance maintains a small dedicated space inside the campus for grant program intake and resident-startup engagement) is a fourth density factor. Station F residents pursuing Bpifrance Prêt Innovation (the non-dilutive grant program) or Bpifrance equity investment have on-site access to Bpifrance staff. This does not affect the AWS Activate application directly, but it does affect the timing of the institutional signal that supports Portfolio tier approval — Bpifrance Prêt Innovation often serves as an interim funding signal before a private-VC round closes.

For Station F residents considering the AWS partner engagement, the density advantage compounds. The partner matching is faster, the discovery is more efficient, the AWS account configuration happens with fewer scheduling delays, and the post-credit-issuance support is reachable in person. None of this changes the credit ceiling — the ceilings documented in section IV apply regardless of where the partner office is — but it does compress the engagement timeline from typical 8–10 weeks to ~6 weeks for a well-scoped Station F resident.

VIWhen a Station F resident is in two programs simultaneously — the cross-program signal-stacking pattern

A small but recurring pattern: a startup admitted to two Station F-hosted programs simultaneously. The configuration is rare (most programs prohibit dual residency, and the operational overhead of two parallel cohort commitments is real), but when it occurs, the partner-filed application narrative can reference both programs and the combined signal supports more aggressive Portfolio approval scoping.

The most common dual-program configurations CloudRoute has observed at Station F: (1) Founders Program + a corporate vertical program (e.g., Founders Program + L'Oréal BeautyTech for a beauty-tech startup), (2) Founders Program + a VC-partner program (e.g., Founders Program + Daphni Yellow when the company entered Founders Program first and Daphni Seed closed mid-program), (3) corporate vertical program + Future 40 designation (a corporate-program graduate later named to Future 40), and (4) very rarely, two vertical corporate programs simultaneously (extremely rare; would require explicit approval from both corporate program operators).

For the partner-filed AWS Activate narrative, dual-program residency reads as a particularly strong cohort signal. The narrative phrasing typically takes the form: "Station F resident via [Program A] and [Program B] concurrent participation; [optional: Future 40 designation 2026]; [VC funding signal if applicable]." The EU-Central reviewer queue treats this as comparable to a US YC + a16z + a vertical-strategic-investor combination — multiple independent institutional vouches stacking.

The credit-application implication: a dual-program Station F resident with no VC backing can credibly file for Portfolio tier ($50K–$75K) on the strength of the cohort signal alone, where a single-program resident in the same funding state would typically be capped at $25K–$50K partner-filed Founders. A dual-program Station F resident with VC backing typically lands at the upper end of the Portfolio range ($100K) more reliably than a single-program peer with comparable funding.

The Future 40 + program-membership combination is the most common form of "cross-program" stacking in practice, because Future 40 is a designation rather than a program (Future 40 designees are also resident in some primary program — Founders Program, Fighters, or a partner program). The Future 40 designation specifically reads to the EU-Central reviewer queue as a strong Station F-internal signal, comparable to French Tech 120 designation in the national French Tech ecosystem.

Operationally, the dual-program pattern requires the partner to know both program names and to scope the use-case narrative across both program contexts. This is where the partner's prior Station F experience matters — a partner who has filed several Station F applications recognizes the dual-program signal and writes the narrative to leverage both. A partner unfamiliar with Station F might list only one program and underweight the application.

VIIThe Station F-specific application narrative — what the partner writes into ACE

Every partner-filed Activate application is an ACE record with structured fields and a free-text narrative. The Station F-specific narrative encodes the program name, the funding signal (if any), and the Paris-specific compliance language (eu-west-3, GDPR, CNIL). Here is the structural pattern a CloudRoute-routed partner uses for a Station F Founders Program resident with closed seed funding and an AI workload.

Company-info block (4 sentences): "Paris-headquartered seed-stage AI startup, 11 engineers, €3.2M seed closed Q1 2026 led by a French seed fund with Bpifrance Prêt Innovation co-funding. Station F resident via Founders Program 2026 cohort. Building a vertical-AI platform for French professional-services firms using Mistral Large 2 as the primary reasoning model. Existing AWS spend $3.8K/month on a partial eu-west-3 footprint."

Use-case paragraph (Portfolio): "Production workload runs in eu-west-3 (Paris) across three Availability Zones for HA. Service mix: EKS for the application control plane, Amazon RDS Aurora PostgreSQL for application metadata, Amazon S3 for document storage and retrieval-augmentation corpora, Amazon OpenSearch Service for vector and lexical search, AWS Lambda for asynchronous workflows, Amazon CloudFront for static asset delivery, Amazon Cognito for B2B authentication. All services in scope of AWS's ISO 27001, ISO 27017, ISO 27018, and SOC 2 Type 2 attestations; AWS DPA executed via AWS Artifact; GDPR data residency confirmed eu-west-3 only. Projected AWS consumption: $7.2K/month at end of 2026 ramp."

Use-case paragraph (Build for Startups): "Distinct from the production application workload: we are building the production AI gateway and evaluation infrastructure as a discrete platform-engineering workload. Service surface: Amazon API Gateway for the model gateway, AWS Lambda for prompt routing, Amazon DynamoDB for prompt-version and evaluation-result storage, Amazon SQS for asynchronous evaluation queueing, Amazon CloudWatch with custom metrics for inference-latency and quality SLOs. Projected consumption for this discrete project: $1.4K/month. Launch target Q3 2026."

Use-case paragraph (Bedrock POC): "Production AI workload: an LLM-assisted professional-services copilot for French-language client document handling. The copilot ingests client documents, performs retrieval-augmented generation over a 1.6M-document professional-services corpus, and produces structured advisory summaries. Model selection: Mistral Large 2 (eu-west-3 hosted on Bedrock) as primary reasoning model, Claude Sonnet 4 (EU-resident variant in eu-west-3) for cross-language references, Amazon Titan Embeddings for the RAG layer. Evaluation methodology: N=500 historical advisory examples with practitioner-validated ground truth; quality measured as BLEU + ROUGE + practitioner blind-rating against ground-truth summary; 90-day evaluation window. Projected Bedrock spend: $2.1K/month at POC scale."

Station F and ecosystem addendum: "Station F resident via Founders Program 2026 cohort; sector-aligned mentorship engaged through the in-house program staff. Seed funding signal: €3.2M closed Q1 2026 led by [seed fund] with Bpifrance Prêt Innovation co-funding; cap table includes both private and quasi-public institutional signatures. Engineering and operations co-located at Station F campus; AWS partner solutions-architect engagement scheduled for on-site working sessions at Station F's shared meeting infrastructure."

The narrative is approximately 350 words across the four blocks. It costs the partner ~10 minutes to write once the discovery call has surfaced the relevant facts. The EU-Central reviewer queue processes the application within 11–18 days from filing. Approval typically lands as: Portfolio at $50K–$75K (depending on the seed signal strength), Build for Startups at $20K–$25K, Bedrock POC at $25K. Combined with the $5K self-serve, the total credit pool lands $100K–$130K (≈€92K–€119K).

VIIIThe Station F credit-application timeline — 14–18 days from inquiry to credit balance

Day 0 — Submit a CloudRoute inquiry indicating Station F residency. Provide program name (Founders Program, Fighters, Meta Startup Lab, Microsoft AI Factory, HEC Paris Incubator, Daphni Yellow, Future 40, etc.) and current funding signal.

Day 1 — Routed within 24 hours to a Paris-headquartered French Premier-tier or Advanced-tier AWS partner with documented prior Station F application track record. Discovery call scheduled within 2 business days.

Day 2–3 — Discovery call (45 minutes). Often on-site at Station F's shared meeting infrastructure given the Paris partner-density advantage. Partner confirms program membership, scopes Activate Founders / Portfolio + Build for Startups + Bedrock POC applicability, identifies the institutional vouch structure.

Day 3–4 — Founder provides company info, AWS account ID (or "create one with me"), use-case paragraphs, deck. ~3–4 hours of total founder time across the discovery and information-gathering phase.

Day 5 — Partner files the ACE records: typically Portfolio + Build for Startups + Bedrock POC if AI, or Founders + Build for Startups + Bedrock POC if pre-VC. All filed within the same business day, with the Station F program name and (if applicable) funding signal pre-loaded in the narrative.

Day 5 (parallel) — Founder claims the $5K Activate Founders self-serve credit through the AWS Activate console. Credits land in 24–48 hours.

Day 11–14 — Portfolio (or partner-filed Founders) approval lands first. EU-Central reviewer queue processes the Station F-narrated applications at typical speed for the queue.

Day 12–16 — Build for Startups approval lands. Often layered within ~2 days of the Portfolio approval given the same partner is filing both.

Day 14–18 — Bedrock POC approval lands. Slightly longer review cycle for Bedrock POC because the POC scope and evaluation methodology require additional reviewer cross-check.

Day 18 onward — Full credit stack visible in AWS Billing dashboard under "promotional credits." $80K–$130K total auto-applies against monthly invoices.

Optional Week 4 onward — Partner begins production engagement: AWS account hardening (IAM, KMS customer-managed keys, eu-west-3 architecture, CloudTrail multi-year retention), CNIL-aligned data residency confirmation, Bedrock POC architecture setup (model gateway, evaluation harness), Mistral / Claude EU-resident model integration. Partner engagement is funded by AWS through the engagement-funding mechanism; customer pays €0.

IXA worked anonymized example — Station F Founders Program AI resident, mid-2026

The following is an anonymized composite of a recent Station F Founders Program resident match. Identifying details (company name, founders, specific seed-fund name, exact funding amount, specific vertical) have been obscured; the operational facts (program membership, funding signal class, AWS architecture, credit-stack composition, timeline) are accurate.

Company context. Paris-headquartered seed-stage AI startup, 9 engineers, €2.8M seed closed Q4 2025 led by a French seed-stage fund with Bpifrance Prêt Innovation co-funding. Station F resident via Founders Program 2026 cohort, six months into the 12-month residency. Building a French-language professional-services AI copilot vertical product. Existing AWS spend $4.1K/month on a partial eu-west-3 footprint; founders had built the early prototype on a self-managed deployment that pre-dated the Mistral-Bedrock integration.

Inquiry. Submitted to CloudRoute via the Station F resident referral path. Initial scope: confirm partner-filed Portfolio applicability, understand the realistic stack ceiling for a Founders Program resident with closed seed funding, validate whether Bedrock POC is appropriate for the AI workload.

Routing. Matched within 14 hours to a Paris-headquartered French Premier-tier AWS partner with documented Bedrock POC track record and prior Station F Founders Program applications filed (4 in the past 12 months, all approved). Discovery call scheduled for day 3, on-site at Station F's Share hall meeting infrastructure.

Discovery scoping. The 45-minute discovery call surfaced three distinct workloads: (1) the general SaaS infrastructure for the multi-tenant copilot platform (Portfolio scope), (2) the production AI gateway and evaluation infrastructure as a discrete platform-engineering workload (Build for Startups scope), and (3) the Mistral Large 2 + Claude Sonnet 4 inference workload with a defined evaluation methodology over N=500 advisory examples (Bedrock POC scope). The partner confirmed all three were credibly filed.

Filing. Day 5: partner filed three ACE records within the same business day. Portfolio narrative referenced Founders Program 2026 cohort, seed funding signal (€2.8M closed Q4 2025, lead seed fund named, Bpifrance Prêt Innovation co-funding noted), and eu-west-3 production architecture with GDPR DPA executed and CNIL-aligned data residency. Build for Startups narrative scoped the AI gateway as a distinct project with launch target Q3 2026. Bedrock POC narrative specified Mistral Large 2 and Claude Sonnet 4 EU-resident model selection, evaluation methodology, and 90-day evaluation window.

Approvals. Portfolio approved on day 13 at $75K (upper end of the Founders Program + seed-funded range). Build for Startups approved on day 14 at $25K. Bedrock POC approved on day 16 at $25K. Combined with the $5K Activate Founders self-serve credit claimed by the founder on day 5, the total credit pool reached $130K (≈€119K). Total founder time across application: ~4 hours.

Post-approval engagement. Partner engaged on production AWS architecture week 4: eu-west-3 account hardening, IAM Identity Center configuration, KMS customer-managed keys for prompt logs and document corpora, CloudTrail multi-year retention in dedicated log-archive account, Bedrock model gateway with Mistral Large 2 ARN and Claude Sonnet 4 EU-resident ARN. Migration of legacy inference workload from previous deployment to Bedrock completed week 7. CNIL-aligned Registre des Activités de Traitement and data subject rights workflow implemented week 7 alongside the migration.

Outcome. Total engagement window: 9 weeks from inquiry to production-ready eu-west-3 architecture with full credit stack applied. Total founder time: ~12 hours across application and partner engagement. Total customer cost: €0; partner compensated by AWS through engagement-funding mechanism; CloudRoute commission paid by partner from engagement-funding allocation.