Learning and careers decision
Codédex
A basic Codédex clone (static lessons + runnable snippets + basic progress) is realistic for one technical person to build in about a week, but reproducing any proprietary curriculum, community, analytics, or brand value is not covered by this replacement.
Visit website↗Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All Codédex alternatives, with the arithmetic →
What a replacement has to do
- Serve lesson pages, let users run small code examples in-browser, track learner progress, search/browse lessons, deploy the site.
What it still won’t have
- Brand recognition and any curated proprietary curriculum
- Existing user community, forum, and network
- Built-in analytics and paid-product polish
- Any non-public integrations or proprietary content
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
Codédex does not publish a price we could read, so there is nothing to compare against. What building costs is below.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a minimal, self-hosted coding-lesson site using Next.js (React) + static generation, PostgreSQL for optional progress storage, and Vercel for deployment. Core features in scope: static lesson pages with Markdown authoring, client-side search, an embedded Monaco editor with runnable examples sandboxed in iframes, user sign-in via OAuth (GitHub), per-user lesson progress saved to Postgres via a small Next.js API, and CI for deploys. Out of scope: payments, advanced analytics, large-scale community/forum. Include error handling, input validation, and automated tests for the API and critical UI flows.
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 3 cited sources+3
- Evidence score60
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 3
Every page the run actually retrieved.
- official productCodédex | Start Your Coding Adventure
- open sourceHacker0x01/hacker101
- open sourcesonic-pi-net/sonic-pi
Integrity checks
What held up, and what did not.
