OpenAI 2026 hackathon

DP OS (District Pixel Operating System)

Built by a photographer, father, and solopreneur, DP OS turns a powerful portfolio into a connected operating system to win clients and stand out in Washington, DC.

Hackathon project · 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,798 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

What the company appears to be

DP OS (District Pixel Operating System) is a self-reported connected operating system for a solo photographer in Washington, DC. The author, Luis Rivas, describes it as a tool that integrates client workflow elements—such as project management, estimates, contracts, and communication—into one system, using AI tools like Codex and GPT-5.6 to build the platform without traditional software development experience.

What changed

The description indicates that DP OS was not a new idea but an evolving system. The author states it existed before the official submission period and that the Build Week effort involved extending and stabilizing features, including Client Window, project data synchronization, and improved interfaces. It also includes a Judge Edition for contest evaluation.

Single most important open question

Is there evidence of real-world usage or business outcomes beyond the author’s personal experience, and how scalable is this approach to other creative professionals?

Back to contents

What The Product Actually Is

The description states that DP OS is a connected operating system for a solo photography business. It includes modules such as:

  • Projects – organizes client, schedule, value, tasks, estimate, contract, production details, and stage.
  • Studio Calculator – creates detailed estimates tied to each project.
  • Contract Builder – generates professional agreements using project and pricing data.
  • Mobile Signing – allows clients to sign contracts via typing or drawing.
  • Client Window – gives clients a branded private space with estimate, signed agreement, timeline, gallery, video, and communication.
  • DP Now – provides anonymous website activity and intent signals.
  • Image Optimizer & Video Compressor – prepares media for faster delivery.

The system is built using PHP, JavaScript, HTML, CSS, and AI tools like Codex and GPT-5.6.

Note

The author states that this is not a mockup or concept but a working system used in real business operations.

Back to contents

Positioning & Claim Evolution

The author positions DP OS as a way to transform a portfolio into a connected operating system, helping photographers win clients and stand out in competitive markets like Washington, DC. It is described as a solution for solo entrepreneurs who are creative but overwhelmed by administrative tasks.

The claim has evolved from an idea rooted in personal frustration (managing all aspects of a business alone) to a working tool that supports real client wins.

Inference The author’s positioning implies a niche market of solo creative professionals, not a general-purpose SaaS product. This is inferred from the context and lack of evidence for broader application.

Back to contents

Target Customer & ICP

The description states that DP OS is built for a solo photographer (Luis Rivas) in Washington, DC, who also handles marketing, sales, communication, pricing, contracts, production, delivery, and administration.

It is implied that the system could be extended to other creative entrepreneurs who are similarly overwhelmed by business operations but skilled in their craft.

Inference The ICP likely includes solo creative professionals (photographers, videographers, designers) operating in competitive markets with high administrative demands. No evidence of segmentation or targeting beyond this.

Back to contents

Business Model & Pricing Evidence

There is no evidence provided about pricing, monetization, or business model. The author describes using the system personally and mentions closing clients through its use, but does not state any revenue or pricing structure.

Note

The description does not include any information on how DP OS would be sold or whether it is a personal tool or a commercial product.

Back to contents

Technical & Delivery Signals

The system is built with PHP, JavaScript, HTML, CSS, and uses AI tools like Codex and GPT-5.6 for development. It includes:

  • A structured interface system
  • End-to-end workflow integration
  • Data synchronization across modules
  • Mobile signing capabilities
  • Image/video optimization tools

The author claims to have used Codex as a product, engineering, and verification partner, and that the system was built without traditional software development experience.

Inference The technical approach is unconventional but self-reported as functional. It suggests a low-code or AI-assisted development model, not a traditional enterprise stack.

Back to contents

Traction & Maturity Signals

The author states that DP OS has been used in real business operations and that two clients were closed using the system during Build Week. He also mentions that Client Window was implemented and put into use immediately after Build Week.

However, there is no evidence of:

  • Revenue
  • Customer base
  • Adoption beyond the author
  • Product usage metrics

Note

The system has been used in practice but lacks independent validation or traction data.

Back to contents

Competitive Context

The description does not mention any direct competitors. It implies that the author’s challenge was to avoid “disconnected generic platforms” and create a unified experience, suggesting a gap in the market for integrated tools for solo creative professionals.

Inference The competitive landscape is not described, but it likely includes generic business tools (e.g., Airtable, Notion) or niche tools for photographers. No evidence of existing solutions or competitive differentiation.

Back to contents

Key Risks & Red Flags

  • No revenue or customer data – The system is personal and self-reported; no evidence of monetization or adoption.
  • Unverified claims – All descriptions are self-reported, with no external validation.
  • Scalability concerns – The tool is built for one person’s use case and may not scale to other professionals without customization.
  • AI dependency – Heavy reliance on AI tools (Codex, GPT) raises questions about long-term maintainability and control.
  • Lack of team or structure – No team size or members listed; the system is built by a single person.

Back to contents

Diligence Questions To Ask The Founders

  1. What specific business outcomes have you seen from using DP OS beyond personal use?
  2. How do you plan to scale this for other creative professionals, and what changes would be required?
  3. Are there any plans to monetize or offer DP OS as a service to others?
  4. What are the limitations of AI-assisted development in maintaining and evolving the system?
  5. How does DP OS handle data privacy and security, especially with client information?

Back to contents

Investment/Partnership Verdict

Not evidenced.

There is no evidence of revenue, customers, or traction beyond the author’s personal use. The system is described as a working prototype built by one person using AI tools, but there is no indication of commercial viability, scalability, or market demand.

Confidence Low. The description is self-reported and unverified, with no third-party data to support claims of product-market fit or business outcomes.

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.