Name Base Secure Routing

What the company appears to be: Name Base Secure Routing (NBSR) is a self-reported prototype for an identity-aware routing system that replaces traditional DNS with short-lived, policy-controlled routes. It operates as a control plane and gateway layer above existing service naming systems.

What changed: The project description states this is a validated prototype built for the OpenAI 2026 hackathon, not a production-ready platform. It uses existing open-source components (FastAPI, Envoy, OPA) to implement identity-based routing with temporary access tickets.

The single most important open question: Is there any evidence of traction, revenue, or customer adoption beyond the prototype's self-reported validation?

The description states that NBSR turns a logical service name (e.g., payments.internal) into a short-lived, identity-authorized route instead of exposing a reusable network location. It uses:

• A control plane to validate workload identity
• Open Policy Agent for default-deny authorization
• Ed25519-signed routing tickets
• Envoy Proxy for external authorization and routing
• Docker Compose and Kubernetes manifests for deployment

The system is described as not replacing DNS but adding an authorization layer above it.

Evidence: The author's own write-up describes the architecture and flow in detail, including how tickets are generated, validated, and used by Envoy to route traffic.

Inference: This appears to be a proof-of-concept for secure service-to-service communication using identity-based routing rather than traditional network addressing.

The description states that NBSR started from the question: "What if a service name resolved to a short-lived, identity-authorized route instead of a reusable network location?"

It explicitly says it is not meant to replace DNS but to add an authorization layer above conventional naming.

Evidence: The author's own write-up and tagline support this positioning.

Inference: This suggests the product is positioned as a security enhancement for service mesh or microservices environments, not as a replacement for DNS infrastructure.

The description does not state any specific customer segments or ideal customer profiles (ICP). It describes the system as working with workloads requesting access to logical service names in environments like Kubernetes or Docker Compose.

Evidence: The author mentions using Kubernetes manifests and Docker Compose, but no explicit target customer is named.

Inference: Based on the technology stack and use case, potential customers could include cloud-native teams managing microservices or developers working with secure internal routing.

There is no evidence of a business model or pricing structure in the description. The project is described as a prototype for a hackathon.

Evidence: The author states it's a validated prototype, not a production-ready platform, and does not mention any monetization strategy.

Inference: No commercial model or pricing data are evident from the self-reported description.

The prototype uses:

• Python and FastAPI
• Ed25519 for signatures
• Open Policy Agent (OPA)
• Envoy Proxy
• Docker Compose and Kubernetes
• Pytest and OPA tests
• PowerShell and Bash scripts

It includes:

• A threat model
• Architecture documentation
• ADRs (Architecture Decision Records)
• Demo script
• Public GitHub repository

Evidence: The author's own write-up details the implementation stack, testing methods, and deployment paths.

Inference: The system is built using well-established open-source tools and follows security best practices like fail-closed gateways and network isolation.

The description states that this is a validated prototype, not a production-ready platform. It includes:

• 20 Python tests passed
• 5 OPA policy tests passed
• Docker Compose configuration validated
• All five services started successfully
• 8 out of 8 mandatory security scenarios passed
• 15 Kubernetes resources passed offline validation

It also mentions that the backend has no published host port and direct access is blocked by real network isolation.

Evidence: The author reports these results as part of their validation process.

Inference: While the prototype works end-to-end, there is no evidence of customer adoption or revenue generation beyond self-reported testing.

The description does not mention any competitors or competitive landscape. It focuses on how NBSR differs from traditional DNS by adding identity-aware routing and short-lived access tickets.

Evidence: No comparison to existing tools or platforms is made.

Inference: The product appears to be positioned in the space of secure service mesh or internal routing solutions, but no known competitors are named.

• Prototype-only: The system is described as a validated prototype, not a production-ready platform.
• No traction or revenue: There is no evidence of customers, users, or monetization.
• Limited team size: Only one member listed (petrit bahtiri).
• Self-reported validation only: All testing and results are self-reported without independent verification.
• No integration with mainstream platforms: No mention of compatibility with major cloud providers or service mesh platforms beyond Kubernetes.

Evidence: The description itself highlights these limitations.

1. What is the current maturity level of the prototype? Is there a roadmap to production readiness?
2. Are there any early adopters or pilot customers using this system in real-world environments?
3. How does NBSR integrate with existing identity management systems (e.g., Okta, Auth0)?
4. Has the team considered performance implications at scale?
5. What are the specific use cases where this solution would be preferred over other service mesh implementations like Istio or Linkerd?