Relay Market Network

Project: Relay Market Network

Source: Self-reported author description from Devpost submission for OpenAI 2026 hackathon

Analysis basis: Only the project description supplied by the caller — no archived history, third-party verification or independent data

The description states that Relay Market Network is a three-role marketplace app built as a hackathon project. It claims to address real-world delivery challenges like race conditions and GPS spoofing through technical solutions such as concurrency control, transactional pricing, and secure handoff codes. The team built it using Java 17, PostgreSQL, and vanilla JS frontend.

What changed: This is a hackathon submission with no evidence of commercial traction or product-market fit beyond the authors’ own claims.

Single most important open question: Is there any evidence that this project has moved beyond prototype or proof-of-concept stage? The description does not indicate any live users, revenue, or operational deployment.

The description states that Relay Market Network is a three-role marketplace:

• Customers place orders with server-priced quotes and live tracking
• Couriers are dispatched and verify handoff with a secure code
• Admins manage catalog/dispatch via a live dashboard

It uses:

• Java 17 + raw JDBC + PostgreSQL for transactional control
• Min-heap + Dijkstra’s algorithm for dispatch logic
• Vanilla JS frontend with optimistic UI updates

The system is described as handling checkout, courier reassignment, and scheduled-order release under concurrency without an ORM.

Inference: The product appears to be a delivery marketplace platform built in a hackathon setting. It is not evidenced to have been deployed or used by real users.

The tagline states:

“Marketplace to doorstep — priced right, tracked live, verified secure.”

This positions the app as a secure, transparent, and real-time delivery marketplace.

The project description claims:

• It addresses problems in student delivery apps that "fake the hard parts"
• It builds real systems for concurrency control, dispatch logic, and verification

Inference: The positioning is to be a technically robust alternative to existing delivery platforms, emphasizing reliability and security over superficial features.

The description does not state specific customer segments or personas. However, the inspiration behind the project implies:

• Students or users of campus-based delivery services
• Users who want reliable, secure, and transparent delivery tracking

Inference: The likely target is a niche segment — such as university or college students using campus delivery services — but no explicit ICP is stated.

The description states:

• Customers order with server-priced quotes
• Couriers are dispatched and verify handoff with a secure code
• Admins manage catalog/dispatch from a live dashboard

There is no mention of pricing tiers, monetization strategy, or revenue model.

Inference: The business model appears to be based on marketplace fees or commissions, but this is not evidenced in the description.

The project was built using:

• Java 17
• PostgreSQL with raw JDBC
• Min-heap + Dijkstra’s algorithm for dispatching
• PBKDF2/AES-GCM for cryptography
• Vanilla JS frontend with optimistic UI patches

Key technical claims include:

• Fully transactional pricing engine
• Real dispatch algorithms (not a sorted list)
• Delivery-code system with no admin bypass
• Use of SKIP LOCKED queues, optimistic versioning

Inference: The team has implemented advanced concurrency and security features, but this is a hackathon prototype. No evidence of production deployment or scalability.

The description states:

• This is a hackathon project
• It was submitted to the OpenAI 2026 hackathon
• The team built it in a short time frame (implied by hackathon context)

No evidence of:

• Live users
• Revenue
• Product-market fit
• Customer adoption or retention

Inference: No traction or maturity signals are evident. This is a prototype, not a product in use.

The description does not mention competitors or market positioning relative to existing delivery platforms.

Inference: No competitive context is provided. The project appears to be self-contained and not compared to other solutions.

• Prototype only: No evidence of live deployment, users, or revenue
• No commercial traction: The product is described as a hackathon submission with no follow-up
• Unproven scalability: The technical stack (raw JDBC, vanilla JS) suggests limited production readiness
• No pricing or monetization strategy: No indication of how the platform would generate revenue

Inference: The project lacks commercial viability indicators and may not be ready for investment or partnership.

1. Has this product been tested with real users or deployed in a live environment?
2. What is the plan to scale beyond the current prototype?
3. Are there any existing partnerships or integrations with delivery services or payment gateways?
4. How does the team intend to monetize this marketplace?
5. What are the technical limitations of the current architecture that would prevent production use?