We have been working hard behind the scenes to bring out the next version of freeCodCamp to you, our community. It has been announced a few times about what’s coming up in the future releases.
We are continuously deploying our current
master, the default development branch on a separate isolated environment. This staging application is identical to our production environment in all aspects of functionality other than it using a separate database.
This isolation lets us test the development in a ‘production like’ scenario, without affecting regular users of freeCodeCamp’s platforms.
We welcome you to test these releases in a “public beta testing” mode and get early access to upcoming features to the platforms.
Your contributions via feedback and issue reports will help us in making the production platforms at freeCodeCamp more resilient, consistent and stable for everyone.
We thank you for reporting bugs that you encounter and helping us prior to general release to public on
You rock! Happy Contributing.
Identifying the upcoming version of freeCodeCamp:
The domain name will be different than
freeCodeCamp.org. Currently this public beta testing version is available at:
Leaving feedback and reporting issues
We welcome you to try out the platform and report us any issues by creating issues on our public tracker available at:
There will be some known limitations and tradeoffs when using this beta version of freeCodeCamp.
All data / personal progress on these beta applications
will NOT be saved or carried overto production.
Users on the beta version will have a separate account from the production. The beta version uses a physically separate database from production. This gives us the ability to prevent any accidental loss of data or modifications. The dev team may purge the database on this beta version as needed.
There are no guarantees on the uptime and reliability of the beta applications.
Deployment is expected to be frequent and in rapid iterations, sometimes multiple times a day. As a result there will be unexpected downtime at times or broken functionality on the beta version. The dev team will usually notify for updates in the Contributors Chat room.
Do not send regular users to this site as a measure of confirming a fix
The beta site is and always has been to augment local development and testing, nothing else. It’s not a promise of what’s coming, but a glimpse of what is being worked upon.
Sign in and authentication only available via email, not social.
Google, GitHub and Facebook logins will NOT be available in this beta mode. This is simply a technical limitation, because we are using a separate
test domainfor this version. Email logins will work just as fine.