Archive position — measured, not model output
0 likes on Devpost
2,264 of the 7,856 archived projects have more likes, and 5,592 share exactly 0 — so this project's #3,177 place in the like-ranked listing is a tie-break inside that group, not a ranking.
Projects (log scale)
Likes on Devpost. ▲ marks this project's group.
Show the figures
| Likes | Projects | Share of archive |
|---|---|---|
| 0 | 5,592 | 71.2% |
| 1 | 1,758 | 22.4% |
| 2 | 285 | 3.6% |
| 3–4 | 132 | 1.7% |
| 5–9 | 75 | 1.0% |
| 10+ | 14 | 0.2% |
Executive Summary
What the company appears to be: Cathonect is a self-reported project aiming to digitize member onboarding for Catholic churches in Ghana, with a focus on secure, assisted enrollment that preserves institutional memory and prevents duplication.
What changed: During Build Week, the author added features around secure photo workflows, improved OTP transaction handling for signup and recovery, and enhanced form validation. These changes were implemented using GPT-5.6 via Codex to investigate and improve system design, particularly in authentication, storage, and concurrency.
The single most important open question: Is there any evidence of actual deployment or user adoption beyond the author's own development work? The description states that the OTP transaction model was validated locally but not applied to staging or production during Build Week. No traction data is provided.
What The Product Actually Is
The description states that Cathonect is a system for assisted member onboarding in Catholic churches, built as Progressive Web Apps (PWAs) with React, TypeScript, Vite, Supabase, PostgreSQL, and other technologies. It includes functionality such as:
- Members and Leaders PWAs
- Assisted registration
- Member records
- Account claiming
- Attendance tracking
- Groups
- Approvals
- Role-based access
It also implements a controlled photo workflow where authorized operators can upload profile photos to unclaimed member records, with server-side validation and temporary storage.
The system uses:
- Supabase Auth
- Edge Functions (Deno)
- PostgreSQL
- GPT-5.6 via Codex for investigation and design
Not evidenced: whether any of these features are currently live or used by users beyond the developer's own testing.
Positioning & Claim Evolution
The author states that Cathonect grew from a problem they observed in Catholic church leadership — reliance on paper forms, spreadsheets, WhatsApp groups, and memory-based processes. They describe their larger vision as becoming an "institutional operating system for the Catholic Church," starting with parishes and outstations in Ghana.
They emphasize:
- Digitizing not just forms but institutional memory
- Improving continuity through leadership changes
- Helping church leaders coordinate people and ministries using reliable information
The positioning is self-reported and claims a future role as an institutional OS, but no evidence of current adoption or traction exists.
Target Customer & ICP
The description states that Cathonect targets Catholic churches in Ghana, specifically parishes and outstations. The author notes that their larger vision includes eventually supporting deaneries and dioceses.
Not evidenced: whether there are any actual customers or users beyond the developer's own testing environment.
Business Model & Pricing Evidence
There is no evidence of a business model or pricing structure in the description. The project appears to be self-reported as a hackathon submission with no indication of monetization, subscriptions, or fees.
Technical & Delivery Signals
The system uses:
- React, TypeScript, Vite
- Supabase (Auth, Storage, Edge Functions)
- PostgreSQL
- Deno for server functions
- GPT-5.6 via Codex for development assistance
- Progressive Web App technology
Key technical elements mentioned include:
- Row-Level Security (RLS)
- Fixed database search paths
- Narrowly authorized server functions
- Private storage and signed URLs
- Transaction locks, replay protection, idempotency
- Environment separation
- Network-only handling for authentication APIs inside the PWA
The author also mentions using Codex to trace failures, compare recovery designs, identify race conditions, implement migrations, expand tests, and review security models.
Not evidenced: whether these systems are deployed or used in production.
Traction & Maturity Signals
The description states that:
- The assisted-photo workflow was successfully rehearsed in staging
- The OTP transaction v2 branch passed extensive local validation
- No end-to-end journey is currently available through the deployed application
- Remaining staging migration, configuration, provider evidence, and physical-device verification must be completed before release
No evidence of actual users, customers, or revenue is provided. The project appears to be in a pre-deployment phase.
Competitive Context
Not evidenced: no mention of competitors or market context beyond the author’s own narrative.
Key Risks & Red Flags
- Lack of traction: No evidence of real-world usage or adoption.
- Unverified claims: The description is entirely self-reported and unverified.
- Pre-deployment state: Features described were not applied to staging or production during Build Week.
- No commercial data: No revenue, customer base, or funding rounds are mentioned.
- Single-person team: Only one person (the author) is listed on the project.
Diligence Questions To Ask The Founders
- What is the current status of deployment? Is the system live in any churches?
- How many churches or members are currently using Cathonect?
- Has there been any feedback from church leaders or users?
- What is the plan for scaling beyond Ghana?
- Are there any partnerships with dioceses or church organizations already in place?
- What are the actual costs of implementing this system at scale?
- How does the system handle compliance with data privacy regulations (e.g., GDPR, local laws)?
- What is the timeline for completing the remaining staging and provider review steps?
Investment/Partnership Verdict
Not evidenced: no information on valuation, funding rounds, or investment interest.
The project appears to be a self-developed hackathon submission with strong technical design but no demonstrated traction or commercial viability. The author describes ambitious goals but provides no evidence of progress toward them beyond local testing and validation. This is not a product in production or with customers; it is an idea in development. Any investment or partnership consideration would require further evidence of real-world use, adoption, or revenue potential.
Source
Submitted to the OpenAI 2026 hackathon on Devpost. Project home on DevPost.
The analysis above was generated by a language model from the project's own one-line description. It is not independent research and contains no verified traction, revenue or customer data.