Base Layer methodology

Methodology

Every comparison published on Base Layer follows a consistent evaluation framework. The goal is to assess compatibility, deployment requirements, operational tradeoffs, and security considerations using publicly available information and official vendor documentation.

Evaluation Framework

What Each Comparison Covers

Base Layer uses the same evaluation structure across comparison pages so readers can understand which criteria are being considered and why they matter.

Platform Limits

  • API restrictions
  • Missing capabilities
  • Vendor dependencies
  • Documented constraints

Compatibility

  • OS compatibility
  • Integration requirements
  • Migration complexity
  • Maintenance impact

Deployment Tradeoffs

  • Scalability
  • Administrative effort
  • Infrastructure requirements
  • Long-term maintenance

Security & Compliance

  • Auditability
  • Encryption practices
  • Data residency
  • Compliance signals

Sources & evidence

Data Sources

Data is collected from public documentation and technical resources.

Official vendor documentation
Technical specifications and product pages
Public support resources and knowledge bases
Release notes and change logs
Security and compliance documentation
API and integration documentation

Review Process

Comparisons are reviewed periodically to reflect significant platform changes.

Review official documentation updates
Verify compatibility and deployment requirements
Update security and compliance information
Check pricing and licensing model changes
Reassess integrations and platform limitations
Correct outdated or deprecated information

Testing Environment

Hands-on testing is conducted using real hardware and network conditions, not simulated environments.

Multiple Linux distributions, Windows, and browser environments
App installation and functionality across platforms
Kill switch behavior under connection drops
DNS leak testing
Speed comparison against baseline throughput
Interface usability, particularly on Linux

Evaluation Boundaries

What Base Layer Does Not Do

Base Layer is designed as a comparison resource, not a ranking engine. Commercial relationships do not determine how products are evaluated or presented.

No Paid Rankings

Products are not ranked higher because of affiliate relationships, partnerships, or commercial arrangements.

No Sponsored Outcomes

Providers cannot buy a conclusion, category position, or favorable evaluation result.

Product Fit First

The focus is product fit, tradeoffs, requirements, and limitations — not universal best-product claims.

No Hidden Criteria

Comparisons are structured around visible criteria so readers can understand what is being evaluated.