Turkey-incorporated startups have direct access to every AWS Activate partner-filed credit track that US and European startups do — but the file reads with Istanbul-specific texture. The default region is eu-central-1 (Frankfurt, ~50ms to Istanbul) rather than us-east-1. KVKK (Law No. 6698, Kişisel Verilerin Korunması Kanunu) sits over data-handling design. BDDK supervises licensed banking activity; SPK supervises capital-markets-adjacent fintech. TÜBİTAK 1512 BiGG and KOSGEB Ar-Ge grants run parallel to the AWS credit stack as non-dilutive funding. And the Turkish lira moved from TRY 8.5/USD in 2021 to TRY 32–40/USD across 2024–2026 — a structural devaluation that makes USD-denominated AWS credits a meaningful hedge for any Istanbul-based founder budgeting in TRY. This page walks through every credit pool a Turkish-incorporated startup is eligible for in 2026, the regional infrastructure context, the regulatory checkpoints, the Turkish VC and accelerator ecosystem, and the realistic stack ceilings at each funding stage.
Turkey occupies an unusual position in the global startup ecosystem — geographically European, regulatorily standalone, commercially adjacent to MENA, and culturally connected to both Europe and the Turkic-language band running east toward Central Asia. Turkish startups are neither European startups nor MENA startups in the way AWS's standard regional templates assume. The credit programs work the same way; the file reads differently.
A Turkish-incorporated startup applying for AWS credits in 2019 went through the EMEA reviewer queue with no Turkey-specific framing. The reviewer would check the funding history (a Turkish VC name, occasionally a European or US co-investor), confirm a generic SaaS use case, and approve at the standard ceiling. The mechanic worked but did not reflect the Istanbul reality — which regions a workload serving Turkish, MENA, and European customers should run in, what KVKK required of the data architecture, why a 212 or Earlybird Digital East signal carried specific weight, or how the Turkish gaming and e-commerce track records (Peak Games to Zynga at $1.8B in 2020; Trendyol's Alibaba relationship from 2018 and subsequent valuation expansion; Insider's growth across MENA, APAC, and the US; Getir's 2021 valuation peak) shaped reviewer perception of the addressable market for the typical Turkish file.
By 2026 AWS's partner-filed credit reviewers have explicit MENA and EMEA-Turkey context. ACE submissions can explicitly frame use cases around eu-central-1 latency profiles for Istanbul-based customer bases; around KVKK compliance with Turkish Personal Data Protection Authority (KVKK Kurumu) sign-off requirements for sensitive cross-border transfers; around BDDK-supervised licensed payment service providers requiring specific encryption and audit-logging postures; around SPK-supervised crowdfunding platforms operating under capital-markets regulation; around Turkish-language Bedrock POCs with secondary Arabic-language deployment for the MENA expansion case. Reviewers do not require an in-country Turkish workload location — the announced Turkey region is not yet GA — but the application is read more sympathetically when the regional context is articulated with precision.
The credit ceiling for Turkish companies is structurally similar to global ceilings but distributed differently. Where a US Series-A typically files Portfolio at $100K on the basis of a USD $5M–$10M round and a projected $15K/month AWS spend, a Turkish Series-A often files Portfolio at $75K–$100K based on a USD $4M–$8M round (or the TRY equivalent of a comparable round size raised primarily from Turkish institutional capital) and a $8K–$15K/month projected AWS spend. The math underwrites the upper end of Portfolio when the projected consumption is meaningful — and Turkish Series-A consumption is genuinely meaningful at the gaming, e-commerce, and AI-applied verticals where Turkey punches above its weight relative to economic GDP.
The other Turkey-specific texture is currency, and it operates differently from any other MENA-adjacent market. The Turkish lira has been through multiple devaluation events 2021 through 2024: TRY ~8.5/USD in early 2021, ~13/USD by late 2021, ~19/USD by late 2022, ~30/USD by late 2023, ~32–35/USD through 2024–2025, with intermittent movement into the 38–40 range during stress periods. The cumulative move is on the order of 4–5x against USD, comparable in magnitude to the Egyptian devaluation but spread across a longer period with more intermediate volatility. For an Istanbul founder running on TRY-denominated cash from a Turkish-VC-led round, USD-denominated AWS credits act as both a runway extension and a structural hedge against further TRY movement compounding through the AWS billing line item. This is the underdiscussed strategic case for Turkish founders spending the founder time on the credit application — for SAR-pegged or AED-pegged Gulf founders, the same argument has materially less force.
A third Turkish-specific texture: the post-IPO and post-exit founder recycling cycle. Peak Games' acquisition by Zynga (announced 2020), the Trendyol valuation expansion and Alibaba investment cycle (2018–2024), Hepsiburada's Nasdaq listing (2021), Insider's growth into a meaningful global SaaS player, Picus Security's sustained US enterprise traction, and Getir's peak-valuation cycle (followed by the well-documented contraction) collectively produced a generation of Turkish founders and operators who exited or partially exited with capital and credibility, and who are now building or backing the next cohort. The practical effect on the credit landscape: Turkish founders applying for credits in 2026 frequently have a co-founder, board member, or angel investor whose name carries weight with AWS reviewers in their own right — a Peak Games alum or a Trendyol-engineering-team alum is a credible signal at a credit application desk in a way that was not true in 2018.
The credit tracks themselves are the same global Activate program tracks. The framing — what use case maps to what track in the Turkish context, what realistic ceilings look like at each Turkish funding stage, and how Turkish regulatory and accelerator signals shape the partner narrative — is where the country-specific reading sits.
A Turkish founder pulling the credit landscape apart for the first time should know the same thing every founder reading this reference learns: the public-facing AWS Activate page (aws.amazon.com/startups) surfaces the $5K self-serve Founders tier and nothing above it. The $25K, $50K, $100K, and stacking-to-$150K tiers are gated to partner submission via ACE or to direct VC submission through the Activate Portfolio Sub-Program. CloudRoute's routing is the partner-vouch path; the alternative is a Turkish VC submitting directly when they hold Portfolio Sub-Program access.
CloudRoute's read of Turkish VC Portfolio Sub-Program coverage as of Q2 2026: 212 holds direct Portfolio access and submits routinely; Earlybird Digital East coordinates through the broader Earlybird Portfolio relationship; Diffusion Capital is in-and-out depending on the quarter; Logo Ventures, Inveo, Revo Capital, Sabancı Ventures, Türk Telekom Ventures, Aslanoba Capital, and ACT VC vary by quarter and submission load. There is no eligibility downside to going partner-filed when the VC route is uncertain — the application contents are identical; only the submission channel and the timeline-variance differ. Where the VC route is reliable and the VC has bandwidth, both routes converge on the same outcome.
Use case in Turkey: early-stage solo founders, pre-seed Istanbul teams, or Turkish founders bootstrapping on personal capital before a first institutional check. This is the floor for any Turkish startup with a working AWS account and a use case description that survives a three-minute form.
Coverage: $5K. Approval typically lands in 24–72 hours. Validity 24 months from issue.
Common Turkish pattern: a solo founder building a Turkish-language B2C product in Istanbul, currently running Lambda + DynamoDB + S3 + CloudFront at a few hundred USD per month from eu-central-1. The $5K covers 9–18 months of pre-seed AWS spend at typical Turkish-startup pre-seed scale. This is also the right first step to take while a partner-filed application is in-flight — the self-serve credits cover bridge spend during the partner-filed window.
Use case in Turkey: Turkish startups with an accelerator signal (Kworks at Koç University, ITÜ Çekirdek at Istanbul Technical University, ODTÜ Teknokent at Middle East Technical University), with a small angel check from a recognized Turkish operator-angel (Peak Games alum, Trendyol alum, Insider alum), or with an early institutional check that does not yet justify Portfolio-tier projected consumption. The partner-filed Founders tier is where most pre-seed and small-seed Turkish startups land before stacking further.
Coverage: $5K floor (when the application is thin), $25K ceiling (when the accelerator + founder background + use case combination is strong). Validity 12 months from issue.
Timeline: 10–14 days from partner ACE submission. Faster for ITÜ Çekirdek incubator alumni and for ODTÜ Teknokent companies — CloudRoute engagement data shows 9–12 days median for ITÜ Çekirdek and ODTÜ-affiliated Turkish applications, versus 12–16 days for equivalent unsponsored Turkish applications.
Common Turkish use case: an ITÜ Çekirdek 2024 cohort B2B SaaS company building for the Turkish SME segment with a planned MENA expansion, currently running on eu-central-1 with $400–$900/month of AWS spend, projecting $2K–$3K/month within six months as Turkish customer base scales and the first MENA pilot customers come online. Partner files at $25K; reviewer approves; credits cover ~14–18 months of projected spend at the projected scale.
Use case in Turkey: Turkish seed-stage startups with institutional backing (212, Earlybird Digital East, Diffusion Capital, Logo Ventures, Inveo, Revo Capital, Sabancı Ventures, Türk Telekom Ventures) or Turkish Series-A startups with clear projected AWS consumption profiles. The funding signal carries Portfolio review; the projected-spend justification carries the ceiling within the Portfolio band.
Coverage: $50K typical for Turkish seed-stage (often higher than the Egyptian or Saudi equivalent because Turkish seed rounds tend to be slightly larger in USD-equivalent terms and projected AWS consumption tracks accordingly); $75K for Turkish Series-A where projected consumption is meaningful; $100K for Turkish Series-A with strong projected consumption and a clearly articulated multi-region or AI-applied scaling path. Turkish gaming companies and Turkish-MENA-expansion B2C SaaS companies are particularly well-positioned for the $100K ceiling because both verticals carry above-typical projected AWS spend.
Timeline: 11–18 days partner-filed; 14–35 days VC-filed depending on the Turkish VC's operational responsiveness. 212 is responsive within the typical window; Earlybird Digital East coordinates with the wider Earlybird operation, which adds 2–4 days; smaller funds vary more.
Validity: 24 months from issue.
Common Turkish use case: Series-A B2B SaaS in Istanbul, raised USD $6M led by 212 with Diffusion Capital and Sabancı Ventures participating, building for the Turkish and MENA B2B segment on AWS. Founders are a Trendyol-engineering alum and an Insider-product alum. Projected AWS spend $9K–$13K/month within twelve months across eu-central-1 (Turkish customers), me-central-1 (Gulf customers), and a planned eu-south-1 secondary for European pilot accounts. Portfolio approves at $100K to cover ~10 months of projected runway across all regions.
Use case in Turkey: KVKK compliance build is the most common Turkish Build for Startups workload, particularly for B2C startups handling Turkish consumer personal data at scale and for Turkish B2B SaaS handling EU customer personal data with KVKK + GDPR cross-mapping. BDDK Open Banking technical implementation (BDDK announced an Open Banking framework that progressively went live across 2022–2024) is the canonical Build for Startups workload for licensed Turkish fintech entities. SPK-supervised crowdfunding platforms and capital-markets-adjacent fintechs justify Build for Startups for the SPK-aligned audit-logging, customer-identity, and transaction-reporting infrastructure.
Other Turkey-relevant Build for Startups scenarios: migration from a Turkish hosting provider (Turkcell-hosted infrastructure, Türk Telekom-hosted infrastructure, or a regional VPS provider) to AWS eu-central-1 with a documented cutover plan; multi-region build-out for Turkish gaming companies serving Turkish + MENA + European players from a coordinated eu-central-1 + me-central-1 + eu-south-1 architecture; KVKK-aligned data-anonymization pipelines for Turkish AI-applied B2B SaaS feeding customer-derived training data into Bedrock or SageMaker pipelines.
Coverage: $25K. Validity 12 months. Stacks with Portfolio without conflict when the scope is distinct.
The stacking criterion Turkish founders miss: reviewers need to see two non-overlapping workloads in the file. "Portfolio funds my SaaS infrastructure broadly; Build for Startups funds the BDDK Open Banking technical implementation specifically." If Portfolio and Build for Startups describe the same workload, only Portfolio approves. The Turkish KVKK compliance build is similar — distinguishable from generic SaaS infrastructure only if the partner articulates the specific KVKK controls (data classification, consent management, cross-border transfer documentation, retention scheduling) as a discrete engineering project.
Use case in Turkey: Turkish-language generative AI workloads on Amazon Bedrock, with a unique secondary advantage for Turkish startups expanding into MENA — the same product team can run a Turkish-language Bedrock POC for Istanbul customers and an Arabic-language Bedrock POC variant for the Gulf customer base from a single architectural foundation. Claude Sonnet handles Turkish well (the language is morphologically agglutinative and dense in suffixes, which historically tripped earlier LLMs; Claude Sonnet handles it cleanly), and Claude Sonnet handles Modern Standard Arabic and most Gulf dialects with comparable quality, which gives Turkish startups a meaningful cross-border product expansion path on a single Bedrock-backed inference architecture.
Coverage: $10K minimum, $25K typical at Turkish seed stage, $50K for Turkish Series-A with substantial projected inference budget and a defined evaluation framework that names both Turkish and Arabic deployment milestones.
Timeline: 14–28 days. The POC plan needs specificity: which model, what evaluation methodology, what monthly inference budget across Turkish and (where relevant) Arabic deployment, what go/no-go decision criteria.
What works specifically in Turkey: Bedrock POC plans that explicitly name both the Turkish primary market and the MENA Arabic-language expansion case approve favorably because AWS's commercial interest in Bedrock penetration across both markets is high and the cross-border product expansion narrative is credible for Turkish founders specifically. POC plans naming Turkish gaming localization (Turkish-language NPCs and dynamic dialogue), Turkish customer-support automation with multilingual EU expansion, or Turkish-language document processing for Turkish SMEs with Arabic-language variant for Gulf market expansion land particularly well.
Turkey does not yet have a launched in-country AWS region as of mid-2026. AWS has signaled an in-country Turkey region in long-term roadmap communications, but commercial general availability has not been announced. The practical region selections for Turkish workloads are eu-central-1 (Frankfurt) as the default, eu-south-1 (Milan) as the European-customer alternative, me-central-1 (Bahrain) for Turkish-MENA cross-border workloads, and the announced Turkey region as the eventual destination when GA arrives.
The credit award itself is region-agnostic — credits land in your AWS billing console and apply to your invoice regardless of which region your workloads run in. Region selection is a customer-experience and regulatory question, not a credit-eligibility question. Turkish founders should pick the region that serves their customers best today and plan to migrate to the Turkey region when GA is announced; credits transfer with no application changes.
Location: Frankfurt, Germany. The workhorse European region; launched in 2014 and the most service-complete AWS region in Europe alongside eu-west-1 (Dublin).
Latency from Turkey: ~50ms from Istanbul, ~48–52ms from Ankara, ~52–55ms from Izmir, ~55ms from Antalya. The lowest-latency commercial AWS region for the Turkish customer base today.
Service coverage: the most complete service set in Europe. Full EC2, RDS, EKS, Lambda, Bedrock (Claude Sonnet, Claude Opus, Claude Haiku, Llama, Titan, Nova — all GA), S3, DynamoDB, CloudFront edge POPs (with Istanbul and Ankara POPs reducing effective latency for cached content meaningfully below the regional-origin number), IAM Identity Center, Aurora Serverless v2, SageMaker, IoT Core, Bedrock Agents. New Bedrock and SageMaker features land in eu-central-1 in the first or second wave after us-east-1 GA.
Used by: the strong majority of Turkey-serving production workloads CloudRoute sees in partner engagements. Default region selection unless there is a specific reason to choose elsewhere (KVKK + GDPR cross-mapping for European customer bases, MENA customer concentration, or a specific gaming-server latency requirement).
Location: Milan, Italy. Launched in 2020.
Latency from Turkey: ~55ms from Istanbul, ~52–58ms from western Turkey. Marginally higher than eu-central-1 for the Istanbul-anchored customer case; competitive for Turkish workloads with a meaningful Italian or Mediterranean European customer base.
Service coverage: growing toward parity with eu-central-1. Most core services GA; some specialized ML and analytics services land in eu-south-1 a quarter or two after eu-central-1.
Used for: Turkish startups with meaningful Southern European customer concentration; Turkish SaaS targeting Italian, Spanish, or Greek mid-market; Turkish gaming companies optimizing for Mediterranean player latency.
Location: Bahrain. The primary MENA-region anchor for Turkish workloads expanding into Saudi Arabia, the UAE, Kuwait, and the broader Gulf.
Latency from Turkey: ~75ms from Istanbul. Higher than eu-central-1 — not the first choice for Turkish customers — but the right choice for the Gulf customer base in a Turkish-MENA dual-deployment.
Service coverage: the workhorse MENA region. Full EC2, RDS, Lambda, Bedrock (Claude Sonnet, Claude Haiku — with regional model availability for Arabic-language inference), S3, DynamoDB, IAM Identity Center.
Used for: Turkish startups deploying a coordinated eu-central-1 (Turkish customers) + me-central-1 (Gulf customers) architecture. Turkish gaming companies serving Turkish and Gulf players; Turkish B2B SaaS expanding into the Saudi or UAE mid-market; Turkish fintech with cross-border MENA payment use cases.
AWS has signaled an in-country Turkey region in long-term infrastructure roadmap communications. As of mid-2026 commercial GA has not been announced; planning and pre-launch activity is in progress. When the Turkey region launches, KVKK-supervised workloads that currently route through eu-central-1 with documented cross-border-transfer mechanisms will be able to consolidate in-country, simplifying the compliance file substantially. Credit awards are region-agnostic — credits earned today on eu-central-1 will migrate to the Turkey region when you move workloads.
Founders building today should select eu-central-1 as the primary production region with an explicit plan to migrate to the Turkey region when GA is announced. CloudRoute partners building Turkish infrastructure typically use Terraform or CDK modules parameterized by region to make the eventual migration mechanical — the region string changes; the underlying architecture does not.
KVKK (Kişisel Verilerin Korunması Kanunu, Personal Data Protection Law No. 6698), enacted in 2016 and overseen by the Turkish Personal Data Protection Authority (Kişisel Verileri Koruma Kurumu, KVKK Kurumu), is the primary Turkish data-protection regime. It overlaps substantially with GDPR but carries distinct cross-border-transfer authorization mechanics that shape how Turkish AWS workloads are architected and how credit applications are framed.
KVKK requires data controllers handling personal data of Turkish data subjects to register with the Turkish Personal Data Protection Authority through the VERBİS (Veri Sorumluları Sicil Bilgi Sistemi) registry, to implement appropriate technical and organizational measures, to honor data subject rights (access, correction, deletion, objection to processing), to notify the authority of breaches within prescribed timeframes, and — most consequentially for AWS architecture decisions — to obtain explicit authorization for cross-border transfer of personal data to jurisdictions that the Turkish Personal Data Protection Authority has not deemed adequate.
The cross-border transfer authorization mechanic matters specifically because Turkey does not currently have an in-country AWS region. Every Turkish AWS workload by definition transfers personal data across borders — typically to eu-central-1 (Frankfurt), eu-south-1 (Milan), or me-central-1 (Bahrain). For data subjects whose personal data is being transferred, the controller needs either (a) explicit consent for the transfer, (b) one of the legal bases enumerated in Article 9 of KVKK, or (c) appropriate safeguards including binding corporate rules or undertakings approved by the Turkish Personal Data Protection Authority. For most Turkish startups, the practical posture is a combination of explicit consent (collected at signup) and contractual safeguards documented with AWS.
For an AWS workload, this translates into specific service-level configurations: KMS for encryption at rest with customer-managed keys, CloudTrail with documented retention to satisfy KVKK audit-trail expectations, defined data classification across S3 buckets and RDS / DynamoDB stores, consent-management infrastructure (often built on Lambda + DynamoDB) for tracking the lawful basis of each data subject's data, and documented cross-border transfer mechanism with the choice of AWS region rationalized in the data-protection-impact-assessment paperwork.
For credit application purposes, KVKK-relevance is a feature, not a friction. It justifies a discrete Build for Startups workload (the KVKK compliance engineering build) on top of the Portfolio application (the underlying SaaS infrastructure). Turkish B2C startups handling personal data of Turkish consumers at scale, Turkish fintech entities with both BDDK supervision and KVKK applicability, and Turkish B2B SaaS handling employee or customer personal data with both KVKK and GDPR cross-mapping routinely stack Portfolio + Build for Startups for total credit awards in the $75K–$125K range — meaningfully higher than the typical Turkish SaaS file at $50K–$75K.
The mechanic: the partner files Portfolio first, describing the general SaaS infrastructure and projected consumption. They file Build for Startups separately, describing the KVKK controls implementation as a defined 4–8 week engineering engagement with specified deliverables (KMS deployment with customer-managed keys, CloudTrail log archive in a dedicated account, Config rules for data classification compliance, GuardDuty + Macie for sensitive data discovery, incident response runbook, cross-border transfer documentation and DPIA artifacts). The two records do not overlap; reviewers approve both.
Turkish B2B SaaS serving European customers typically operates under both KVKK (for Turkish employee data and any Turkish customer base) and GDPR (for European customer data). The architectural answer is usually a coordinated eu-central-1 (Frankfurt) primary deployment with KVKK + GDPR controls documented in parallel, and a defined data classification that distinguishes which records fall under which regime. Build for Startups can fund the engineering work to implement this cross-mapping cleanly — the partner narrative names KVKK + GDPR cross-mapping as the discrete workload, distinct from the underlying SaaS infrastructure that Portfolio funds.
BDDK (Bankacılık Düzenleme ve Denetleme Kurumu, the Banking Regulation and Supervision Agency) is the Turkish regulatory authority for banks, leasing companies, factoring companies, financial holding companies, and licensed payment service providers. SPK (Sermaye Piyasası Kurulu, the Capital Markets Board) is the regulatory authority for capital-markets activity, including crowdfunding platforms, investment funds, and the increasingly material crypto-adjacent fintech segment under recent regulation. BDDK-supervised and SPK-supervised Turkish workloads carry distinct AWS architecture profiles and a credit-application advantage.
BDDK published its first information-systems-management and audit-related framework in 2007 and has updated it iteratively since, with substantial 2018 and 2020 amendments addressing cloud computing specifically. The current framework permits Turkish licensed banking entities to use cloud services subject to specific control requirements: data residency considerations (with cross-border transfers requiring explicit risk assessment), customer-managed encryption keys for sensitive data, comprehensive audit logging with multi-year retention, defined incident response procedures, and ongoing third-party-risk-management documentation for the cloud provider relationship. For BDDK-licensed payment service providers — a growing segment in Turkey as the BDDK Open Banking framework matures — the practical AWS architecture posture is heavier than for an unregulated B2B SaaS company: KMS with customer-managed keys throughout, CloudHSM for high-assurance signing where applicable, dedicated AWS accounts for production workloads with strict IAM segregation, comprehensive CloudTrail + Config + Security Hub for BDDK-aligned audit trails.
SPK regulation is the relevant overlay for Turkish crowdfunding platforms (which have a distinct SPK licensing framework with capital adequacy, customer-identification, and disclosure requirements), for Turkish alternative-investment platforms, and increasingly for the Turkish crypto-asset service provider segment under regulation that has progressively tightened through 2024 and 2025. SPK-aligned AWS architecture broadly tracks BDDK architecture in shape — encryption, audit logging, incident response — but with capital-markets-specific overlays: transaction reporting infrastructure, customer-identification document handling with KVKK + AML cross-mapping, and (for crypto-adjacent platforms) wallet-management security postures that go beyond typical SaaS architecture.
For Turkish fintech founders, this regulatory texture is among the strongest single justifications for a stacked credit application. Portfolio funds the general SaaS infrastructure; Build for Startups funds the BDDK or SPK technical build specifically; Bedrock POC funds an AI-applied component (KYC document analysis with Claude Sonnet, fraud-detection anomaly scoring with SageMaker, customer-support automation with Bedrock Agents) that is operationally distinct from the regulatory build. Turkish fintech files that articulate all three workloads cleanly land in the $100K–$150K total credit pool consistently — among the highest single-application credit stacks CloudRoute sees in the Turkish market.
A second-order BDDK point worth surfacing: the BDDK Open Banking framework, progressively implemented across 2022–2024, requires Turkish licensed banks and licensed payment service providers to expose customer account data through secure APIs to authorized account-information service providers and payment-initiation service providers. The technical requirements broadly mirror PSD2 in Europe: API Gateway with mutual-TLS authentication, dedicated tenant isolation, comprehensive audit logging, PCI-DSS-aligned card-data handling, ISO 27001 alignment as a baseline. Implementing this on AWS is a 6–10 week focused engineering project across infrastructure, application logic, and compliance documentation — a real workload that justifies a distinct Build for Startups application.
Turkey runs two substantial non-dilutive funding programs that operate in parallel to the AWS credit stack and are worth understanding for Turkish founders building the financing picture as a whole. TÜBİTAK (Türkiye Bilimsel ve Teknolojik Araştırma Kurumu, the Scientific and Technological Research Council of Turkey) runs research and development grant programs at multiple scales. KOSGEB (Küçük ve Orta Ölçekli İşletmeleri Geliştirme ve Destekleme İdaresi Başkanlığı, the Small and Medium Enterprises Development Organization) runs SME-focused support programs including the Ar-Ge (R&D) grants.
TÜBİTAK 1512 BiGG (Bireysel Genç Girişim, Individual Young Entrepreneur Program) is the most credit-stack-adjacent TÜBİTAK program for early-stage Turkish founders. BiGG provides up to approximately TRY 600K–1M (the program adjusts amounts periodically) in non-dilutive grant capital to selected early-stage Turkish entrepreneurs through a structured application process with regional partner organizations. For an AWS credit application, a TÜBİTAK BiGG signal does not directly affect ACE review (AWS reviewers do not specifically recognize the BiGG name in the way they recognize 212 or Earlybird) but the grant capital itself extends startup runway in TRY-denominated terms in a way that complements USD-denominated AWS credits. The two funding mechanisms cover different cost categories: BiGG covers Turkish-headquartered burn (salaries, office, equipment, TRY-denominated services); AWS credits cover USD-denominated cloud infrastructure. Together they meaningfully reduce the headline burn rate for an early-stage Turkish startup.
TÜBİTAK 1507 KOBİ Ar-Ge (SME R&D Support) is the medium-stage TÜBİTAK program covering up to 75% of approved R&D project costs for SME-classified Turkish companies up to defined project budgets. For Turkish startups past the BiGG stage and into a more substantial R&D buildout — including cloud-infrastructure-heavy AI-applied product development — 1507 grants can offset Turkish-side R&D spend in ways that combine cleanly with AWS Build for Startups credits covering the cloud-side engineering buildout.
KOSGEB Ar-Ge ve İnovasyon (R&D and Innovation) destek programları cover similar ground for KOSGEB-eligible Turkish SMEs — including grant and reduced-interest loan capital for R&D and innovation projects. KOSGEB programs are operationally distinct from TÜBİTAK programs but cover overlapping ground for early-stage Turkish companies that fit either eligibility framework.
The credit-application implication: Turkish founders building a financing picture in 2026 should think of the AWS credit stack as one component of a multi-source non-dilutive plus dilutive funding architecture. TÜBİTAK BiGG or 1507, KOSGEB Ar-Ge, AWS partner-filed credits, and the Turkish institutional VC round combine in ways that meaningfully reduce both the equity dilution and the cash burn relative to a purely VC-funded equivalent in the US or Western European market. The AWS partner narrative does not directly cite the TÜBİTAK or KOSGEB signals — they do not function the way an accelerator vouch or VC vouch does for AWS reviewers — but they are part of the broader credibility picture that makes the Turkish credit application read seriously.
The VC vouch — alongside the partner vouch and the accelerator vouch — is one of the three credible signals that move a Turkish application through ACE review faster. The Turkish VC ecosystem has matured substantially across 2018–2026 and several Turkish funds carry direct or indirect AWS Activate Portfolio Sub-Program access. Here are the funds AWS reviewers recognize in 2026 and the typical mechanic for each.
The pattern across these funds is similar: portfolio status is documented in the credit application, the fund name appears in the use case framing, and (for some) the partner submitting your ACE record has an existing referral relationship with the fund. The application moves faster and reviewers default to higher-confidence approvals.
212 is one of the longest-running and most visible Turkish VC funds, with a portfolio focused on Turkish, MENA, and increasingly cross-border European technology companies. 212 holds direct AWS Activate Portfolio Sub-Program access as of CloudRoute's last confirmation in Q2 2026, which means 212-backed companies can either route through 212 directly or through a partner-filed application that names 212 as the institutional sponsor.
212-backed Turkish companies clear partner-filed Portfolio at $75K–$100K consistently. The Turkish Series-A with 212 leading is among the cleanest single applications in the Turkish credit landscape — institutional funding signal is unambiguous, projected consumption at 212-stage portfolio companies is typically meaningful, and the regulatory overlay (where present) is well-articulated by 212 portfolio companies that have been through the same process before.
Earlybird Digital East is the Istanbul-focused arm of the broader Earlybird Venture Capital operation (Earlybird being a European fund with anchor offices in Munich, Berlin, and Istanbul). Earlybird Digital East invests across Turkish, Turkic-region, and broader CEE technology companies. The Earlybird Portfolio relationship with AWS coordinates through the broader Earlybird operation; Earlybird Digital East-backed Turkish companies leverage that broader relationship for partner-filed Portfolio applications.
Earlybird Digital East-backed Turkish companies clear partner-filed Portfolio at $75K–$100K with timeline that runs 2–4 days longer than equivalent 212-backed applications because the Earlybird routing involves coordination with the broader Earlybird operation. The end-state credit ceiling is comparable; the wall-clock difference is modest and not consequential for founders not in active fundraising urgency.
Diffusion Capital is one of the active Turkish early-stage VCs focused on Turkish and CEE technology companies across SaaS, fintech, and AI-applied verticals. Diffusion holds AWS Activate Portfolio Sub-Program access intermittently — CloudRoute confirms status at routing time per quarter. Diffusion-backed Turkish companies typically file partner-filed with Diffusion named as institutional sponsor when direct Diffusion routing is not in immediate capacity.
Diffusion-backed Turkish companies file at the same Portfolio ceiling ($75K–$100K) regardless of whether Diffusion is the submission channel or the named institutional sponsor on a partner-filed application. The institutional funding signal is what reviewers verify; the submission channel is operational.
Logo Ventures is the corporate VC arm of Logo Yazılım, the Turkish enterprise-software company. Logo Ventures invests in Turkish technology companies, particularly those operating in or adjacent to enterprise software and SME-focused B2B SaaS. Portfolio Sub-Program status varies by quarter; partner-filed routing with Logo Ventures named as institutional sponsor is the typical mechanic.
Logo Ventures-backed Turkish companies file at $50K–$100K Portfolio depending on funding stage and projected consumption. The Logo Yazılım parent-company association can carry secondary weight in reviewer assessment because Logo is a well-known Turkish enterprise-software entity with substantial AWS-account history of its own.
A broader set of Turkish VCs and corporate VCs with varying Portfolio Sub-Program status. Inveo invests across early-stage Turkish technology companies. Revo Capital is active in Turkish seed and Series-A rounds with a focus on B2B SaaS, marketplaces, and AI-applied verticals. Sabancı Ventures is the corporate VC arm of Sabancı Holding, one of the largest Turkish industrial groups, and invests in technology companies aligned with Sabancı's strategic interests. Türk Telekom Ventures is the corporate VC arm of Türk Telekom and invests in Turkish technology companies with telecom-adjacency or strategic relevance.
For Turkish founders, the practical heuristic: 212 and Earlybird Digital East are the most reliable named-fund signals for AWS reviewers. The others may or may not be in Portfolio Sub-Program at any given moment but consistently work as named institutional sponsors on partner-filed applications. The institutional funding signal is what reviewers verify, and the partner can verify it without the VC needing to submit directly.
Aslanoba Capital is the family office of Hakan Aslan, who built and exited Yemeksepeti (acquired by Delivery Hero for $589M in 2015 — one of the most consequential early Turkish technology exits). Aslanoba invests across Turkish technology companies, particularly at the seed and early-Series-A stage. The Aslanoba name carries operator credibility that is distinct from a pure-financial VC signal; reviewers recognize the Yemeksepeti-Aslanoba lineage.
ACT VC is one of the active Turkish funds with an early-stage focus and growing Portfolio Sub-Program engagement. ACT-backed Turkish companies file at typical seed Portfolio ranges.
Beyond the named funds, the Turkish operator-angel cohort is a meaningful second-order signal. Peak Games alums (post-Zynga acquisition), Trendyol alums (post-Alibaba investment cycle), Insider alums, Picus Security alums, Hepsiburada alums, and Getir alums have collectively become an active Turkish operator-angel network investing in next-generation Turkish startups. When a Turkish founder has a Peak Games or Trendyol co-founder, advisor, or angel investor on the cap table, that operator signal compounds the institutional VC signal in the partner narrative.
AWS partner-filed credit reviewers in 2026 know specific Turkish technology companies and the verticals they validated. The Turkish gaming and e-commerce track records over 2015–2024 reshaped how reviewers interpret the typical Turkish file — institutional credibility for the Turkish ecosystem at the credit-application desk is materially higher than for most adjacent MENA markets.
Peak Games to Zynga ($1.8B, 2020). Peak Games — Toon Blast, Toy Blast — sold to Zynga in mid-2020 in one of the largest pure-software exits in Turkish history. Peak's engineering, product, and operational alumni dispersed across the Turkish ecosystem and became one of the most consequential sources of next-generation Turkish founders. For AWS credit applications, Peak alum founders are a recognized signal — they are technically credible operators with both Turkish-market and global-scale software experience.
Trendyol valuation expansion (2018 Alibaba investment; subsequent $16.5B implied valuation peak). Trendyol's scaling from a Turkish e-commerce marketplace to a regional player with cross-border MENA and Western European operations validated the Turkish-MENA cross-border B2C marketplace pattern. Trendyol-engineering alumni have substantial AWS-scale experience and credibility at the credit-application desk; the Trendyol pattern itself (Turkish-headquartered B2C marketplace with cross-border expansion) is a pattern AWS reviewers recognize and underwrite favorably for Turkish founders building in adjacent shape.
Insider growth as a Turkish global SaaS company. Insider scaled from an Istanbul-headquartered B2B SaaS company into a recognized global player with US, MENA, and APAC customer bases. The Insider track record is the strongest single Turkish-B2B-SaaS precedent for AWS reviewers — a Turkish-headquartered company building globally-competitive B2B SaaS infrastructure on AWS at meaningful scale.
Picus Security US enterprise traction. Picus Security, founded in Turkey, built a sustained US enterprise customer base in the security-validation category. The Picus precedent demonstrates that Turkish-founded technical-depth B2B SaaS can serve global enterprise markets from a Turkish operational base; reviewers recognize the pattern.
Getir peak valuation and subsequent contraction. Getir reached a $11.8B valuation in 2021 before the well-documented contraction across 2022–2024. The Getir cycle is more complicated to reference at a credit-application desk — the precedent demonstrates Turkish-founded operational and engineering capability at meaningful scale but also illustrates the cyclical risks of high-burn consumer-marketplace business models. Reviewers do not penalize Turkish files for the Getir cycle, but they do read Turkish operational and business-model claims with appropriate calibration.
Hepsiburada Nasdaq listing (2021). Hepsiburada's Nasdaq listing in mid-2021 was the first major Turkish technology company on a US public exchange. The listing validated Turkish technology companies as candidates for US public-market access and broadened reviewer awareness of the Turkish ecosystem.
The cumulative effect: a Turkish credit application in 2026 enters reviewer evaluation with substantial precedent context. Reviewers know that Turkish-founded companies have scaled to billion-dollar gaming exits, multi-billion-dollar e-commerce valuations, US-enterprise SaaS traction, and US public-market listings. The credit decision is technical (use case, projected spend, regulatory scope) — but the implicit credibility floor for Turkish files is meaningfully higher than for most adjacent emerging-market ecosystems precisely because the precedent base is strong.
Turkish startups occupy a strategically distinctive position relative to purely MENA or purely European peers — they can credibly target customers across Turkey, the MENA region, and the European Union from a single Istanbul-anchored operational base. This dual-market positioning shapes the credit application narrative in specific ways.
The Turkish-MENA expansion case operates on several layers. Cultural and historical proximity between Turkey and the broader MENA region — particularly the Gulf and Levant — gives Turkish founders access to MENA business networks that are functionally inaccessible to European or US founders. Turkish gaming, Turkish e-commerce, Turkish fintech, and Turkish B2B SaaS have demonstrated repeatable patterns of Istanbul-headquartered companies serving Saudi, UAE, Kuwaiti, and Egyptian customer bases without requiring an in-region acquisition. For AWS architecture, this translates to coordinated eu-central-1 + me-central-1 deployments where the Turkish team operates the underlying platform from eu-central-1 and the MENA customer base accesses from me-central-1 with appropriate replication and data-locality considerations.
The Turkish-EU expansion case operates differently. Turkey is not an EU member state but holds Customs Union status and has substantial economic and regulatory adjacency to the EU. Turkish technology companies serving European customers — particularly European mid-market B2B SaaS — operate under KVKK domestically and GDPR for their European customer base. The AWS architecture answer is typically eu-central-1 primary with KVKK + GDPR cross-mapping controls; eu-south-1 secondary for Italian or Mediterranean customer concentration; and a defined data-residency-and-classification posture that distinguishes which records fall under which regime.
The credit application narrative benefits from articulating this dual-market positioning explicitly. A Turkish Series-A B2B SaaS company building for the Turkish, MENA, and European mid-market should articulate the eu-central-1 + me-central-1 + (selective) eu-south-1 region pattern, the KVKK + GDPR + (where applicable) BDDK regulatory posture, and the multilingual product surface (Turkish primary, Arabic and English secondary). Portfolio funds the underlying SaaS infrastructure broadly. Build for Startups funds the regulatory engineering build (KVKK + GDPR cross-mapping, or BDDK Open Banking, depending on scope). Bedrock POC funds the multilingual generative-AI workload — Turkish-language primary inference with Arabic-language secondary deployment for the Gulf customer base and English-language secondary deployment for European mid-market customers.
The stack reads well precisely because it is genuinely use-case-specific. Turkish founders who attempt to file a generic "we sell B2B SaaS" application without articulating the cross-border positioning land at the lower end of Portfolio ranges ($50K–$75K). Turkish founders who articulate the Turkish-MENA-EU positioning with specific reference to the projected workloads, the multilingual product surface, the regulatory cross-mapping, and the region selection rationale routinely land at $100K Portfolio with Build for Startups and Bedrock POC stacking cleanly on top.
The Turkish tech ecosystem concentrates in three primary urban centers — Istanbul, Ankara, and Izmir — with secondary clusters in Antalya, Bursa, and around major Turkish university teknokent zones. AWS partner availability, accelerator presence, and regional infrastructure access vary modestly across the geography.
Istanbul is the dominant Turkish technology center by every relevant metric — startup density, VC office presence, accelerator activity, and total venture funding deployed. The Kadıköy and Beşiktaş corridors host the highest concentration of founder offices and growth-stage company headquarters; the European-side Levent and Maslak business districts host the Turkish offices of major international technology companies and the headquarters of several Turkish corporate VCs (Sabancı Ventures, Türk Telekom Ventures, Logo Ventures); ITÜ Ayazağa campus hosts ITÜ Çekirdek; Koç University on the European side hosts Kworks. The strong majority of Turkish AWS credit applications CloudRoute routes are Istanbul-headquartered companies.
Ankara is the secondary Turkish technology center, anchored by ODTÜ Teknokent (the Middle East Technical University Technology Development Zone) and Bilkent CYBERPARK. The Ankara ecosystem skews toward technical-depth verticals — defense technology, deep tech, advanced engineering, and government-adjacent technology. ODTÜ-affiliated Turkish startups have substantial technical credibility at the credit-application desk; the ODTÜ Teknokent name is recognized by AWS reviewers as an indicator of engineering depth.
Izmir hosts a third concentration anchored by IZTECH (Izmir Institute of Technology) and the Aegean region's university teknokent activity. The Izmir ecosystem skews toward maritime technology, agritech for the Aegean and Mediterranean agricultural sector, and increasingly broader B2B SaaS as the regional ecosystem matures. Antalya and Bursa host smaller technology clusters with specific verticals (Antalya: tourism technology and consumer-internet adjacency; Bursa: industrial automation and manufacturing technology with proximity to the Turkish automotive sector).
For credit application purposes, founder city does not affect the application ceiling or the timeline. What affects routing is the partner geography — CloudRoute routes Turkish inquiries preferentially to Istanbul-based partners, with Ankara-based partners as the secondary option for ODTÜ-affiliated or government-adjacent files, and Dubai-based partners as the cross-border backup. The discovery call timezone aligns naturally with Turkish working hours regardless of partner geography because Istanbul and Dubai operate within a one-hour offset that has no practical scheduling impact.
| Track | Typical Turkey award | Filed by | Time-to-balance | Turkey-specific gate |
|---|---|---|---|---|
| Activate Builders (self-serve) | $1K | You | 24 hours | None — universal |
| Activate Founders (self-serve) | $5K | You | 3–7 days | None — universal |
| Activate Founders — partner-filed | $15K–$25K | Partner via ACE | 10–14 days | Accelerator vouch helps (ITÜ Çekirdek / ODTÜ Teknokent / Kworks) |
| Activate Portfolio (partner-filed) | $50K–$100K | Partner via ACE | 11–18 days | Institutional funding required (212 / Earlybird DE / Diffusion / Sabancı) |
| Build for Startups — KVKK work | +$25K | Partner via ACE | 14–21 days | KVKK Law 6698 compliance build scope; consent + cross-border |
| Build for Startups — BDDK Open Banking | +$25K | Partner via ACE | 14–21 days | BDDK-licensed payment service provider; Open Banking technical scope |
| Build for Startups — SPK work | +$25K | Partner via ACE | 14–21 days | SPK-supervised entity; capital-markets infrastructure scope |
| Bedrock POC — Turkish + Arabic NLP | +$10K–$50K | Partner via ACE | 14–28 days | Multilingual Turkish + Arabic inference workload; defined POC plan |
AWS credits are denominated in USD; the AWS invoice is denominated in USD; Turkish customers pay AWS in USD via the standard banking flow. For Turkish founders budgeting in TRY — which is most Turkish founders, because the local-VC seed round was raised in TRY and the operational burn is denominated in TRY — the currency translation matters substantially because the Turkish lira has been through structural devaluation.
The Turkish lira moved from approximately TRY 8.5/USD in early 2021 to approximately TRY 13/USD by late 2021, to approximately TRY 19/USD by late 2022, to approximately TRY 30/USD by late 2023, to a TRY 32–40/USD range across 2024 through mid-2026 with intermittent volatility into the upper end of that band during stress periods. The cumulative move 2021 → 2026 is approximately 4–5x — comparable in magnitude to the Egyptian devaluation but distributed across a longer period with more intermediate volatility.
For a Turkish founder budgeting in TRY, this matters in two distinct ways. First, USD-denominated AWS credits have effectively appreciated 4–5x against TRY-denominated cost expectations since early 2021. A $50K AWS credit pool today corresponds to approximately TRY 1.75M at the TRY 35/USD reference rate; the same $50K credit pool at the early-2021 reference rate would have corresponded to approximately TRY 425K. The same headline USD figure carries materially more TRY-equivalent runway than it did five years ago.
Second, AWS credits act as a hedge against further TRY depreciation. AWS bills are USD-denominated. Without credits, a Turkish startup's AWS bill compounds with currency movement — a TRY devaluation event makes the AWS bill more expensive in TRY terms even if the underlying AWS consumption is constant. Credits insulate the burn from that currency shock for the duration of the credit pool. A 36-month credit pool (24 months Portfolio + 12 months Build for Startups + 12 months Bedrock POC, all running concurrently in the validity window) covers a meaningful chunk of a Turkish startup's runway and removes the AWS-currency-risk variable from the burn equation for the duration.
A typical Turkish engagement aligns to the global partner-filed timeline, with one consistent regional variance: the discovery call often runs in English with the technical partner and the founder's CTO, with the option to coordinate a separate Turkish-language session with the founder's legal or compliance counsel for KVKK or BDDK scope files where Turkish-language regulatory documentation is in scope.
Day 0 — Inquiry submitted to CloudRoute. Three questions: company name, funding stage, AWS use case (one sentence). Turkey-specific: noting whether KVKK, BDDK, or SPK scope applies routes the inquiry to a partner with regional regulatory experience. Noting accelerator status (ITÜ Çekirdek cohort year, ODTÜ Teknokent affiliation, Kworks) and Turkish VC backing (212, Earlybird Digital East, Diffusion, etc.) routes preferentially to partners with documented track records for that signal.
Day 1 — Self-serve Activate Founders application ($5K). 3 minutes at aws.amazon.com/startups/credits/. Lands in 24–72 hours; covers bridge spend during the partner-filed window.
Day 1 — CloudRoute routes to a matched partner. For Turkish inquiries the partner is typically headquartered in Istanbul, Ankara, or Dubai with documented Turkish partner-filed credit experience and (for regulatory files) explicit KVKK, BDDK Open Banking, or SPK implementation track record. Calendar link issued.
Day 2–4 — Discovery call (30 minutes for non-regulated SaaS; 45–60 minutes for BDDK or SPK-scope fintech). Partner confirms eligibility, walks through the application framing, identifies whether to file Portfolio standalone or stack Build for Startups + Bedrock POC. For Turkish-preferring founders, a follow-on session can run in Turkish with the founder's legal or compliance counsel for KVKK or BDDK scope.
Day 5–7 — You provide application inputs: company info, deck (8–10 slides), AWS account ID (or "I'll create one"), use case paragraph, projected AWS spend by service, accelerator confirmation, VC confirmation. Partner builds the ACE record and submits.
Day 8–14 — AWS reviewer queue assigns the record. Partner-tier, accelerator, and VC vouches accelerate this. For applications going through partners with > 70% ACE close rate, partner-filed Founders approval typically lands within this window.
Day 12–18 (Portfolio) — Portfolio approval lands. $50K–$100K visible in AWS billing console.
Day 14–21 (Build for Startups, Bedrock POC) — Stacking applications land. Build for Startups for KVKK, BDDK Open Banking, or SPK work; Bedrock POC for Turkish + Arabic inference. Each adds $15K–$50K to the visible balance.
Total founder time: ~45 minutes (no regulatory overlay) or ~90 minutes (with BDDK Open Banking scope including counsel coordination). Total wall-clock: 12–21 days. Total cost: $0.
BDDK Open Banking files where the compliance counsel needs to sign off on the Build for Startups scope can extend the timeline by 3–7 days; the BDDK technical-implementation scope is genuinely substantive and the counsel review is appropriate. SPK-scope files for crowdfunding or capital-markets-adjacent platforms can extend further (SPK technical-implementation scoping is generally less standardized than BDDK Open Banking and individual application review tends to take longer). KVKK files for sensitive personal data with cross-border transfer authorization documentation tend to run within the standard timeline because the AWS-architecture work does not block on KVKK Kurumu sign-off — the architecture posture is designed for KVKK authorization, but the application itself moves before the authorization completes. Plain SaaS files with no regulatory overlay consistently run within the standard 12–18 day window.
The biggest predictors of total credit award for a Turkish application are the combination of funding stage, accelerator and VC vouches, regulatory scope, and multilingual product surface. This matters more than founder city within Turkey.
| Variable | Turkish pre-seed (bootstrapped or BiGG) | Turkish seed (ITÜ Çekirdek / 212 angel / Earlybird DE) | Turkish Series-A (212 / Earlybird DE / Diffusion / Sabancı) |
|---|---|---|---|
| Typical credit pool | $25K–$40K | $50K–$75K | $100K–$150K |
| Portfolio approval likelihood | Low (no institutional signal) | Moderate-to-High (depends on funding & spend) | High |
| Build for Startups stack? | Rarely (no discrete workload) | Sometimes (KVKK or migration scope) | Usually (KVKK + GDPR cross-mapping, BDDK, or SPK) |
| Bedrock POC fit? | Yes, if Turkish-language AI use case | Often (Turkish + early Arabic deployment) | Often (multilingual Turkish + Arabic + English) |
| Region selection | eu-central-1 default | eu-central-1 default | eu-central-1 + me-central-1 (Gulf) + (selective) eu-south-1 |
| Application length | 10–14 days | 12–18 days | 14–21 days (compliance review) |
| Founder time | ~30 min | ~45 min | ~90 min (incl. compliance counsel) |
| Cost to founder | $0 | $0 | $0 |
Situation: Building a B2B payments platform for Turkish SMEs with a cross-border MENA expansion thesis — Turkish SME accounts payable automation as the primary product, with a planned Saudi and UAE deployment within twelve months. Founding team: ex-Trendyol engineering lead (CTO) and ex-Insider product lead (CEO). BDDK licensing application in progress as a licensed payment service provider; BDDK Open Banking technical implementation in scope as a discrete engineering project. Existing AWS infrastructure was a single-account eu-central-1 setup built by the CTO before BDDK considerations were specified. KVKK applicability for Turkish customer data plus GDPR for the European-team employee data; planned multilingual product surface with Turkish primary, Arabic secondary for Saudi and UAE launch, English secondary for European mid-market pilots. Projected AWS spend $11K/month within twelve months across eu-central-1 (Turkish customers) and me-central-1 (Gulf customers).
What CloudRoute did: Routed within 19 hours to an Istanbul-headquartered AWS partner with documented BDDK Open Banking implementation track record (4 prior Turkish fintech engagements). Discovery call ran 55 minutes including the founder's external regulatory counsel for BDDK scope confirmation. Partner filed Portfolio ($100K) on day 5 to cover general SaaS infrastructure across eu-central-1 + me-central-1, named 212 as institutional sponsor with Earlybird Digital East and Aslanoba documented as co-investors. Filed Build for Startups ($25K) on day 6 specifically scoped to the BDDK Open Banking technical build — API Gateway with mutual-TLS, dedicated tenant isolation, comprehensive CloudTrail + Config + Security Hub for BDDK audit alignment, KMS with customer-managed keys, incident response runbook. Filed Bedrock POC ($25K) on day 7 scoped to multilingual KYC document analysis — Turkish primary using Claude Sonnet, Arabic secondary using Claude Sonnet for the Gulf deployment, English secondary using Claude Sonnet for European mid-market pilots — with defined held-out test set, evaluation methodology, and monthly inference budget articulation.
Outcome: Total credits approved by day 18: $150K (≈ TRY 5.25M at TRY 35/USD reference rate). Portfolio approved at $100K (clean institutional funding signal, meaningful projected consumption, multi-region architecture). Build for Startups approved at $25K (BDDK Open Banking scope was specific and the partner narrative articulated the discrete engineering workload cleanly). Bedrock POC approved at $25K (multilingual scope and the explicit Turkish + Arabic + English deployment plan landed favorably). BDDK Open Banking compliance build delivered over 8 weeks; cumulative AWS spend across the credit-pool engagement: $6.8K (fully credit-funded). BDDK licensing application accepted on the resulting AWS architecture without architectural remediation. CloudRoute's commission paid by the partner from AWS engagement funding. Customer cost: $0.
engagement window: 18 days · founder time: ~6 hours · credits secured: $150K · cost to customer: $0
CloudRoute routes within 24 hours to a partner with documented Turkish partner-filed credit experience. Customer pays $0. Credits land in 12–21 days. Turkish-speaking solutions architects available for KVKK, BDDK, or SPK scope discovery calls.