NerTzh Metrics Control Plane

The company appears to be a solo developer project named NerTzh Metrics Control Plane, self-described as an auditable local control plane for inspecting Bybit spot market metrics and integrating optional GPT-5.6/Codex-assisted analysis. The author states this is a tool built during the OpenAI Build Week hackathon, intended to demonstrate how AI-assisted engineering can produce reproducible, auditable developer tools for trading systems.

What changed: The project was submitted as part of an OpenAI hackathon, with no indication of prior development or commercial activity. It is described as a prototype with demo mode enabled by default and live trading disabled.

Single most important open question: Is there any evidence that this tool has been used beyond the author's own development environment, or whether it has moved beyond the prototype stage?

The description states that NerTzh is a local developer control plane for inspecting Bybit spot market metrics. It includes:

• A FastAPI-based control plane and responsive local viewer on port 8081.
• Optional Bybit demo engine isolated on port 8082.
• PostgreSQL for engine state and reconciliation.
• DuckDB plus Markdown for the local Context Bridge.
• Read-only routes for health, metrics, validation, order-status, and context.
• Protected chat boundary requiring a local control token.
• Virtual local TP/SL monitoring; native exchange TP/SL orders are disabled in the judge path.
• Demo-safe configuration with live trading disabled by default.

The viewer does not start the trading engine, call a remote model, or spend API credits when opened. The optional analysis route is explicit and protected.

Inference: The product appears to be a local tool for inspecting and auditing trading system states, with optional AI-assisted analysis capabilities that are explicitly separated from live execution.

The author positions NerTzh as:

• An auditable local control plane.
• A tool for inspecting Bybit spot market metrics.
• A developer tool for reconciling state and inspecting evidence.
• A demonstration of how Codex and GPT-5.6-assisted engineering can be used to build reproducible, auditable systems.

The project is described as a prototype built during the OpenAI Build Week hackathon, with no indication of prior commercial traction or product development beyond this submission.

Claim: The tool is designed to make trading system states inspectable from one surface without pretending saved evidence is live trade or AI decision.

Inference: The positioning is focused on auditing, reproducibility, and developer experience, not on direct market participation or commercial deployment.

The description does not state the target customer or ideal customer profile (ICP). It is unclear whether this tool is intended for:

• Individual developers working with trading systems.
• Firms or teams building trading infrastructure.
• Auditors or compliance teams inspecting trading systems.

Inference: The tool appears to be aimed at developers or engineers working in quantitative trading, particularly those using Bybit and looking for a local, auditable control plane.

The description does not provide evidence of any business model or pricing. It is unclear whether the project intends to:

• Be open-source.
• Offer a paid version.
• Be monetized through partnerships or consulting.
• Have any commercial offering beyond the prototype.

Inference: There is no evidence of a defined business model or pricing strategy.

The project is built with:

• FastAPI
• PostgreSQL
• DuckDB
• Markdown
• WebSockets
• Python
• Open-source tools
• Bybit integration (via demo engine)
• GPT-5.6/Codex-assisted engineering

It includes a demo release and video assets, and the repository is publicly available.

Inference: The tool is built with modern developer stack and integrates with trading infrastructure, but it is not described as production-ready or deployed in any live environment.

The project was submitted to the OpenAI 2026 hackathon, and the author states that it is a prototype. No evidence of:

• Revenue
• Customers
• Adoption
• Product-market fit
• Live deployment
• User feedback or engagement

Inference: The tool is at the prototype stage, with no demonstrated traction or maturity beyond the hackathon submission.

The description does not mention any competitors. It is unclear whether there are existing tools for:

• Local control planes in trading.
• Auditing trading system states.
• AI-assisted engineering in quantitative trading.

Inference: No competitive context is provided, and it's unknown whether this project addresses a known market gap or overlaps with existing solutions.

• The tool is described as a prototype, not a product.
• There is no evidence of revenue, customers, or traction.
• The author states that the demo mode is enabled by default and live trading is disabled — this may indicate a lack of commercial readiness.
• No information on whether the project will be maintained or expanded beyond the hackathon submission.

Inference: The biggest risk is lack of commercial viability or product-market fit, as there is no evidence of real-world usage or intent to scale.

1. What is the intended use case for this tool beyond the prototype?
2. Is there any plan to move beyond demo mode and into production use?
3. How does this tool differ from existing local control planes or auditing tools in trading systems?
4. Are there any plans to monetize or commercialize this tool?
5. What is the long-term vision for the project, and how does it fit into the broader trading ecosystem?