Boris

Boris is a self-reported documentation compiler built in Zig, designed to generate both human-readable static websites and AI-ready structured knowledge graphs from a single source of truth. The project was submitted by Timothy Hartman and Beau Boorman as part of the OpenAI 2026 hackathon. It claims to offer zero-dependency compilation, deterministic output, and portability of documentation across platforms.

The author states that Boris is not just another static site generator but a compiler focused on ownership and migration of knowledge. The product is described as running in-process, avoiding heavy runtimes, and producing two artifacts simultaneously: a semantic website and an AI-ready context bundle.

The description states that Boris is a zero-dependency documentation compiler built in modern Zig 0.16. It is described as:

• A compiler, not a JavaScript application.
• Designed to generate two artifacts:
  • A fast, semantic static website for people.
  • A structured, AI-ready Context Bundle for retrieval, indexing, and future migrations.
• Built to help users own their documentation today, while ensuring it remains portable tomorrow.

The author emphasizes that Boris is not a typical documentation tool but one that treats documentation as a graph of knowledge, with each piece of content (document, heading, image, link, metadata) becoming part of a structured knowledge graph.

Inferred: The product is a static site generator with an added focus on AI readiness and migration. It is not evidenced to be used in production or by any users beyond the authors.

The description states that Boris was designed around the idea that "documentation isn't a collection of files. It's a graph of knowledge."

It positions itself as an alternative to existing documentation tools that tie content to specific frameworks, hosting providers, or ecosystems, making migration difficult.

The authors claim:

• Boris avoids tying users to a framework or ecosystem.
• It allows for deterministic output and in-process execution.
• It supports both human-readable and AI-ready formats simultaneously.

Inferred: The positioning is centered on documentation ownership, portability, and AI readiness. It is not evidenced that this has been tested or validated by users or the market.

The description does not state a specific customer segment or ideal customer profile (ICP). It implies that Boris targets users who want to:

• Own their documentation.
• Migrate it easily.
• Use it in AI contexts.

It is not evidenced what kind of users or organizations would use this tool, nor whether there are any existing customers or user personas defined.

There is no evidence of a business model or pricing structure. The description does not mention:

• Revenue streams
• Subscription tiers
• Licensing models
• Paid features
• Monetization strategy

Inferred: Since the project is self-reported and submitted for a hackathon, it is likely not monetized at this stage.

The description states that Boris:

• Is built in Zig 0.16.
• Is a zero-dependency compiler.
• Runs entirely in-process.
• Avoids heavyweight runtimes.
• Produces deterministic output from a single source of truth.
• Generates two artifacts:
  • A semantic static website.
  • An AI-ready Context Bundle.

Inferred: The technical approach is to build a compiler rather than a web app, using Zig for performance and portability. No evidence of delivery mechanisms or deployment details beyond the self-reported architecture.

The description does not provide any evidence of traction or maturity:

• No revenue.
• No customers.
• No usage metrics.
• No product adoption.
• No user feedback or reviews.
• No public release or versioning beyond the hackathon submission.

Inferred: The project is in an early stage, likely a prototype or proof-of-concept submitted for a hackathon. It has no demonstrated market traction or commercial viability.

The description does not mention any competitors or competitive positioning. It is not evidenced whether Boris competes with:

• Static site generators (e.g., Jekyll, Hugo, Docusaurus).
• Documentation platforms (e.g., Confluence, Notion, GitBook).
• AI-ready knowledge management tools.

Inferred: The product appears to be positioned as a next-generation documentation compiler, but no competitive landscape is described or evidenced.

• No traction or adoption: The project is self-reported and submitted for a hackathon. No evidence of real-world usage.
• Unproven utility: The claims around AI readiness, portability, and ownership are not substantiated.
• Limited team size: Only two members (Timothy Hartman, Beau Boorman) — may limit execution capacity.
• Niche focus: The product is highly technical and may have a limited target audience.
• No monetization strategy: No indication of how the project will generate revenue or sustain itself.

1. What specific use cases are you solving for, and who are your early adopters?
2. How does Boris differ from existing static site generators in terms of functionality and adoption?
3. Have you built a working prototype or MVP? If so, what is its current state?
4. What is the long-term vision for monetization or product development?
5. Are there any early users or partners who are testing or using Boris?
6. How do you plan to scale beyond the hackathon submission?