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

When building a cloud infrastructure startup, pitching the right corporate venture capital (CVC) arms can give you more than just capital—it can unlock deep technical integrations, go-to-market (GTM) motions, and co-selling opportunities with giants like AWS, Microsoft, and Google.

The major corporate venture funds and investment arms aligned with cloud infrastructure include:

1. Microsoft: M12

• Focus: Cloud infrastructure, data architecture, developer tools, AI infrastructure, and cybersecurity.
• Why pitch them: M12 is explicitly thesis-driven around the next generation of cloud and data workloads. Because Microsoft operates Azure and has a massive enterprise footprint, an M12 investment often comes with a streamlined path toward Azure Marketplace integration, co-sell programs, and enterprise validation.

2. Google / Alphabet: CapitalG & GV

• CapitalG (Growth Fund): Focuses on growth-stage B2B software, enterprise tech, and cloud infrastructure. They operate independently but offer direct access to Google's vast engineering, AI (Gemini/Vertex), and Google Cloud Platform (GCP) ecosystems.
• GV (formerly Google Ventures - Early to Growth): Operates independently as a traditional financial VC backed by Alphabet. While they invest independently, portfolio companies get high-value access to Google networks (having previously backed infrastructure giants like GitLab and Cockroach Labs / DataStax analogs).
• Why pitch them: If you are building data-intensive or AI-adjacent cloud infrastructure that heavily leverages modern silicon or distributed systems, Google's ecosystem provides unmatched technical synergy.

3. Amazon: AWS (Strategic Partnerships & Accelerators)

• Focus: Unlike Microsoft, Amazon doesn't operate a singular massive traditional "branded CVC" fund for general cloud infra, but instead invests via targeted initiatives like the AWS Impact Accelerator , sector-specific funds (like the Climate Pledge Fund or Industrial Innovation Fund), and direct strategic investments through corporate development.
• Why pitch them: AWS relies heavily on ecosystem lock-in and partner integrations. Working closely with AWS Startup programs, getting designated as an Advanced/Premier APN partner, and securing a strategic investment or credits via their business development teams can land you directly in the AWS Marketplace storefront, which is a massive pipeline for enterprise adoption.

Key Strategy Tips for Pitching Cloud CVCs:

• Co-existence vs. Killer Feature: Be crystal clear on whether your infrastructure complements their native services (e.g., a specialized observability, security, or data layer) or if you risk building a feature they already roadmap. Frame yourself as an ecosystem enhancer that drives higher cloud consumption for them.
• The Co-Sell Motion: Emphasize how your product will utilize their respective marketplaces (Azure Marketplace, AWS Marketplace, GCP Marketplace). CVCs love startups that increase platform stickiness and drive cloud consumption credits down.
• Watch out for "Strategic Drag": Ensure a corporate term sheet doesn't include restrictive ROFRs (Right of First Refusal) or acquisition clauses that might chill future independent M&A or public market interest.

To help narrow down the strategy, could you tell me:

• What specific layer of cloud infrastructure are you building (e.g., developer tools, data storage, networking, AI/ML ops, security)?
• What is your current stage (pre-seed, seed, Series A)?

For a cloud infrastructure startup, I’d target the CVC arms that have a strategic reason to care about your layer of the stack (compute, networking, storage, security, DevOps, observability, AI infrastructure, data platforms), not just generic corporate investors. The main ones to consider:

I would also consider adjacent strategic investors because many cloud infrastructure startups are more naturally aligned with hardware, networking, security, or developer ecosystems:

• nvidia.com — particularly if you touch AI infrastructure, GPU orchestration, inference, distributed training, or accelerated computing.
• cisco.com — networking, security, observability, infrastructure management.
• intelcapital.com — chips, systems infrastructure, edge, enterprise infrastructure.
• delltechnologies.com — enterprise infrastructure, cloud, security, developer tools.

How I’d prioritize the pitch list

A typical order:

1. M12 — if you sell into enterprises or developers.
2. GV — if you have deep technical differentiation and could become a category-defining infrastructure company.
3. AWS/Amazon strategic investors — if your product increases AWS consumption, improves AWS workloads, or fits AWS customer pain points.
4. NVIDIA Ventures — if AI infrastructure is central.
5. Oracle Ventures / Cisco / Dell Technologies Capital / Intel Capital — depending on your layer.

