What we build
- Flow — See what your application actually does at runtime.
- Zerethon Tools — 180 free utilities for developers, creators and learners.
- Smart Edu — Lessons, question banks and online exams for schools, teachers and students.
- Zerethon Games — 27 free browser games — puzzles, arcade and learning games.
- Zerethon Social — A calmer social space built around people you actually know.
The products share one account system (sign in once, use any of them) but are otherwise separate applications, each on its own subdomain with its own data. How they fit together explains why.
How we work
- Ship before promising. We describe what exists. Plans are labelled as plans, and each product page lists its current limitations.
- Small team, owned end to end. The same people design, build, deploy and support the products, so feedback reaches the people who can act on it.
- Evidence over opinion. Performance work starts with measurements; product decisions start with how people actually use the products.
- Privacy by default. We collect what a feature needs, process data in the browser where we can, and don't sell personal data.
Why there is a knowledge section
Building these products means solving problems many other teams face: finding the real cause of a slow request, sharing one login across applications, designing exams that are fair online. The Knowledge section is where we write those up — practical explanations grounded in work we have actually done.
Funding and business model
The products are free to use. The cost of running them is covered by the team and, on some public pages, by advertising served through Google AdSense, as described in the privacy policy. Zerethon is not a financial or investment product, and no Zerethon feature — achievements, points or badges — has monetary value.
Open source
Parts of Zerethon are public on GitHub, including flow-laravel (Flow's MIT-licensed Laravel adapter) and its demo application.
Get in touch
Questions, feedback, bug reports and partnership ideas are all welcome — see contact. For security issues, please follow the responsible disclosure steps.