OpenAI 2026 hackathon

CyberTrace AI

Correlate evidence. Reconstruct attacks. Respond faster—with AI

Solo project by Adhira Gireesh Kumar · 0 likes · 0 comments

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,614 place in the like-ranked listing is a tie-break inside that group, not a ranking.

Projects (log scale)

1
10
100
1k
10k
05,592
11,758
2285
3–4132
5–975
10+14

Likes on Devpost. ▲ marks this project's group.

Show the figures
LikesProjectsShare of archive
05,59271.2%
11,75822.4%
22853.6%
3–41321.7%
5–9751.0%
10+140.2%
Devpost like counts for all 7,856 archived projects, captured when this archive was built.

Executive Summary

Company: CyberTrace AI

Self-reported basis: The entire analysis is based on a single project description submitted by the author to the OpenAI 2026 hackathon on Devpost. No independent verification, archived history, or third-party corroboration exists for any of the claims made.

What it appears to be: A proof-of-concept cyber investigation platform that uses AI to correlate forensic evidence from multiple sources (e.g., Windows logs, network traffic) and reconstruct attack timelines. It is described as a full-stack web application built with Next.js, React, FastAPI, and Python, using GPT-5.6 via Codex for development assistance.

What changed: The author states this was built as part of a hackathon submission. No prior version or evolution is evidenced.

Single most important open question: Is there any evidence that the platform has been tested in real-world environments or used by actual cybersecurity teams?

Confidence level: Low — based on one self-reported, unverified source with no traction data, revenue, customer base, or operational history.

Back to contents

What The Product Actually Is

The description states that CyberTrace AI is an AI-powered cyber investigation platform. It allows users to upload forensic evidence such as Windows logs, firewall logs, network traffic, and email data. The system then:

  • Correlates events across these sources
  • Detects suspicious behaviors
  • Reconstructs attack timelines
  • Calculates threat severity and confidence
  • Maps attacker behavior to the MITRE ATT&CK framework
  • Generates prioritized remediation recommendations

It is described as a full-stack web application, built with:

  • Frontend: Next.js, React, TypeScript, Tailwind CSS
  • Backend: FastAPI with Python
  • AI development tooling: GPT-5.6 via Codex

Inference: The platform is intended to automate parts of the incident response workflow for cybersecurity analysts.

Back to contents

Positioning & Claim Evolution

The author claims that CyberTrace AI helps analysts:

  • Correlate evidence
  • Reconstruct attacks
  • Respond faster
  • Provide explainable investigations, not just threat detection

It positions itself as a tool that improves analyst efficiency by reducing manual work and offering actionable insights.

Inference: The platform is positioned to serve cybersecurity teams looking for AI-assisted forensic analysis, particularly in environments where analysts must manually piece together logs and events.

Back to contents

Target Customer & ICP

The description states that the product targets cybersecurity analysts who investigate cyber incidents. It is designed to help them:

  • Understand what happened during an attack
  • Respond more quickly
  • Focus on remediation rather than manual evidence analysis

It also mentions a SOC-inspired interface, suggesting it may be aimed at Security Operations Centers (SOCs).

Inference: The primary customer segment appears to be cybersecurity professionals working in incident response or forensic analysis roles.

Back to contents

Business Model & Pricing Evidence

No information is provided about pricing, monetization, or business model. The description does not mention:

  • Revenue streams
  • Customer acquisition costs
  • Subscription tiers
  • Licensing models
  • Enterprise vs. individual use cases

Not evidenced

Back to contents

Technical & Delivery Signals

The platform is described as a full-stack web application, built using:

  • Frontend: Next.js, React, TypeScript, Tailwind CSS
  • Backend: FastAPI with Python
  • AI development tooling: GPT-5.6 via Codex

It includes features like:

  • Multi-source evidence correlation
  • Dynamic threat scoring
  • MITRE ATT&CK mapping
  • Interactive timeline reconstruction
  • AI-generated recommendations

Inference: The technical stack suggests a modern, scalable architecture suitable for web-based tools. Use of GPT-5.6 implies an emphasis on rapid development and AI-assisted engineering.

Back to contents

Traction & Maturity Signals

The project was submitted to the OpenAI 2026 hackathon, indicating it is a proof-of-concept or prototype.

No evidence of:

  • Revenue
  • Customers
  • Product usage
  • Market traction
  • Deployment in production environments
  • Iteration beyond the hackathon phase

Not evidenced

Back to contents

Competitive Context

The description does not mention any competitors. However, based on its stated functionality (forensic analysis, threat correlation, MITRE ATT&CK mapping), it would likely compete with:

  • SIEM tools (e.g., Splunk, QRadar)
  • Forensic analysis platforms
  • Incident response platforms

Inference: The competitive landscape includes established players in cybersecurity forensics and incident response. However, no direct comparison or differentiation from existing solutions is provided.

Back to contents

Key Risks & Red Flags

  1. No traction or commercialization evidence: The product exists only as a hackathon submission.
  2. Unverified claims: All features are self-reported without validation.
  3. Limited scope: The platform appears to be a prototype with no indication of scalability or enterprise readiness.
  4. AI dependency: Reliance on GPT-5.6 for development raises questions about reproducibility and control over the system’s behavior.
  5. No data privacy or compliance considerations: No mention of handling sensitive forensic data, which is critical in cybersecurity.

Back to contents

Diligence Questions To Ask The Founders

  1. What specific forensic formats does the platform currently support?
  2. Has the platform been tested with real-world incident data?
  3. How does it handle large-scale enterprise environments or high-volume log ingestion?
  4. Are there any plans for integrating threat intelligence feeds or external APIs?
  5. What is the current status of the product beyond the hackathon (e.g., roadmap, next steps)?
  6. How does the platform ensure accuracy and reduce false positives in its threat detection and correlation?

Back to contents

Investment/Partnership Verdict

Not evidenced

The project is described as a hackathon submission, with no evidence of:

  • Revenue
  • Customers
  • Product-market fit
  • Scalability
  • Commercial viability

It is not clear whether this represents a viable product or just an idea. Any investment or partnership decision would require further due diligence into:

  • Real-world testing
  • Market validation
  • Product maturity
  • Team execution capability

Confidence: Low — the description provides no evidence of traction, revenue, or operational history beyond a single submission to a hackathon.

Back to contents

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.