What to emphasize in the pitch

Cloud-provider CVCs usually care about one or more of:

• Consumption pull-through: “Customers using us spend more on your cloud.”
• Platform leverage: “We make your ecosystem more valuable.”
• Strategic gap: “We solve a problem hyperscalers do not want to build themselves.”
• Enterprise distribution: “You can introduce us to customers.”
• Technical moat: “This is difficult infrastructure, not a feature that a cloud provider can quickly copy.”

One caution

Taking a hyperscaler’s money can create strategic signaling issues. Some investors may wonder whether you are becoming tied to one ecosystem, so founders often keep ownership and partnership relationships balanced. CVCs can provide valuable introductions and validation, but the investment relationship should be evaluated alongside future fundraising and customer strategy.

If you tell me your specific layer (e.g., Kubernetes, networking, observability, AI infra, storage, security, developer tools, data infrastructure) and stage (seed/Series A/etc.), I can narrow this to the 5–10 investors most likely to engage.

When building a cloud infrastructure startup, pitching the corporate venture capital (CVC) arms of major cloud providers can unlock massive distribution, technical alignment, and co-selling opportunities. However, each major player approaches venture investing with a distinct mandate.

The primary corporate venture funds from the major cloud ecosystems to consider target different stages and strategic objectives:

• M12 (Microsoft's Venture Fund)
  • Focus: Enterprise software, cloud and data architecture, security, and AI infrastructure.
  • Why pitch them: M12 explicitly targets the next generation of cloud infrastructure and data layers. If your startup integrates deeply with Azure, or if your go-to-market (GTM) strategy relies on co-selling through enterprise marketplaces, M12 provides a direct bridge into Microsoft’s massive enterprise sales organization and product teams.
  • Learn more: Explore investment criteria on M12 Focus Areas.
• CapitalG (Alphabet’s Growth-Stage Fund)
  • Focus: Growth-stage technology companies (typically Series B and beyond) in enterprise software, security, AI/ML, and cloud-adjacent infrastructure.
  • Why pitch them: CapitalG operates relatively independently as a growth investor but heavily leverages Alphabet's vast engineering and go-to-market apparatus. They have a history of backing monumental infrastructure and data giants (like Databricks and CrowdStrike). Note that Alphabet also has GV (Google Ventures) , which invests independently across all stages, but CapitalG is your go-to if you are specifically aligned with enterprise/cloud scaling and need direct access to Google Cloud ecosystem advisors.
  • Learn more: Read about their value-add via the CapitalG About Page.
• Amazon / AWS (Strategic Ecosystem vs. Dedicated CVC)
  • Focus: AWS doesn't have a single monolithic "AWS Venture Fund" for core infrastructure the way Microsoft has M12. Instead, Amazon operates targeted funds like the Amazon Industrial Innovation Fund and early-stage programs like the AWS Impact Accelerator.
  • Why pitch them: For pure cloud infra, AWS prefers deep commercial integration and partnership over traditional equity checks early on. However, engaging with AWS Startup Programs and their corporate development teams can lead to direct co-marketing, AWS Marketplace integration, and potential investment from their specialized internal envelopes.
  • Learn more: Check out opportunities via Amazon Catalytic Capital & AWS Programs.
• Oracle Corporate Ventures / Strategic Partnerships
  • Focus: Enterprise workloads, multicloud infrastructure, database tech, and high-performance computing.
  • Why pitch them: Oracle aggressively incentivizes startups building on Oracle Cloud Infrastructure (OCI) via aggressive credits and migration programs. While they do less traditional early-stage lead-investing compared to M12, their corporate development group actively seeks infrastructure layers that make OCI more sticky for enterprise clients.

Strategic Tips Before You Pitch:

1. Beware of the "Killer Feature" Risk: If your infrastructure startup replicates a core roadmap item that the cloud provider is building internally, their CVC will pass or—worse—take deep technical notes and build it themselves. Ensure your moat relies on open standards, multicloud flexibility, or deep IP.
2. Co-selling is the Real Currency: The cash from a CVC is nice, but the real value is getting an enterprise account executive at Microsoft, Google, or AWS incentivized to sell your product to their enterprise pipeline. Ask potential CVC partners specifically how they structurally aid portfolio companies with marketplace co-sell motions.

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

• What is your current funding stage (Pre-seed, Seed, Series A)?
• Is your infrastructure cloud-agnostic or optimized specifically for one provider (e.g., AWS-native, Azure-native)?

If you’re building cloud infrastructure, I’d prioritize the corporate funds that can provide more than capital: cloud distribution, technical validation, enterprise introductions, and potentially strategic partnerships.

My shortlist

The important nuance: Amazon is different

For a cloud-infrastructure startup, AWS may be more strategically valuable than an AWS equity check.

AWS currently offers up to $200K in Activate credits, plus technical and GTM support, and its Global Startup Program provides Partner Development Managers and Solution Architects to qualifying startups.

So I'd pursue two tracks:

• Investment: M12 → GV → Salesforce Ventures → CapitalG depending on stage.
• Strategic relationship: AWS Startups / AWS Partner Network / AWS Marketplace.

That can be especially powerful if your product can become something AWS's salesforce can actually sell or recommend.

One thing I'd not do

Don't pitch these funds with a generic:

“We're building infrastructure for the cloud.” That's too broad and potentially makes you look like a feature AWS/Azure/GCP could eventually absorb.

Instead, position the company around the layer that the cloud providers don't want to own.

For example:

• “The control plane for multi-cloud GPU infrastructure”
• “Datadog for inference infrastructure”
• “Terraform for AI workloads”
• “The security layer for agentic workloads”
• “The FinOps platform for GPU clusters”
• “The developer platform for running stateful workloads across clouds”

The more clearly you can show why AWS/Azure/GCP customers need you even though those clouds already provide infrastructure, the more compelling the CVC pitch becomes.

If I were sequencing your outreach

Seed / pre-Series A: M12 + GV + a handful of specialist infrastructure VCs.

Series A: M12 + GV + Salesforce Ventures, with AWS strategic/partner discussions running in parallel.

Series B+: Add CapitalG and other growth-oriented strategic investors.

M12 is particularly compelling right now because its stated mandate is unusually close to what you've described: AI Cloud Infrastructure, with explicit interest in the next generation of cloud and data architecture.

If you tell me what your infrastructure startup actually does, your stage (pre-seed/seed/A), and whether you're AWS-, Azure-, GCP- or multi-cloud-oriented, I can give you a much tighter top-10 investor target list, including the specific partner at each fund I'd try to reach.

Seed / pre-Series A: M12 + GV + a handful of specialist infrastructure VCs.

Series A: M12 + GV + Salesforce Ventures, with AWS strategic/partner discussions running in parallel.

Series B+: Add CapitalG and other growth-oriented strategic investors.

M12 is particularly compelling right now because its stated mandate is unusually close to what you've described: AI Cloud Infrastructure, with explicit interest in the next generation of cloud and data architecture.

For a cloud infrastructure startup, you should prioritize corporate venture funds that can provide more than capital: cloud credits, marketplace distribution, design partners, enterprise introductions, and ecosystem credibility.

The best targets depend on what layer you’re building (DevOps, security, data infrastructure, compute, Kubernetes, AI infra, observability, networking, etc.), but this is the short list I’d start with:

Venture Capital Tracker Enterprise Technology Association## My suggested priority order

If you are building AI/cloud infrastructure

1. NVIDIA / NVentures
2. Microsoft M12
3. GV
4. AWS strategic investment
5. Intel Capital

AI infrastructure is currently a major focus area across these ecosystems.

If you are building developer infrastructure (DevOps, Kubernetes, platform engineering)

1. Microsoft M12
2. GV
3. AWS
4. Salesforce Ventures
5. Intel Capital

If you are building cloud security

1. Microsoft M12
2. GV
3. Salesforce Ventures
4. AWS
5. NVIDIA

Cloud security has been a strong area for enterprise-focused investors; for example, Salesforce Ventures has highlighted investments in cloud security companies such as Wiz.

How I would pitch a cloud provider CVC

Do not lead with:

"We are building a better cloud platform." Lead with:

"We make your cloud more valuable by increasing consumption, bringing workloads onto your platform, reducing customer friction, or extending your ecosystem." Cloud providers care about:

• Consumption growth — "Customers spend more on your cloud because of us."
• Marketplace revenue — "We can become a top marketplace seller."
• Enterprise adoption — "We unlock workloads you currently struggle to win."
• Developer mindshare — "We become the default tool developers use."
• Strategic gaps — "We solve a problem your customers complain about."

A practical fundraising approach

I would usually approach:

• 2–3 cloud strategic investors (for leverage and partnerships)
• 3–5 infrastructure-specialist VCs
• 1–2 AI/security specialists if applicable

Avoid taking a strategic investor solely for the logo. Check:

• Do they introduce customers?
• Will they commit engineering/product resources?
• Are there exclusivity clauses?
• Could the investment scare off competitors or acquirers?

If you tell me your specific layer (e.g., "Kubernetes management," "AI inference cloud," "cloud security," "observability," "data infrastructure," "serverless," etc.), your stage (seed/Series A/etc.), and your primary cloud target (AWS/Azure/GCP/multi-cloud), I can narrow this to the 10–15 funds most likely to write a check.

Avoid taking a strategic investor solely for the logo. Check:

• Do they introduce customers?
• Will they commit engineering/product resources?
• Are there exclusivity clauses?
• Could the investment scare off competitors or acquirers?

If you tell me your specific layer (e.g., "Kubernetes management," "AI inference cloud," "cloud security," "observability," "data infrastructure," "serverless," etc.), your stage (seed/Series A/etc.), and your primary cloud target (AWS/Azure/GCP/multi-cloud), I can narrow this to the 10–15 funds most likely to write a check.

Building a cloud infrastructure startup means you are playing in the backyard of the big three hyperscalers. Pitching their corporate venture capital (CVC) arms can unlock heavy-hitting enterprise go-to-market (GTM) motions, co-selling agreements, and massive infrastructure credits—if you target the right ones.

The primary corporate venture funds and investment arms from the major cloud providers mapped to a cloud infra startup include:

• M12 (Microsoft) — Focuses heavily on B2B enterprise software, developer tools, cybersecurity, and next-generation cloud and data architecture. Because of their explicit focus on AI infrastructure, data streaming, and secure IT management, M12 is a premier target if your infrastructure touches enterprise workloads, hybrid-cloud tooling, or data/AI scaling. Learn more about their thesis on the M12 AI Cloud Infrastructure Focus Page.
• GV & CapitalG (Alphabet / Google) — While GV (formerly Google Ventures) operates independently and invests broadly in infrastructure, data layers, and dev tools (early bets like SambaNova, CockroachDB, and Snorkel), CapitalG steps in for later-stage growth rounds ($50M+ checks). Note that Gradient Ventures (Alphabet's AI-focused seed fund) also targets early infrastructure (like AI compute and optimization). Check out current investment verticals via GV.
• AWS / Amazon Investment Vehicles — Amazon doesn't have a singular "AWS Venture Fund" for standard enterprise SaaS/infrastructure in the traditional standalone CVC mold (like M12). Instead, they deploy capital via strategic accelerators and targeted funds like the Amazon Industrial Innovation Fund (logistics/supply chain focus) or the Climate Pledge Fund (sustainability/energy-efficient data centers). For pure-play cloud infra, your best AWS route is often commercial alignment through programs like the AWS Startups ecosystem rather than a direct corporate equity check from a dedicated AWS VC arm.

Strategic Checklist Before You Pitch:

1. Co-opetition Risk: Ask yourself if your infrastructure competes directly with a core native service they sell (e.g., building a rival managed database to AWS Aurora or Google BigQuery). If so, their CVC might pass to avoid alienating existing ecosystem partners, though they still might invest if it drives massive core-compute consumption (EC2/GCE/Azure usage).
2. The GTM Motion: The real value of taking CVC money from Microsoft or Google isn't just the cash—it's getting listed in their enterprise marketplace faster, securing joint-selling incentives for their sales reps, and preferential architectural alignment.
3. Alternative Structures: Look into their startup programs (AWS Activate, Microsoft for Startups Founders Hub, Google for Startups Cloud Program) for non-dilutive credits before signing away equity, as these often pave a natural runway to their investment teams.

To help narrow down which of these targets makes the most sense right now, tell me:

• What is your core infrastructure layer (e.g., compute, storage, networking, developer tooling, or AI/ML pipelines)?
• What is your current funding stage (Pre-seed, Seed, Series A)?

For a cloud infrastructure startup, you should pitch M12 (Microsoft), GV and CapitalG (Alphabet/Google), and AWS-aligned strategic investment initiatives or specialized accelerators, as they directly back enterprise infrastructure and developer ecosystems .

When targeting corporate venture capital (CVC) from major cloud providers, align your pitch with how each specific arm invests and integrates with its parent cloud ecosystem:

• M12 (Microsoft's Venture Fund): Focuses heavily on enterprise software, cloud infrastructure, and AI/deep tech. Pitch them if your infrastructure cleanly integrates with or enhances the Azure ecosystem, as M12 often helps bridge go-to-market strategies with Microsoft’s enterprise sales organization.
• GV (formerly Google Ventures) & CapitalG (Alphabet): GV acts as an independent financial investor with Google backing, while CapitalG focuses on growth-stage scaling. Pitch GV for early-to-mid stage core infrastructure breakthroughs, and CapitalG if you are scaling and want deep alignment with Google Cloud Platform (GCP) architecture or data/AI workloads.
• AWS Strategic Investments & Programs: Unlike Google and Microsoft, Amazon relies less on a single standalone flagship CVC brand like M12 and more on direct strategic investments, targeted ecosystem funds, and massive accelerator tracks (such as their AI and cloud-focused startup accelerators) that unlock AWS credits and co-selling opportunities.

Strategic Trade-Offs of Pitching Cloud CVCs

To help narrow down the exact fund partners and tailor your outreach strategy, tell me:

• What is your current funding stage (Seed, Series A, etc.)?
• Is your infrastructure agnostic or tightly coupled to a specific cloud provider's proprietary stack?

If you’re building cloud infrastructure, I’d prioritize the strategic funds that can provide more than capital—cloud credits, distribution, technical validation, marketplace access, and introductions to enterprise buyers.

My priority list

1. m12.vc — highest priority

• Probably the cleanest fit if you’re doing cloud infrastructure, AI infrastructure, data infrastructure, DevOps, security, or developer tooling.
• M12 explicitly has an “AI Cloud Infrastructure” investment thesis covering cloud/data architecture, IT management, analytics, stream processing, data collection, and efficient/secure AI workloads.
• They invest from Seed through Series B and emphasize leveraging Microsoft's ecosystem and GTM.
• Pitch angle: “Microsoft can help us become infrastructure for the next generation of enterprise cloud/AI.”

2. nvidia.com — especially strong for AI infrastructure

• A very strong target if your infrastructure touches GPUs, inference, training, orchestration, networking, storage, data centers, AI agents, or accelerated computing.
• NVentures explicitly targets AI infrastructure and frontier compute and provides access to NVIDIA technical teams, platform integrations and GTM support.
• NVIDIA's strategic value can be enormous if your product becomes part of the AI-compute stack.
• Pitch angle: “We make NVIDIA compute materially more useful/economical/easier to deploy.”

3. salesforceventures.com — underrated for enterprise cloud infrastructure

• Don't dismiss Salesforce just because you're not building CRM software.
• Its current mandate explicitly includes Data & Infrastructure, and Salesforce Ventures says it expanded into cloud infrastructure companies transforming enterprise cloud computing.
• They bring relationships with enterprise decision-makers and Salesforce's ecosystem.
• Pitch angle: “We are infrastructure that makes enterprise cloud/AI adoption easier.”

4. gv.com — excellent if you want a true VC alongside strategic value

• GV is technically Alphabet's venture fund, rather than a Google Cloud corporate-venture arm.
• It has the unusual combination of VC independence and access to Google/Alphabet's technology and talent.
• Particularly attractive if you're building foundational infrastructure rather than something tightly coupled to one cloud.
• Pitch angle: “We're building a category-defining infrastructure layer that can sit above/between clouds.”

5. ciscoinvestments.com — strong for networking/hybrid cloud/observability/security

• Especially relevant if you're in networking, hybrid/multicloud, infrastructure management, storage, compute, observability, or cloud-native operations.
• Cisco specifically says its cloud investment strategy looks across the compute, networking and storage stack, with emphasis on hybrid multicloud.
• Pitch angle: “We are part of the infrastructure layer Cisco needs as enterprise computing becomes distributed.”

6. AWS — pursue the strategic relationship, but distinguish AWS Startup programs from VC

• AWS has an excellent startup ecosystem: credits, technical help, mentorship, marketplace distribution and investor connections.
• For a cloud-infrastructure startup, getting into the AWS ecosystem can be tremendously valuable even if an AWS-affiliated investment isn't the immediate outcome.
• Pitch angle: “We can become an important AWS-native infrastructure/Marketplace partner.”
• I'd simultaneously pursue AWS Activate / AWS Marketplace / AWS startup contacts rather than treating this solely as a VC fundraising target.

How I'd rank them by startup type

One important fundraising point

I wouldn't pitch all of these with the same deck.

Strategic investors are looking for a reason their ecosystem makes your company disproportionately successful. Your pitch should therefore have a specific slide—perhaps “Why Microsoft / NVIDIA / Google / Cisco”—showing exactly what you would do with their platform, customers, distribution, hardware, marketplace, or technical resources.

For example:

M12: “Microsoft becomes a distribution channel into enterprise AI/cloud.”

NVentures: “NVIDIA becomes embedded in our infrastructure architecture and ecosystem.”

Cisco: “Cisco becomes our channel into hybrid-cloud infrastructure buyers.”

GV: “Google gives us technical depth while preserving cloud neutrality.” That is considerably stronger than simply saying “we'd love a strategic investor.”

Also, don't overlook the non-investment relationships. AWS currently offers up to $200K in Activate credits, while Google Cloud's startup program can provide up to $200K in credits, or up to $350K for eligible AI startups. Amazon Web Services Google Cloud Those relationships can be useful both for reducing burn and for establishing credibility before asking the corporate VC arm for money.

If you tell me what your infrastructure product actually does, your stage (pre-seed/Seed/A), and roughly how much you're raising, I can narrow this to a top 5 target list and tell you exactly how I'd approach each fund and what the pitch should emphasize.

If you’re building cloud infrastructure, I’d prioritize corporate/strategic funds based on two things: actual infrastructure appetite and whether the parent cloud can materially accelerate distribution.

My shortlist

1. m12.vc — highest-priority

• This is probably the cleanest fit among the hyperscaler-affiliated funds.
• M12 explicitly lists AI Cloud Infrastructure as an investment focus, covering cloud/data architecture, IT management, analytics, and efficient AI workloads.
• Its portfolio includes infrastructure companies such as d-Matrix, Allstacks, and env0, so this isn't merely a theoretical thesis.
• M12 emphasizes access to Microsoft's ecosystem, technology and GTM resources.
• Pitch angle: “We make Azure/Microsoft's cloud ecosystem more valuable” is substantially better than simply “we're a cloud infrastructure company.”

2. gv.com — very strong

• GV isn't technically “Google Cloud Ventures,” but it's Google's main venture arm and has a serious infrastructure thesis.
• GV says it was early to back the AI infrastructure layer, including companies such as Snorkel, DeepSet, SambaNova, Modular and Lightmatter.
• Its partners specifically cover cloud infrastructure, developer tools and ML. Erik Nordlander, for example, focuses on cloud infrastructure and developer tools.
• GV has also invested directly in companies rethinking cloud infrastructure, such as Blacksmith.
• Pitch angle: technical differentiation + massive infrastructure market + developer adoption.

3. salesforceventures.com — underrated if you're enterprise-facing

• Salesforce isn't a hyperscaler, but Salesforce Ventures explicitly invests in Data & Infrastructure and has a long history in cloud infrastructure.
• Its value proposition is particularly compelling if your infrastructure ultimately gets sold to enterprises: customer introductions, strategic partnerships and access to Salesforce's ecosystem.
• Pitch angle: “Our infrastructure becomes part of the enterprise cloud stack,” rather than a pure developer-tool story.

4. Amazon/AWS — pursue strategically, but don't think of it like M12

• I would not put an “AWS Ventures” fund on your target list as though it were equivalent to M12 or GV. AWS's current startup strategy is much more centered on its startup ecosystem, partner/GTM programs, credits and accelerators.
• AWS offers up to $200K in Activate credits, Marketplace distribution, technical support and co-selling; its Global Startup Program is specifically designed for funded startups ready to scale.
• Amazon does have the Alexa Fund, but its stated mandate is emerging technologies, with roots in voice/smart devices and current activity spanning AI, hardware and entertainment—not general cloud infrastructure.
• Pitch angle: get an AWS strategic relationship/Marketplace/co-sell motion rather than making an AWS corporate-investment round the centerpiece.

How I'd rank them

The interesting thing is that you don't necessarily want all of them. If your startup is, say, Kubernetes/DevOps infrastructure, I'd lean heavily toward M12 + GV. If it's data infrastructure, GV + M12 + Salesforce Ventures. If it's security infrastructure, M12 becomes especially interesting because of Microsoft's security distribution.

And there's a potentially important fundraising strategy here: don't pitch the hyperscalers on the same story. Give each one a reason that their strategic assets make your company disproportionately more valuable.

If you tell me what the infrastructure actually does, stage (pre-seed/Seed/A), and current traction, I can give you a ranked list of 10–15 specific investors/partners—including the individual partners at each fund I'd target and the pitch angle for each.

To secure strategic investment for a cloud infrastructure startup, you should target the dedicated investment arms of the major hyper-scalers. These corporate venture capital (CVC) funds provide not only capital but also critical technical architecture validation, marketplace access, and cloud credits.

Here is the strategic breakdown of the funds you should pitch, ranked by their strategic alignment with infrastructure startups.

🔎 1. M12 (Microsoft Venture Fund)

• Strategic Focus: Enterprise software, cloud infrastructure, AI, and cybersecurity.
• Why It Works: M12 operates with a mandate to find technologies that complement the Azure ecosystem. They offer startups a direct path to co-sell with Microsoft’s global sales force and integrate into the Azure Marketplace.
• Typical Stage: Seed to Series C.

📈 2. AWS Generation AI Fund & Amazon Venture Arms

• Strategic Focus: Generative AI infrastructure, cloud tools, DevOps, and core infrastructure.
• Why It Works: While Amazon historically made ad-hoc ecosystem investments, they have consolidated specific funds (like the AWS Generative AI Innovation Center initiatives and core corporate development teams) to back startups that drive consumption on AWS.
• Typical Stage: Early to Growth stage.

📊 3. Google Ventures (GV) & CapitalG

• Strategic Focus: Core infrastructure, developer tools, security, and data analytics.
• Why It Works: Alphabet operates two distinct arms. GV acts more like a traditional VC, investing early in foundational technology. CapitalG is their growth-stage fund. Landing an investment here provides unparalleled access to Google Cloud Platform (GCP) product teams.
• Typical Stage: GV (Seed to Series A); CapitalG (Series B to Growth).

➡️ 4. Oracle Ventures

• Strategic Focus: Enterprise infrastructure, database technology, and cloud security.
• Why It Works: Oracle Cloud Infrastructure (OCI) has aggressively expanded its market share by focusing on high-performance compute and AI workloads. They invest heavily in startups that can leverage OCI's bare-metal capabilities.
• Typical Stage: Series A to Growth.

⚠️ Strategic Diversification Guardrails

Before pitching any hyper-scaler CVC, you must establish clear operational boundaries:

• Avoid Exclusive Cloud Lock-in: Ensure the investment terms do not legally bind your infrastructure to their specific cloud. Your customers will demand multi-cloud or hybrid-cloud compatibility.
• IP Protection: Clearly delineate your proprietary infrastructure code from the cloud provider's underlying APIs during technical due diligence to protect your core intellectual property.
• Customer Neutrality: Being backed by one specific provider (e.g., Microsoft) can occasionally create friction if you are selling to a customer heavily deeply embedded in a rival ecosystem (e.g., AWS).

To help tailor a specific outreach strategy, tell me:

• What specific layer of the infrastructure stack are you building? (e.g., orchestration, database, security, networking)
• What funding stage are you currently raising?
• Are you currently built on a specific cloud provider , or are you cloud-agnostic?