Cathonect: Secure Assisted Member Onboarding

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.

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.

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.

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.

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.

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.

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.

Not evidenced: no mention of competitors or market context beyond the author’s own narrative.

• 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.

1. What is the current status of deployment? Is the system live in any churches?
2. How many churches or members are currently using Cathonect?
3. Has there been any feedback from church leaders or users?
4. What is the plan for scaling beyond Ghana?
5. Are there any partnerships with dioceses or church organizations already in place?
6. What are the actual costs of implementing this system at scale?
7. How does the system handle compliance with data privacy regulations (e.g., GDPR, local laws)?
8. What is the timeline for completing the remaining staging and provider review steps?