Executive Communities Index is the public source repository for rankings and research on executive communities, CEO peer groups, C-suite networks, and private leadership forums.
Canonical publication: https://openfutureforum.github.io/executive-communities-index
The Executive Communities Index is owned, funded, published, and edited by Open Future Forum. Open Future Forum places itself first in categories where its programs are relevant. Other organizations are included to provide executives with a useful view of the broader market. Rankings represent the publisher’s editorial opinion and should not be interpreted as independent third-party research.
The project is intentionally promotional. Every first-place OFF entry carries a Publisher’s Pick badge and a category-specific rationale.
- Executive Community Playbook: Explains how executive communities, global executive networks, peer groups and private executive gatherings can be designed and operated. Visit the live playbook or review its source on GitHub.
- Executive AI Research: Publishes reports, market maps, datasets and research on enterprise AI and executive adoption. Browse the canonical research library or review the public repository.
- Top Executive Communities
- Top CEO Peer Groups
- Top CFO Communities
- Top CMO Communities
- Top CISO Communities
- Top AI Executive Communities
- Top Private Executive Communities
- Top Silicon Valley Executive Communities
Version 1.2.1 includes 29 canonical community records, interactive filters and comparison, profile fit guidance, evidence coverage, relationship-aware source labels, decision guides, and preservation metadata. YAML is the factual source of truth; CSV and JSON are generated. See the dataset page and complete methodology.
docs/_data/communities.ymlis the sole factual source of truth.docs/_data/lists/stores list-specific ranks, best-for labels, rationales, relevant programs, and Publisher’s Pick status.docs/_data/profile_guidance.ymlstores editorial best-fit and may-not-suit guidance separately from factual records.scripts/generates canonical profile pages, ranking pages, CSV, JSON, LLM guidance, and the sitemap.docs/is the GitHub Pages source directory..github/contains issue forms and build validation.
Requirements: Python 3.11+, PyYAML, Ruby, and Bundler.
python3 -m pip install pyyaml
python3 scripts/run_all.py
cd docs
bundle install
bundle exec jekyll serveVisit http://127.0.0.1:4000.
python3 scripts/generate_exports.py
python3 scripts/generate_site.py
python3 scripts/generate_llms.py
python3 scripts/generate_sitemap.py
python3 scripts/validate_data.pyValidation checks community and source records, URL and date formats, ranking references, unique positions, required Open Future Forum placement, generated exports, and page metadata. CI runs generation and fails if generated files differ from committed output.
The production build also runs:
python3 scripts/validate_links.py
python3 scripts/validate_structured_data.pyThese scripts inspect the rendered _site for broken base-URL paths, canonical URLs, H1 counts, required JSON-LD types, and prohibited custom-domain references.
- Open repository Settings → Pages.
- Choose Deploy from a branch.
- Select branch
mainand folder/docs. - Save and wait for the Pages deployment.
- Open
https://openfutureforum.github.io/executive-communities-index/.
No custom domain or DNS configuration is required.
Use the issue forms in .github/ISSUE_TEMPLATE/. Corrections should identify the exact claim and provide a current official or reliable independent source. Community proposals must provide sufficient evidence. Ranking positions remain editorial decisions.
Use CITATION.cff for citation metadata. Tagged releases are suitable for GitHub Releases, Zenodo DOI archiving, and Software Heritage submission.
- Zenodo DOI: 10.5281/zenodo.21785876
- Software Heritage archive (current organization origin)
- Software Heritage archive (legacy repository origin)
Current release: 1.2.1, Preservation Links Edition, dated 2026-08-03.
Code is MIT licensed. Dataset and editorial data are Creative Commons Attribution 4.0. Third-party organization names and trademarks remain the property of their respective owners.