Archive position — measured, not model output
1 like on Devpost
506 of the 7,856 archived projects have more likes, and 1,758 share exactly 1 — so this project's #2,124 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
The description states that trusin is a webhook relay system built for developers, designed to make webhook delivery reliable, traceable, and actionable. It is described as open-source and self-hostable infrastructure.
What changed
This project was submitted to the OpenAI 2026 hackathon by one developer (Aditya Putra Pratama), indicating a prototype or early-stage development effort. No prior version or product history is evidenced.
Single most important open question
Is there any evidence of actual usage, adoption, or revenue generation from this tool? The description contains no data on customers, users, or monetization.
What The Product Actually Is
The description states that trusin is a webhook relay system. It receives webhooks, persists events, routes them to destinations, retries failed deliveries, and displays a delivery timeline through a dashboard. It includes a CLI/TUI and an MCP server for AI-assisted operations. The backend is built in Rust; the frontend uses React and Vite. PostgreSQL stores data; Redis powers queues.
Evidence
- "trusin receives webhooks, persists events, routes them to destinations, retries failed deliveries, and shows a complete delivery timeline."
- "We built the backend, queue workers, and CLI in Rust; the dashboard uses React and Vite."
- "PostgreSQL stores organizations, events, rules, and delivery attempts. Redis powers queues and scheduled retries."
Inference The system is intended for developers debugging webhooks, with a focus on observability and reliability.
Positioning & Claim Evolution
The description states that trusin was built to solve the problem of debugging webhooks — specifically, failed requests being hard to reproduce, delivery history incomplete, and local development requiring extra tools. The goal is to make every webhook traceable and actionable.
Evidence
- "Debugging webhooks was frustrating: failed requests were hard to reproduce, delivery history was often incomplete, and local development required extra tools just to receive an event."
- "We built trusin to make every webhook traceable and actionable."
Inference The positioning is as a developer tool for improving webhook observability and reliability. It is not described as a commercial product or platform.
Target Customer & ICP
The description states that trusin is aimed at developers who need to debug webhooks, particularly those working with HTTP, Slack, and Telegram destinations. It supports local development without requiring tunneling tools.
Evidence
- "trusin receives webhooks, persists events, routes them to destinations, retries failed deliveries, and shows a complete delivery timeline."
- "We built trusin to make every webhook traceable and actionable."
- "The goal remains the same: make it easy to answer, 'What happened to this webhook?' in seconds."
Inference The ICP is developers working with webhooks, especially those needing reliable delivery, retry mechanisms, and observability.
Business Model & Pricing Evidence
Not evidenced. The description does not mention pricing, monetization, or any business model beyond the open-source nature of the tool.
Technical & Delivery Signals
The system is built using Rust for backend components, React/Vite for frontend, and includes a terminal UI and MCP server. It uses PostgreSQL for data storage and Redis for queues. It supports routing to HTTP, Slack, and Telegram destinations. It includes secure authentication methods such as Google, GitHub, Turnstile, API tokens, and scoped permissions.
Evidence
- "We built the backend, queue workers, and CLI in Rust; the dashboard uses React and Vite."
- "PostgreSQL stores organizations, events, rules, and delivery attempts. Redis powers queues and scheduled retries."
- "trusin also includes a terminal UI and MCP server for AI-assisted operations."
- "Secure authentication with Google, GitHub, Turnstile, API tokens, and scoped permissions."
Inference The tool is built with modern developer tools and supports multi-destination routing and secure access.
Traction & Maturity Signals
Not evidenced. There is no mention of users, customers, downloads, or any usage metrics. The project was submitted to a hackathon, suggesting it is in early development.
Competitive Context
Not evidenced. No information is provided about competitors or market positioning beyond the general category of webhook relay tools.
Key Risks & Red Flags
- No traction or adoption evidence: The tool is described as a hackathon submission with no data on usage.
- Single founder: Only one team member is mentioned, suggesting limited development capacity.
- Open-source and self-hosted: This may limit monetization opportunities unless there’s a SaaS offering or enterprise version not described here.
- No pricing or business model: No indication of how the tool will be monetized.
Diligence Questions To Ask The Founders
- What is the current usage or adoption rate of trusin?
- Are there any customers or users beyond the developer who built it?
- Is there a plan to commercialize this tool, and if so, how?
- How does trusin handle scale or performance in production environments?
- Has the tool been tested with real-world webhook traffic or integrations?
Investment/Partnership Verdict
Not evidenced. The description contains no data on revenue, customers, traction, or business model. It is a self-reported hackathon project by one developer, without any indication of commercial viability or market demand.
Confidence level Low — based entirely on the author’s own account, with no external validation or evidence of adoption or monetization.
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.