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 #7,568 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: Vigil is an open-source iOS safety camera app built by a single founder, Karthik Mahadevan, for use in stressful situations where individuals need to record encounters that may involve power imbalances or risk of evidence destruction. It is designed to help users capture and protect sensitive footage without fear of it being taken, searched, damaged, or erased.
What changed: The project was submitted as part of the OpenAI 2026 hackathon on Devpost. It represents a prototype built over a short development period using AI-assisted tools like Codex with GPT-5.6. The app currently supports basic recording and local storage but does not yet stream video to the cloud during recording.
The single most important open question: Is there sufficient evidence of traction, revenue, or customer adoption to justify further due-diligence effort? The description provides no data on usage, users, or monetization — only a self-reported product overview and roadmap.
Note: This analysis is based entirely on the author's own description. No external verification, archived history, or third-party sources are available. All claims are unverified and self-reported.
What The Product Actually Is
The description states that Vigil is an open-source iOS safety camera app designed for stressful situations. It allows users to:
- Start recording with one large control.
- Use an iPhone Action Button shortcut.
- Choose between rear, front, or dual-camera recording (picture-in-picture).
- Hide live preview using Screen Curtain and lower display brightness while recording.
- Save completed recordings to a "Vigil Vault" with Face ID or passcode protection.
- Optionally copy recordings to Photos and/or Google Drive.
- Finalize clips when interrupted or sent to background, then resume into new protected clips.
- Review capture context including timestamp and short ID.
- Share untouched original or stamped copy.
- Use an SOS control for emergency calls.
It does not include advertising, analytics, tracking, or developer-operated servers. The app is built using Swift, SwiftUI, AVFoundation, MultiCam APIs, LocalAuthentication, Photos, Google Sign-In, and Google Drive API.
Inference: The product appears to be a minimal viable prototype (MVP) focused on privacy and safety in high-stakes environments. It lacks streaming capabilities during recording and does not yet support tamper-proof storage.
Positioning & Claim Evolution
The author positions Vigil as a tool for truth and justice, enabling people to document protests or encounters where authority may be misused. The core claim is that it helps users record important events without fear of losing the evidence due to device seizure or destruction.
The app emphasizes:
- Protection from physical loss or damage.
- Preservation of first-hand accounts when institutional coverage fails.
- A focus on safety over convenience, especially under stress.
- Transparency about limitations and failure modes.
Claim: The author claims Vigil is a "safety camera" for use in stressful situations.
Fact: Not evidenced — this is a self-positioning statement without proof of adoption or impact.
Target Customer & ICP
The description indicates that the app targets individuals who may be documenting encounters involving power imbalances, such as students during protests in India. The primary user persona seems to be someone needing to record events where they are at risk of having their phone taken or destroyed.
It is not clear whether the target audience includes law enforcement, journalists, activists, or general public users beyond protest contexts.
Inference: The ICP likely centers around individuals in high-risk environments who value secure documentation and privacy.
Not evidenced: No explicit segmentation or user personas provided.
Business Model & Pricing Evidence
The description states that Vigil has no advertising, analytics, tracking, developer-operated server, or separate Vigil account. It is open-source and does not charge for use.
There is no mention of monetization strategies, subscriptions, or paid features in the current version.
Claim: The app is free to use with no commercial intent.
Fact: Not evidenced — this is a self-stated position without any revenue or pricing data.
Technical & Delivery Signals
The app is built using:
- Swift and SwiftUI
- AVFoundation and Apple’s MultiCam APIs
- LocalAuthentication for Vault access
- iOS file protection for local recordings
- Photos framework for optional Camera Roll copies
- Google Sign-In and Google Drive API for cloud backup
- App Intents for Action Button shortcut
Codex with GPT-5.6 was used as a technical partner during development, helping with interface design, camera pipeline implementation, crash diagnostics, and integration of features like OAuth and backups.
Inference: The app leverages modern iOS APIs and AI-assisted development tools to build a functional prototype quickly.
Not evidenced: No details on scalability, performance metrics, or long-term maintenance plans.
Traction & Maturity Signals
The description mentions:
- A public beta available through TestFlight.
- Source code, setup instructions, privacy model, security limitations, and roadmap are publicly accessible.
- The project was submitted to the OpenAI 2026 hackathon.
- It is described as an MVP.
There is no evidence of:
- Active user base
- Revenue or monetization
- Customer feedback or adoption metrics
- Product usage statistics
Not evidenced: No traction data, customer numbers, or market validation provided.
Competitive Context
The description does not reference any competitors. It focuses on the unique safety and privacy aspects of the app rather than comparing it to existing tools in the market.
Inference: Vigil likely operates in a niche space related to secure documentation and evidence collection, possibly overlapping with apps for activists or journalists.
Not evidenced: No competitive analysis or market positioning compared to other tools.
Key Risks & Red Flags
- No revenue or monetization strategy — raises questions about long-term sustainability.
- Prototype nature — the app is described as an MVP and not yet fully functional (e.g., no real-time cloud streaming).
- Single-founder team — limits scalability and operational capacity.
- Limited testing and verification — relies heavily on AI-assisted development, which may introduce unknown risks or inconsistencies.
- No third-party validation — no independent audits, reviews, or user feedback are mentioned.
Inference: The project is early-stage and unproven in terms of real-world utility, scalability, or commercial viability.
Not evidenced: No risk assessments or failure mode analyses beyond the author’s own documentation.
Diligence Questions To Ask The Founders
- What specific use cases have you identified for Vigil? How many people are currently using it?
- Are there any known technical limitations that prevent full functionality (e.g., no real-time cloud streaming)?
- Has the app undergone any security or privacy audits?
- What is your plan for expanding beyond the current MVP features?
- Have you considered how to scale this product beyond a single developer?
- How do you intend to validate the effectiveness of the app in real-world scenarios?
Investment/Partnership Verdict
This project is presented as an early-stage prototype built during a hackathon. It has no demonstrated traction, revenue, or customer base. The author describes it as open-source and non-commercial, with no clear path to monetization or growth.
Verdict: Not ready for investment or partnership consideration at this stage.
Confidence Level: Low — based on sparse evidence and lack of commercial data.
Next Steps: If further due-diligence is warranted, request actual usage data, user feedback, or a more detailed business plan.
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.
