AKTRU Verified AI Identity Builder

The description states that AKTRU Verified AI Identity Builder is a local-first web application that audits company representations across:

• Website content;
• Metadata;
• Structured data (Schema.org, JSON-LD);
• Machine-readable identity files;
• Optional registry documents provided by the user.

It classifies detected values into four evidence classes:

1. Supported by supplied registry document
2. Declared by website owner
3. Inferred from technical content
4. Unresolved

The tool exports:

• Technical audit reports;
• Markdown and JSON summaries;
• Before-and-after manifests;
• Deterministic machine-readable identity proposals;
• ZIP evidence packages.

It does not modify original files and requires explicit human approval before export.

Inference The application is a static web tool that processes local files without uploading them. It is not an API or SaaS offering.

The author states that the product aims to preserve provenance, expose uncertainty, and keep final decisions with human reviewers, rather than merging inconsistent data into one answer.

Early versions had issues like:

• AI systems interpreting only a minimal HTML shell due to JavaScript rendering.
• Terminology such as “verified from registry” which implied authentication of the document itself.

These were corrected by:

• Adding meaningful static HTML content for crawlers.
• Changing terminology to reflect what the tool can actually prove: “Supported by supplied registry document.”

Inference The positioning has shifted from a general-purpose identity audit tool to one focused on transparency, traceability, and human-in-the-loop validation.

The description does not clearly define target customers or ideal customer profiles (ICP). It implies the tool may be used by individuals or organizations auditing company identities, but no specific buyer personas or use cases are described.

Inference Potential customers could include SEO professionals, data analysts, or content creators working with structured data and identity signals. However, no explicit customer segments are defined.

There is no evidence of any business model or pricing structure in the description. The tool is presented as a self-hosted, open-source-like solution with no monetization strategy described.

Inference If this evolves into a commercial offering, it might be based on consulting or service-based pricing. But no such model exists yet.

The application is built using:

• React
• TypeScript
• Vite
• Browser File APIs
• GitHub Actions and Pages

It was developed during OpenAI Build Week 2026, with Codex assisting in implementation tasks including:

• Repository architecture
• Auditing engine
• Local file parsing
• Export generation
• Automated testing
• Accessibility improvements

The tool supports deterministic exports, handles encoding issues (e.g., BOM), and separates technical consistency from registry evidence coverage.

Inference The delivery approach is lightweight, client-side, and focused on reproducibility and traceability. It avoids cloud dependencies or telemetry.

The project has reached version 1.0.1, with:

• 30 of 30 automated tests passing
• Production build success
• Dependency audit showing zero known vulnerabilities
• Mobile validation at 375 px
• Keyboard accessibility checks
• Console validation without errors or warnings
• Public demonstrations in Polish, English, and German

However, there is no evidence of:

• Real-world usage
• Customer adoption
• Revenue or monetization
• Active user base

Inference The tool shows technical maturity and readiness for public use, but lacks real-world traction or commercial validation.

No explicit competitors are mentioned in the description. The author does not reference similar tools or platforms that perform identity auditing or structured data validation.

Inference It may operate in a niche space related to identity signals, structured data, and AI interpretation. However, no direct comparison or competitive positioning is evident.

1. No real-world usage or adoption: The tool has only been demonstrated publicly with synthetic data.
2. Unclear monetization path: While the author mentions a future service model, there is no current business plan or revenue source.
3. Limited scalability: As a client-side tool, it may not scale well for large-scale audits or enterprise use cases.
4. Single-person team: With only one member listed, operational capacity and long-term sustainability are unclear.
5. No external validation or third-party integration: The tool does not appear to integrate with major platforms or APIs.

Inference The risk of failure lies in whether the author can successfully transition from prototype to scalable, monetizable product.

1. What is your plan for transitioning from a prototype to a commercial offering?
2. Have you identified any specific use cases or customers who would pay for this tool?
3. How do you intend to validate the accuracy of the registry documents users provide?
4. Are there plans to expand beyond local-first processing, e.g., adding cloud capabilities or API access?
5. What are your thoughts on integrating with existing identity management systems or platforms?