RefactorFlow

RefactorFlow is a self-reported behavioural coding-practice platform for Python challenges, built as a solo project by Kamogelo Skhosana. The platform allows users to solve timed Python challenges in a distraction-free Monaco editor and receive session reports that capture their coding process — including edits, pauses, timing, and completion behaviour.

The author states that RefactorFlow was inspired by the idea that a developer’s process matters as much as the final solution, aiming to help learners understand their problem-solving habits. It includes features such as timed sessions, secure code execution via isolated Docker containers, and session reports with behavioural insights.

What Changed: The project is presented as a new tool for coding practice, focused on process over outcome. There is no evidence of prior version or evolution beyond this single submission.

Single Most Important Open Question: Is there any evidence of user adoption, revenue, or traction that would indicate market demand or product-market fit?

The description states that RefactorFlow is a behavioural coding-practice platform for Python challenges. It includes:

• Timed coding sessions in a distraction-free Monaco editor
• Secure code execution against private tests, using isolated Docker containers
• Session reports with coding-trail and behavioural insights
• Authentication, profiles, settings, dark mode, progress tracking, and session history

The author built it using Next.js 15, Supabase, and Monaco Editor, with code execution handled by a separate service that uses Docker containers for safety.

Inference: The platform is designed to capture and analyze how users approach coding challenges, not just whether they solve them correctly.

The author states that RefactorFlow was inspired by the idea that a developer’s process matters as much as the final solution, aiming to help learners understand their problem-solving habits. The tagline — “From passing tests to thinking better - that's RefactorFlow” — reinforces this positioning.

Claim: The platform is intended to be more reflective and supportive than traditional coding platforms, which only tell users whether their answer passed or failed.

Inference: This is a shift from outcome-based feedback to process-based learning. It positions itself as a tool for developer self-awareness and improvement, rather than just skill acquisition.

The description states that RefactorFlow is a coding-practice platform for Python challenges, aimed at learners working on beginner, intermediate, and advanced levels.

Inference: The target customer appears to be developers or aspiring developers who are practicing coding skills, particularly in Python. The platform may appeal to those seeking feedback on their problem-solving approach rather than just correctness.

Not evidenced: No specific customer segments, personas, or use cases beyond general learners are described.

The description does not contain any information about pricing, monetization, or business model.

Inference: Since this is a solo hackathon project, it is likely not yet monetized, and no evidence of revenue streams or pricing models exists.

The author reports that RefactorFlow was built with:

• Next.js 15
• Supabase (for authentication, challenge data, tests, profiles, session info)
• Monaco Editor
• Docker containers for secure code execution
• Codex with GPT-5.6 used for development assistance

The system uses a separate execution service that isolates user code in Docker containers to avoid security risks.

Inference: The platform shows technical sophistication in terms of architecture and security, particularly around code isolation and full-stack development.

There is no evidence of traction or maturity beyond the single submission to a hackathon. The project is described as a solo effort, with no mention of users, customers, revenue, or adoption metrics.

Inference: This is an early-stage product, likely in prototype or MVP form, and lacks any indication of real-world usage or growth.

The description does not mention any competitors. The author focuses on the unique value proposition of behavioural feedback over traditional platforms that only report pass/fail results.

Inference: RefactorFlow appears to be positioned as a niche tool in the coding practice space, potentially competing with platforms like HackerRank or LeetCode but with a different focus — process vs. outcome.

• No traction or revenue: The project is a solo hackathon submission with no evidence of adoption.
• Single founder: The team size is listed as 1, which may limit scalability and execution capacity.
• Unproven market fit: No data on user feedback, engagement, or demand.
• Technical complexity without validation: Secure code execution via Docker containers is complex; lack of evidence of successful implementation in production.

1. What is the actual user experience like? How do users interact with the session reports?
2. Are there any early adopters or beta testers who have provided feedback?
3. Has the platform been tested for scalability or performance under load?
4. What are the plans for monetization or long-term product development?
5. How does RefactorFlow differentiate from existing platforms like HackerRank or LeetCode in practice?