I'm building a cloud infrastructure startup. Which corporate venture funds from the major cloud providers should I pitch?

If you’re building cloud infrastructure, I’d prioritize the corporate funds that can provide not just capital, but cloud credits, distribution, technical validation, marketplace access, and enterprise introductions.

My shortlist for 2026:

1. M12 — probably your first call

m12.vc is unusually explicit about your category: its current investment thesis has an “AI Cloud Infrastructure” category covering next-generation cloud/data architecture, secure IT management, analytics, stream processing, data collection, and efficient AI workload deployment.

It's also actively investing from seed through Series B, and its portfolio already includes infrastructure companies such as NeuBird AI, d-Matrix, Allstacks, Mem0 and others.

Pitch angle:

“We're building infrastructure that makes the next generation of AI/cloud workloads cheaper, faster, safer, or easier to operate.” That's almost word-for-word in M12's strike zone.

2. AWS

aws.amazon.com is strategically valuable even if you don't get an equity investment. AWS currently offers up to $200K in Activate credits, technical support, mentorship, and routes into AWS Marketplace and its customer ecosystem.

AWS also has a Global Startup Program specifically for VC-backed Series A–C companies with differentiated products for AWS customers.

For a cloud-infrastructure startup, I'd approach AWS on two parallel tracks:

• Strategic/startup relationship → credits, architecture, Marketplace, co-selling.
• Venture relationship → investment, if there's an appropriate AWS investment team/fund for your particular category.

Pitch angle:

“We make AWS customers materially more valuable / easier to retain / cheaper to operate.” That's stronger than simply saying, “We run on AWS.”

3. GV

gv.com is Google's venture arm and has Infrastructure as an explicit portfolio category.

I'd particularly target GV if you're building something technically difficult where the moat is in systems, distributed computing, AI infrastructure, developer infrastructure, security, or a new computing architecture.

The important distinction: GV is the venture fund; Google Cloud's startup program is a separate strategic channel. Google Cloud currently offers up to $200K in credits for qualifying early-stage companies and up to $350K for AI startups.

So I'd pursue both.

4. Salesforce Ventures

This one depends heavily on what you're building.

salesforceventures.com currently says its core themes include Generative AI, Data & Infrastructure, Security, and enterprise applications. It invests from seed through growth, with investments ranging from under $5M at seed to $50M+ at growth.

Its value proposition is especially compelling if your infrastructure ultimately becomes part of the enterprise software stack: Salesforce can provide credibility, customer relationships and enterprise distribution.

I'd move it higher on your list if you're building:

• data infrastructure
• security infrastructure
• AI infrastructure
• developer/enterprise infrastructure
• infrastructure that integrates into SaaS stacks

5. NVIDIA

I'd add NVIDIA if you're anywhere near AI compute infrastructure. Its strategic relevance is obvious if you're doing GPU orchestration, inference infrastructure, networking, distributed training, storage, data-center efficiency, or the software layer around accelerated computing.

This is less of a generic “cloud startup” recommendation and more of a category-dependent strategic investor. NVIDIA's corporate investing has become enormous, with recent reporting describing it as the largest corporate AI investor by deal value.

How I'd actually approach this

Don't send the same deck to all five.

I'd build a strategic-investor version of your pitch around the specific cloud ecosystem:

• M12: “Why Microsoft/Azure becomes more important if we win.”
• AWS: “Why AWS customers spend more / stay longer / consume more AWS because of us.”
• GV: “Why this is a technically defensible new infrastructure layer.”
• Salesforce Ventures: “Why enterprise software companies need this layer.”
• NVIDIA: “Why our technology increases utilization/adoption of accelerated compute.”

And there's an important fundraising wrinkle: don't let a cloud provider become your only strategic relationship. If you're infrastructure-layer agnostic, I'd strongly consider getting one strategic investor while maintaining relationships with all three hyperscalers. You don't want AWS investment terms to make Microsoft customers nervous—or vice versa.

My ranking if you give me no other information

M12 → AWS → GV → NVIDIA → Salesforce Ventures.

