Methodology

What We Produce

Each StackFacts output includes:

• Deployment context summary: A plain-language description of the scenario based on intake responses
• Reference architecture diagram: A generic control layer diagram showing architectural responsibilities without vendor-specific components
• Required control layers: Identity, data, runtime, network, and governance requirements for the deployment
• Tradeoffs and alternatives: Key decisions that may require balancing competing priorities
• Explicit assumptions: What we assumed about your environment that you should validate
• What this does NOT decide: Items explicitly out of scope for the reference architecture

What We Do Not Do

• We do not recommend specific vendors
• We do not rank or compare products
• We do not provide security assessments
• We do not certify compliance readiness
• We do not guarantee outcomes
• We do not replace qualified professionals

How Outputs Are Generated

StackFacts outputs are generated based on your intake responses using a structured framework that maps deployment characteristics to control requirements.

The framework considers: organization size, industry, cloud infrastructure, geographic region, data sensitivity, and timeline. These factors influence which control layers receive emphasis and which tradeoffs are highlighted.

Intelligence Sources

Full Stack Landscape combines multiple intelligence layers to produce accurate, actionable account positioning:

• Technographic enrichment: Automatic stack detection from multiple data providers. Technologies are mapped to a 7-layer architecture model and pre-filled for review.
• Web intelligence: Real-time search across trust centers, job postings, press releases, earnings transcripts, and public documentation to validate and enrich the technology footprint.
• Corrections intelligence: A curated knowledge layer that overrides stale or incorrect information with verified facts - product renames, acquisition status, integration availability, and competitive positioning.
• Integration directory: A verified database of platform-to-partner integrations across 25+ enterprise technology vendors, mapping specific platform products to partner capabilities.

Every technology in the output is tagged with its source and confidence level. Technologies you provide are marked "confirmed." Those discovered through enrichment are marked with their confidence level so you can validate them in discovery.

Platform Architecture Mapping

Platform Deal Architecture maps an account's entire technology footprint against your platform's product portfolio. For each technology in the account's stack, the engine determines:

• Which of your platform products integrate with it
• The integration type (native, API, certified, marketplace, community)
• Coverage gaps where no integration exists
• How your coverage compares to competing platforms

This analysis runs across 25+ platform vendors spanning security, cloud infrastructure, data platforms, observability, ITSM, CRM, and developer tools - producing a different result for each platform because each maps differently to the same account architecture.

Limitations

• Outputs are based solely on intake responses and do not reflect detailed knowledge of your environment
• Control layer requirements are generalized and may not capture organization-specific needs
• Tradeoffs presented may not be exhaustive for your particular circumstances
• This tool is designed for pre-decision guidance and should not be used as the sole basis for implementation

Corrections

If you identify errors in a StackFacts output, please report them via our errata page. We review all submissions and update outputs when corrections are warranted.