Our Commitment
Vendor Neutrality
Reference Architectures is committed to vendor neutrality. This page explains what that means and how we maintain it.
Architecture First
Control layers and constraints are always presented before any mention of vendors.
No Defaults
No assumed "standard" vendors or implied preferences. We never suggest one vendor is the obvious choice.
Merit Over Money
Commercial considerations never override technical fit. We do not accept payment for placement.
Equal Treatment
Same rules apply to all vendors. Brand size or market dominance never alter conclusions.
What Neutrality Means in Practice
- Diagrams use generic labels (e.g., "Identity Layer") not vendor names
- Control requirements are stated as capabilities, not product features
- When vendors are referenced, they are mapped to capabilities, not positioned as solutions
- Ordering of vendors (when listed) does not imply ranking
- All recommendations include explicit reasoning
- Alternatives are always explained, even when one approach is more common
What We Avoid
- Vendor logos in diagrams
- "Best of" lists or rankings
- Language implying one vendor is superior
- Marketing phrases or promotional language
- Competitive or comparative framing
- Invented statistics or unverified claims
Reporting Concerns
If you believe a reference architecture output violates our neutrality principles, please contact us. We take all reports seriously and will investigate.
Experience vendor-neutral guidance
See how our neutrality commitment shapes the guidance you receive.