Fareke

FareKE is a self-reported community-powered platform for Kenyan commuters to check matatu fares between routes. The project was built by a single developer (Deve Sal) as part of the OpenAI 2026 hackathon, using AI-assisted development tools like Codex. It claims to help users search routes, view reported fares, and contribute fare data to build a centralized database.

The description states that FareKE aims to make commuting more transparent and help Kenyans budget for daily journeys. However, no evidence of revenue, customers, traction or adoption is provided beyond the author's own account.

Key commercial due-diligence question: Is there sufficient evidence of user demand or engagement to support a scalable business model beyond the initial prototype?

The description states that FareKE is a platform where users can:

• Search for transport routes between locations
• View fares reported by the community
• Contribute new fare reports to keep information current
• Help build a centralized source of public transport fare information

It is described as a web-based application built with JavaScript, Node.js, and PostgreSQL, designed for mobile usability.

Inference: The product appears to be a simple data collection and display tool that relies on community input rather than formal partnerships or APIs from transport providers.

The author positions FareKE as:

• A solution to an everyday problem faced by millions of Kenyans
• A way to make commuting more transparent and easier to budget for
• A community-driven platform that builds a centralized fare database

The project evolved from a personal observation about the lack of centralized fare information in Kenya, with the goal of turning this into a working product.

Inference: The positioning is rooted in local problem-solving and community participation, not formal market research or user validation.

The description states that FareKE targets:

• Kenyan commuters who use matatus (public transport)
• Students and daily commuters who need to budget for travel
• Anyone seeking reliable fare information before traveling

It is implied that the primary users are individuals rather than institutions or businesses.

Inference: The target customer segment is defined by geography (Kenya) and behavior (daily public transport use), but no evidence of actual user segmentation or persona development exists.

The description does not mention any pricing model, monetization strategy, or business model. It focuses on the platform's functionality and community-driven nature.

Inference: No commercial structure is evident beyond the initial prototype; there is no indication of how the platform might generate revenue or sustain operations.

The project was built using:

• JavaScript
• Node.js
• PostgreSQL
• AI tools like Codex for development acceleration

It emphasizes speed, simplicity, and mobile usability. The author notes challenges in designing a fast, readable interface suitable for use while traveling.

Inference: The tech stack suggests a basic web application with minimal infrastructure requirements, but no evidence of scalability or robustness beyond the prototype stage.

The description states that this is a hackathon submission and that the author built it in a short time using AI-assisted development. There is no mention of:

• Users
• Revenue
• Customer adoption
• Product usage metrics
• Iteration history or product maturity

Inference: The project appears to be at an early prototype stage with no demonstrated traction or user engagement.

No competitive landscape or existing alternatives are mentioned in the description. The author does not reference other platforms, apps, or systems that might address similar needs.

Inference: There is no evidence of market analysis or awareness of competitors; the project seems to be positioned as a novel solution without context.

• Unverified claims: All statements are self-reported and unverified.
• No traction: No evidence of users, customers, or adoption.
• Single-person development: The entire product was built by one developer, raising questions about scalability and long-term maintenance.
• Unclear monetization: No business model or revenue plan is evident.
• Dependence on community input: Reliance on user-generated data introduces risks around accuracy, consistency, and sustainability.

1. What specific problem are you solving, and how do you know it affects enough people to justify a scalable solution?
2. How will you ensure the accuracy of community-reported fare data?
3. Have you validated your idea with actual users in Kenya?
4. What is your plan for building a sustainable user base beyond the initial prototype?
5. Are there any existing systems or apps that already attempt to solve this problem?
6. How do you intend to monetize or scale this platform?