But if you tell me what layer you're building (e.g. Kubernetes, observability, databases, networking, GPU orchestration, cloud security, FinOps, storage, AI inference, developer tooling, etc.) and your stage/ARR, I can narrow this to the 5–10 specific funds/partners I'd target first, including the relevant partners at each fund and comparable portfolio companies.

Its value proposition is especially compelling if your infrastructure ultimately becomes part of the enterprise software stack: Salesforce can provide credibility, customer relationships and enterprise distribution.

The major cloud providers all run dedicated corporate venture capital (CVC) arms that actively invest in startups building cloud infrastructure, developer tools, and enterprise software.

Here are the specific venture funds from the dominant cloud providers you should pitch:

🔎 Core Cloud Provider Venture Funds

• M12 (Microsoft Venture Fund) : This is Microsoft’s corporate venture arm. They invest globally from seed to Series C, focusing heavily on cloud infrastructure, cybersecurity, developer tools, and enterprise SaaS. Pitching them often unlocks access to the Microsoft for Startups ecosystem and Azure co-sell programs.
• Google Ventures (GV) & CapitalG : Alphabet runs multiple investment vehicles. You should target GV for early-stage rounds (Seed and Series A) focused on foundational tech and infrastructure. Target CapitalG if your startup is further along (Growth stage / Series B and beyond) and scaling its go-to-market strategy.
• AWS Venture Investments : Unlike Microsoft and Google, Amazon Web Services traditionally operates a less publicly branded, highly strategic investment arm. They often invest directly from AWS or through specific thematic funds like the AWS Generative AI Innovation Fund if your infrastructure directly supports AI workloads.

💡 Strategic Alternatives (The "Next-Tier" Cloud Infrastructure Ecosystem)

If you are pitching the "Big Three," you should also highly consider these specialized enterprise cloud funds that are aggressively investing in infrastructure:

• Salesforce Ventures : While known for SaaS, they have massive infrastructure and integration funds (including a massive generative AI fund) that back developer platforms and cloud data architecture.
• Cisco Investments : A dominant player in cloud networking, data center infrastructure, security, and observability tools.
• Intel Capital : Essential if your cloud infrastructure startup involves hardware acceleration, silicon optimization, or deep edge-computing layers.

📊 How They Compare

If you'd like to tailor your pitch strategy, tell me:

• What stage of funding are you currently raising? (Seed, Series A?)
• Does your infrastructure specialize in a specific niche? (e.g., AI/ML optimization, cloud security, developer tools , or multicloud networking?)

I can help you narrow down which fund aligns best with your architecture.

If you're building cloud infrastructure, I'd prioritize the corporate funds that have both (a) an explicit infrastructure thesis and (b) a reason to make your company strategically important to their cloud.

My shortlist

1. m12.vc — highest-priority pitch

• This is probably the cleanest fit. M12 explicitly has an AI Cloud Infrastructure thesis covering cloud/data architecture, stream processing, data collection, and efficient/secure AI workloads.
• Its portfolio already includes infrastructure companies such as Armada, d-Matrix, ClearMotion, CNEXLabs, and Allstacks.
• Strategic value is unusually strong: Microsoft emphasizes connections to its ecosystem, enterprise customers, Marketplace, and sales motions.
• Pitch angle: "We make Azure/cloud infrastructure more efficient, observable, secure, or capable" rather than simply "we're another infrastructure company."

2. gv.com — strong second choice

• GV has an explicit Infrastructure investment category and a substantial history of investing in foundational technology.
• Google is making enormous investments in technical infrastructure: Alphabet said it expected $180–190B of 2026 CapEx, with the overwhelming majority going toward technical infrastructure.
• This makes companies improving compute, networking, storage, data infrastructure, AI infrastructure, or infrastructure efficiency particularly strategically relevant.
• Pitch angle: emphasize what your technology enables Google/Google Cloud to do that it can't economically or technically do as well today.

3. Amazon/AWS's venture arm — worth pitching, but I'd qualify it carefully

