Help us understand how you’re building the future of Platform Engineering.
At Weave Intelligence, our research is fueled by the source. We spend our days talking to platform engineers, infrastructure architects, and DevOps leaders to understand the "real world" of the SDLC.
A vendor briefing is your chance to get on our radar. It’s an open door for technology providers to show our analysts how their products, services, and roadmaps are solving the complex problems facing platform teams today.
What is a vendor briefing?
Think of a briefing as a research deep-dive rather than a sales pitch. It is an opportunity for our team to learn about your company and latest developments, where you can share your product vision and differentiation.
While the flow of the session is focused on your presentation, our analysts will engage with questions to better understand the technical "how" and the strategic "why" behind your solution. We use these sessions to inform our broader research, build out reference architectures, and gather data for our reports.
What we’re looking for
Besides your product, the value it provides and its features, our questions will help us understand how you fit into the modern platform stack. When briefing us, please keep following questions in mind:
What’s the main focus area of your solution? Be it Infrastructure, app development, CI/DE, security, observability, FinOps or other cross cutting any concerns:. Make sure you are transparent about stakeholders, pain points and how you solve them.
Developer Experience (DevEx): How does your tool reduce cognitive load for developers?
Shift down or shift left: How does your solution help to apply best practices and platform engineering principles and expand the capabilities of an Internal Developer Platform?
Integration: Does your solution play well with others? We want to hear about integrations, APIs, and how you fit into an Internal Developer Platform (IDP).
Solving scale: How does your technology handle the jump from "it works on my machine" to "it works for 5,000 engineers"?
Point of view: What’s your take on the industry? How do you envision the future of platform engineering and which role will you and your solution play?
How it works
The request: Fill out the form below. Tell us who you are and what’s new.
The review: Our team reviews every request. We prioritize briefings that align with our current research themes (like AI in Platform Engineering, security, observability or FinOps).
The session: If it’s a match, we’ll book a 45-minute virtual session.
The outcome: Your information goes into our internal knowledge base, making you a part of our ongoing research and vendor landscape analysis.
Tips for a great briefing
Skip the fluff: We’re a team of former practitioners and senior analysts. You can dive straight into the architecture.
Show, don’t just tell: A demo is worth a thousand slides - we would love to see your product in action, ideally indicating how it enables developers in a 'golden path
Be honest about the "who": Who is your actual buyer? Who is your actual user? Knowing your target helps us categorize you correctly.
State of Platform Engineering Report: Volume 4
state-of-platform-engineering-report-volume-4
Reference architecture for an AI/ML Internal Developer Platform on GCP
reference-architecture-for-a-data-ai-internal-developer-platform-on-gcp
Reference architecture of an Internal Developer Platform on Azure
reference-architecture-of-an-internal-developer-platform-on-azure
Reference architecture of an Internal Developer Platform on GCP
reference-architecture-of-an-internal-developer-platform-on-gcp
Cloud Development Environments (CDEs) for Platform Engineers
cloud-development-environments-for-platform-engineers
Kubernetes cluster lifecycle management for platform engineers
kubernetes-cluster-lifecycle-management-for-platform-engineers
State of AI in Platform Engineering 2025
state-of-ai-in-platform-engineering-2025
Observability for platform engineers
observability-for-platform-engineers
Reference architecture of an Internal Developer Platform on AWS
ref-arch-aws