About CacheSphere
CacheSphere is a curated plain-English reference for 140 programming languages — catalogue, compare, concept transfer, and MIT-licensed JSON — plus small hand-curated AI/dev tools (14) and stack records (7). Registry layers for models, agents, companies, and benchmarks are preview snapshots; the Advisor is experimental. Coverage varies by language and record; link out for authority. Not a substitute for official docs or your own evaluation.
Who runs it
CacheSphere is built by Idaluna Labs. The project is open source: GitHub. Contact: [email protected].
What each tier covers
- Reference (core): 140 languages, compare, transfer,
/api/languages.json— deepest coverage. - Hand-curated: 14 AI/dev tools and 7 stack records — small, manual, reviewable signals.
- Preview snapshots: models, agents, companies, benchmarks — real registry data, uneven depth; verify on detail pages.
- Experimental: Advisor, Decision Brief examples, hosted
/api/agent/*when deployed — useful drafts, not authoritative.
What it is not
- Not official language documentation or a compiler spec.
- Not a course, tutorial site, or playground host.
- Not a model host or finished decision product.
How records are curated
CacheSphere adds structure between noisy discovery channels and the catalogues humans and agents use. The
public pipeline is: discovery (public, ToS-respecting signals only) →
verification (official docs and small experiments where sensible) →
curation (relevance and minimum data) → publish lean records with links
out for depth. Full internal notes live in the repo under
docs/PROCESS_LAYER.md.
Quality and evidence
Flagship languages tend to have richer patterns and tips; niche entries may be basic reference only. Benchmark and proof claims are early evidence — see proof status and benchmark methodology before citing numbers externally.
Licence and self-host
Core catalogue JSON is MIT-licensed. Clone the repo and run your own instance — see
Quickstart and For AI tools.
Static JSON works on any host; /v1 routes and MCP need the Node server when you deploy it.
FAQ · Quickstart · Home