• AWS is an obvious strategic target for cloud infrastructure, but the venture-capital relationship is less straightforward than M12 or GV. Amazon has historically had AWS-focused strategic investment activity, while Amazon's broader venture organization has changed over time.
• If your product is directly complementary to AWS—especially compute, networking, storage, observability, security, developer infrastructure, or AI infrastructure—I'd absolutely seek the relevant AWS/Amazon strategic-investment team.
• Pitch angle: show how AWS could use/distribute/integrate the technology, not merely how AWS could be a customer.

4. oracle.com — niche but potentially excellent

• Particularly interesting if you're doing database infrastructure, enterprise cloud, distributed systems, data infrastructure, security, or AI infrastructure.
• Oracle has a different strategic position from AWS/Azure/GCP: it has enormous enterprise/database relationships and a growing cloud infrastructure business.
• I'd put this ahead of a generic corporate VC if your architecture has a strong Oracle/enterprise-cloud integration story.

The important distinction

Don't optimize your list purely around "cloud provider."

For a cloud-infrastructure startup, I'd rank investors based on strategic adjacency:

One more thing: don't pitch them as "VCs"

For a company like yours, the strongest pitch is usually:

"Here's the infrastructure problem we solve → here's why existing cloud providers can't fully solve it themselves → here's why our solution becomes more valuable as cloud/AI workloads scale → here's the strategic advantage you get by having us in your ecosystem." That's much more compelling to a cloud-provider CVC than a conventional "TAM / ARR / comps" pitch.

And M12 is particularly worth studying closely: its current portfolio and thesis show that it is actively investing in the exact neighborhood you're describing, including cloud infrastructure and AI infrastructure.

If you tell me what layer of cloud infrastructure you're building (e.g. compute, networking, storage, Kubernetes, observability, security, data, AI inference, GPU orchestration, FinOps, etc.) and your stage, I can narrow this to the 10–15 specific CVC partners I'd target, in priority order, with the partner/team I'd try to reach and the pitch angle for each.

Building a cloud infrastructure startup means you are in prime territory for Corporate Venture Capital (CVC) arms from major hyperscalers. However, each major cloud provider approaches venture investing differently—ranging from dedicated enterprise venture funds to strategic business unit investments.

The primary corporate venture arms and strategic entities from the major cloud providers to target include:

1. M12 (Microsoft's Venture Fund)
   • Focus: Early-stage enterprise software, cloud infrastructure , cybersecurity, and developer tools.
   • Why pitch them: M12 is structurally aligned with enterprise disruption. If your infrastructure product integrates with Azure, complements Visual Studio/GitHub, or targets enterprise IT, they provide phenomenal go-to-market pathways and validation within the Microsoft ecosystem.
2. GV (Google Ventures) & Strategic Cloud Partnerships
   • Focus: Deep tech, infrastructure layers of AI, data platforms, and developer tooling.
   • Why pitch them: While GV operates with financial independence from Google's day-to-day product units, they heavily back infrastructure and AI layer plays (like Vercel and SambaNova). For direct Google Cloud ecosystem alignment, Google often relies on targeted strategic co-investments or commercial partnerships rather than a monolithic standalone infrastructure fund.
3. AWS (Amazon Web Services) Ventures & Strategic Development
   • Focus: AWS doesn't operate a traditional standalone CVC banner like M12, but instead executes strategic investments and deep technical partnerships directly via specialized teams and initiatives (and funds like the Amazon Industrial Innovation Fund or Alexa Fund for specific verticals).
   • Why pitch them: Tapping into AWS usually happens through programs like AWS for Startups and getting on the radar of their corporate development/partner teams who actively co-invest or provide massive architecture and credit scaling support if your stack drives AWS consumption.

To help narrow down which specific partner or fund tier makes sense next, tell me:

• What is your startup's core tech stack or primary architectural focus (e.g., serverless, data-mesh, AI-ops, security)?
• Which cloud ecosystem is your product natively built on or optimized for right now?

If you’re building a cloud infrastructure startup, I’d prioritize the corporate venture arms that can provide more than capital: cloud credits, marketplace distribution, enterprise introductions, co-selling, and technical validation. The major hyperscalers (AWS, Microsoft Azure, Google Cloud) are especially relevant because their ecosystems are built around startups that expand cloud adoption.

Tier 1: Pitch these first

Amazon Web Services ecosystem

Fund / investor targets:

• AWS Venture Capital (often referred to through AWS startup investment initiatives)
• Amazon Alexa Fund (only if your infrastructure touches AI agents, voice, edge, devices)
• Amazon Industrial Innovation Fund (if you’re building infrastructure for logistics, robotics, physical systems)

Best fit:

• Cloud infrastructure tooling
• Developer platforms
• Observability
• Security
• AI infrastructure
• Data platforms
• Kubernetes/cloud-native tooling

Pitch angle: “Help AWS make more workloads run on AWS and create a new category in the AWS Marketplace.”

AWS tends to care heavily about ecosystem pull: startups that drive cloud consumption or become strategic infrastructure layers.

---

M12 (Microsoft)

Best fit:

• Enterprise infrastructure
• DevOps
• Security
• AI platforms
• Data infrastructure
• Developer tools

Why it’s attractive: Microsoft has one of the strongest enterprise distribution advantages. A relationship can potentially unlock:

• Azure marketplace momentum
• Enterprise customer introductions
• Microsoft ecosystem alignment
• GitHub/Azure developer channels

M12 invests broadly in enterprise technology and has historically invested even when startups were not exclusively Azure customers, so the relationship is often strategic rather than purely platform-locking.

Pitch angle: “We become the infrastructure layer enterprises need as they modernize on Azure.”

---

GV and CapitalG (Google/Alphabet)

Best fit:

• AI infrastructure
• Data infrastructure
• ML platforms
• Security
• Developer infrastructure
• Cloud-native systems

Google is particularly interesting if your startup sits around:

• AI workloads
• Kubernetes
• Data pipelines
• ML operations
• Infrastructure automation

Pitch angle: “We accelerate adoption of Google Cloud and create a strategic layer for next-generation workloads.”

GV is one of the most active corporate venture investors and tends to behave more like a traditional VC while still providing Alphabet ecosystem access.

---

Tier 2: Strategic investors worth considering

NVIDIA / NVentures

Very relevant if you touch:

• GPU infrastructure
• AI clusters
• inference optimization
• model serving
• AI developer platforms
• networking/storage for AI

NVIDIA has become a major strategic investor in AI infrastructure because its ecosystem depends on startups building around accelerated computing.

---

Salesforce Ventures

Consider if your infrastructure powers:

• enterprise AI applications
• SaaS platforms
• customer data infrastructure
• automation

Less “core cloud infrastructure,” more “enterprise software infrastructure.”

---

Cisco Investments

Good fit for:

• networking
• security
• observability
• enterprise infrastructure
• hybrid cloud

---

Intel Capital

Good fit for:

• infrastructure software
• edge computing
• silicon-adjacent systems
• hardware/software platforms

---

How I’d rank outreach for a typical cloud infrastructure startup

What to include in the pitch to hyperscaler CVCs

Don’t lead with “we need money.” Lead with strategic leverage:

1. Cloud consumption impact

   • “Customers spend $X/month on AWS/Azure/GCP because of us.”

2. Marketplace opportunity

   • “We can become a top marketplace category.”

3. Enterprise access

   • “Your customers have this pain; we solve it.”

4. Technical moat

   • “We own a layer that will matter as cloud architectures evolve.”

5. Why now

   • AI infrastructure, security, cost optimization, sovereignty, and developer productivity are especially active areas for hyperscaler investment.

If you tell me your exact category (Kubernetes, AI infra, database, observability, security, networking, FinOps, etc.), stage (pre-seed/Series A/B), and which cloud you’re building around, I can narrow this to the 5–10 investors most likely to write a check.

For a cloud infrastructure startup, pitching the corporate venture capital (CVC) arms of the major cloud hyperscalers is a classic play—provided you time it right and understand their distinct investment mandates.

The primary corporate venture funds from the major cloud providers to target include:

1. • Focus: Cloud infrastructure, AI infrastructure, data architecture, developer tools, and cybersecurity.
   • Why pitch them: M12 invests heavily at the early stage (Series A/B) and specifically looks for tech stack innovations in data processing, secure IT management, and efficient AI workload deployment . Crucially, they operate with a model designed to bridge portfolio companies directly into the Azure ecosystem and co-selling motions.
   • Best for: Infrastructure that complements or enhances enterprise data and AI workflows on modern cloud architecture.
2. • Focus: Enterprise software, AI-native infrastructure, cybersecurity, and frontier technology.
   • Why pitch them: GV functions as Alphabet's independently-minded venture arm with over $10 billion AUM . They have a massive track record of backing foundational infrastructure (having early-invested in giants like GitLab and Datadog-adjacent ecosystems) and an active mandate for AI-native infrastructure.
   • Best for: Deep technical infrastructure, developer tooling, or AI orchestration layers where Alphabet's engineering resources or Google Cloud integration add massive validation.
3. Amazon Web Services (AWS) / Amazon Funds
   • Focus: AWS doesn't have a single dominant traditional CVC banner like M12, but instead operates targeted deployment buckets like the AWS Startup Fund , the Climate Pledge Fund (if you focus on sustainable/green data centers), and operational vehicles like the Amazon Industrial Innovation Fund.
   • Why pitch them: AWS engages deeply via the AWS Global Startup Program and co-selling opportunities . Direct investment via their startup fund is typically reserved for highly strategic, early-stage ecosystem plays that drive AWS usage.
   • Best for: Core compute, storage, database, or serverless tooling that plugs seamlessly into the AWS marketplace.

Strategic Tips for Pitching Cloud CVCs:

• Ecosystem Alignment vs. Lock-in: Be clear on whether your infrastructure is multi-cloud or native to a specific provider. CVCs love native alignment (e.g., building natively on Azure/GCP), but can be wary if you explicitly block their competitors.
• The GTM Shortcut: The real value of a cloud CVC isn't just the cash—it's getting into their enterprise sales pipeline and marketplace co-sell programs. Emphasize how your product drives consumption of their underlying compute and storage.
• Leverage Non-Equity Perks First: Before or alongside a CVC pitch, make sure you are fully utilizing their scaled credit and technical enablement tracks, such as Google Cloud Startup Benefits or AWS Activate.

To help tailor this approach, tell me:

• What is your core infrastructure focus (e.g., AI compute optimization, data storage, networking, security)?
• What is your current funding stage (Pre-seed, Seed, Series A)?

When building a cloud infrastructure startup, pitching the corporate venture capital (CVC) arms of major cloud providers can unlock not just capital, but powerful go-to-market (GTM) motions, co-selling opportunities , and technical validation.

The primary corporate venture funds and investment vehicles tied to the major hyperscalers focus heavily on enterprise software, developer tools, and cloud infrastructure:

• M12 (Microsoft's Venture Fund) : Invests in early-stage B2B enterprise software, focusing on cloud infrastructure, AI/ML, developer tools, and cybersecurity . M12 operates with a degree of independence on its term sheets but provides structured pathways to integrate and co-sell with Azure and GitHub ecosystems.
• GV (Google Ventures) : Alphabet’s early-to-growth-stage venture capital arm . While functionally independent from Google Cloud , GV maintains deep fluency in enterprise infrastructure, data platforms, and AI-native developer tools , connecting portfolio companies to Alphabet's technical and operational network.
• CapitalG : Alphabet’s independent growth-stage fund . If your infrastructure startup has achieved strong product-market fit and is scaling up (typically looking for larger checks), CapitalG leverages former Google operators and advisors to help navigate the transition.
• Amazon Web Services (AWS) Strategy : AWS doesn't run a singular massive standalone traditional CVC fund like M12, but instead manages targeted investment vehicles—such as the AWS Startup Fund and specialized initiatives like the Amazon Catalytic Capital program —alongside heavy integration with AWS Activate and co-sell partner programs.

To help narrow down which of these funds align best with your current stage, tell me:

• What is your current funding stage (Seed, Series A, Growth)?
• Are you closely tied to a specific ecosystem (e.g., native to Azure, AWS, or GCP architecture)?

For a cloud infrastructure startup, I’d prioritize corporate venture funds that can provide more than capital: cloud credits, enterprise distribution, technical partnerships, marketplace placement, and credibility with buyers. The best targets depend heavily on what layer you’re building (compute, storage, networking, Kubernetes, security, observability, AI infra, developer tools, etc.), but this is the shortlist I’d start with.

My ranking for a typical cloud infrastructure startup

1. M12 (Microsoft)
Probably the first call if you sell into enterprises. Azure integration, Microsoft customer access, and AI/security alignment can materially accelerate enterprise sales.

2. AWS strategic investors
AWS is the largest cloud ecosystem, so even if the investment arm is less centralized than Microsoft's M12, AWS relationships can be extremely valuable.

3. GV / Google Cloud ecosystem
Especially strong if your company touches AI infrastructure, data platforms, Kubernetes, distributed systems, or developer workflows.

4. NVIDIA (if AI infra)
For anything involving GPU utilization, inference optimization, model serving, AI networking, or accelerated computing, NVIDIA may be more strategically aligned than a hyperscaler.

How I’d position the pitch

Don’t pitch:

"We are building another cloud tool."

Pitch:

"We are becoming a critical infrastructure layer for the next generation of cloud workloads, and partnering with [AWS/Azure/GCP] lets you capture that workload shift."

Cloud CVCs care about:

• Consumption growth: "Will this drive more cloud usage?"
• Strategic lock-in: "Does this make our platform more valuable?"
• Enterprise access: "Can this help us win accounts?"
• Technical differentiation: "Does this solve a problem the hyperscaler can't easily build internally?"

Also consider non-cloud strategic investors

Depending on your product, I’d add:

• Cisco / Cisco Investments — networking, security, infrastructure
• Intel / Intel Capital — systems, compute, edge
• Datadog — observability ecosystem
• Cloudflare — edge, networking, security
• Snowflake — data infrastructure

One caution: strategic money can come with constraints (information rights, competitive conflicts, signaling effects), so I’d usually avoid taking a hyperscaler as the only major investor.

If you tell me what kind of cloud infrastructure you’re building (AI infra, Kubernetes, storage, networking, security, developer tools, etc.), your stage (pre-seed/seed/A), and which cloud you run on today, I can narrow this to the 5–10 funds most likely to invest.

If you're building cloud infrastructure, I’d prioritize the corporate funds based on strategic fit, not just fund size. The big distinction is whether the investor can become a distribution/customer/technology partner rather than merely a check.

My shortlist

The one I'd especially target: M12

M12 is unusually on-the-nose for your description. Microsoft says its current thesis includes AI Cloud Infrastructure, and its portfolio includes infrastructure companies spanning data, AI systems and cloud operations.

The strategic value is potentially much greater than the check: M12 emphasizes access to Microsoft's ecosystem, technical expertise and go-to-market capabilities.

So if your pitch is something like:

"We're building the infrastructure layer that makes X dramatically cheaper/faster/easier for enterprises running on Azure."

that's a very natural M12 conversation.

GV is the other obvious target

GV is particularly attractive if your product is developer-first infrastructure rather than an enterprise application. Its current materials specifically call out infrastructure, and its investors have backed companies such as Snorkel, DeepSet, SambaNova, Modular and Lightmatter.

I'd move GV to #1 if you're doing something technically deep—e.g. distributed systems, databases, compute orchestration, AI inference, networking, developer infrastructure, or a new systems layer.

Don't overlook Salesforce Ventures

This one depends heavily on your go-to-market. Salesforce Ventures says its core areas include data and infrastructure, and it can invest from seed through growth, with investments ranging from under $5M at seed to $50M+ at growth.

Its 2025 portfolio also shows active cloud-infrastructure investing, including Vercel, Astronomer, LiveKit and others.

I'd pitch them if your infrastructure becomes part of the enterprise application/data stack, especially if Salesforce customers could plausibly become customers of yours.

One caveat on AWS

I wouldn't frame this as "AWS Ventures or nothing." AWS's current public startup strategy is heavily ecosystem-oriented: credits, technical help, marketplace/partner infrastructure and co-selling.

That's valuable—but for a startup whose core product potentially competes with an AWS service, the strategic relationship becomes much more complicated.

In that case, I'd be much more aggressive about M12/GV/Salesforce Ventures and independent VCs.

---

How I'd actually run the fundraising

I'd make the target list roughly:

Tier 1 — strategic

• M12
• GV
• AWS/Amazon
• Salesforce Ventures

Tier 2 — strategic depending on architecture

• Alibaba Cloud / Alibaba ecosystem
• Oracle ecosystem

Then pair them with independent infrastructure VCs.

The last part is important: I would not build your round around cloud-provider CVCs. Their strategic interests can create future customer, pricing, acquisition, or competitive complications. Ideally you have a strong independent lead investor and one strategic cloud investor who brings distribution/credibility.

If you tell me what your infrastructure startup actually does (e.g. Kubernetes, observability, AI inference, databases, networking, security, cloud cost optimization, developer tooling, etc.) and your stage/round, I can narrow this to the 5–10 specific funds/partners I'd pitch first, including the particular investors at each fund who look like the best fit.

When building a cloud infrastructure startup, pitching the corporate venture capital (CVC) arms or strategic investment programs of major cloud providers can yield major dividends—not just in capital, but in credits, co-selling agreements, and technical validation.

The primary corporate venture funds and strategic arms to target, categorized by provider, include:

• Microsoft (M12): M12 is Microsoft's dedicated venture fund, actively investing in early-stage enterprise software, AI, and cloud infrastructure . Getting them on board provides a direct line to Azure go-to-market teams and enterprise co-selling motions.
• Google (GV / Google Cloud) : While Alphabet's GV operates as an independent financial VC rather than a strict strategic arm, they heavily back enterprise tech and developer ecosystems. Simultaneously, engaging directly with the Google for Startups Cloud Program and their specialized AI partner funds can unlock heavy infrastructure credits and technical alignment.
• Amazon (AWS Startup Fund & Specialized Funds) : AWS doesn't have a massive standalone traditional CVC fund, but they operate the strategic AWS Startup Fund targeting early-stage software and cloud-adjacent tech. They also deploy capital through targeted vehicles like the Amazon Industrial Innovation Fund or Climate Pledge Fund if your infrastructure explicitly serves logistics or sustainability. For broader scale, plugging into AWS Activate is essential.
• Oracle (Oracle for Startups / VC Connect) : Oracle lacks a traditional branded venture fund, but through Oracle for Startups VC Connect they actively curate deal flow and connect early-stage infrastructure builders directly with external institutional VCs and Oracle Cloud Infrastructure (OCI) credits.

Key Strategic Trade-Offs to Consider

• The "Kill Zone" Risk : Pitching a hyperscaler's CVC means they see your roadmap intimately. If your infrastructure tool looks like a feature they plan to build natively into their console next year, they may pass—or worse, build it. Ensure your moat relies on deep architecture, multi-cloud optionality, or proprietary data/workflows rather than a thin wrapper around basic cloud primitives.
• Co-Sell vs. Cash : The real value of a cloud provider check isn't the money; it's getting listed on their marketplace (e.g., AWS Marketplace, Azure Marketplace) and getting their enterprise sales reps incentivized to sell your infrastructure to Fortune 500 accounts.

To help narrow down which of these to prioritize, tell me:

• What is your startup's core infrastructure focus (e.g., data ops, security, developer tooling, AI/compute orchestration)?
• What funding stage are you currently raising for (Pre-Seed, Seed, Series A)?