Neutrality Commitment
Reference Architectures is committed to vendor neutrality. This page explains what that means and how we maintain it.
Core Principles
Architecture First
Control layers, responsibilities, and constraints are always presented before any mention of vendors. Vendors appear only after architecture is established, if at all.
No Defaults
We do not assume "standard" vendors or imply preferences. When vendors are mentioned, multiple vendors may qualify—or none. We never suggest that one vendor is the obvious choice.
Eligibility Over Monetization
Commercial considerations never override technical fit. If criteria are not met, a vendor is excluded regardless of any business relationship. We do not accept payment for placement or favorable treatment.
Equal Treatment
The same neutrality rules apply to all vendors equally. Paid participation, brand size, or market dominance never alter eligibility, inclusion criteria, or architectural 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.