PlanGuard

PlanGuard is a self-reported AI Cloud Risk Operations platform that claims to investigate runtime drift, explain security and compliance impact, and recommend fixes before risks become incidents. The project was built as part of the OpenAI 2026 hackathon by one founder (Karim), using a stack including React, FastAPI, Python, PostgreSQL/Supabase, and AI tools like Codex and GPT-5.6. It positions itself as a unified platform for monitoring cloud risk, security posture, compliance readiness, and website security. The description states that it supports runtime drift monitoring, integrates security findings, assets, attack paths, and remediation workflows, and aims to make cloud risk management proactive through AI.

What Changed: The project evolved from an initial concept focused on cloud security operations into a platform with Website Security Posture Management (WSPM), redesigned dashboards, and expanded integrations. It also introduced AI capabilities for investigating drift and explaining impact in plain language.

Single Most Important Open Question: Is there any evidence of actual usage or traction beyond the hackathon prototype? The description does not state whether PlanGuard has been deployed, tested with users, or has any customers.

The description states that PlanGuard is a Cloud Risk Operations platform. It helps organizations monitor:

• Runtime drift
• Cloud security posture
• Website security posture
• Compliance readiness

It brings together:

• Security findings
• Assets
• Attack paths
• Compliance reporting
• Remediation workflows

The platform aims to help engineering and security teams quickly identify, prioritize, and resolve cloud risks.

Inference: Based on the tech stack (React, FastAPI, Python, PostgreSQL/Supabase) and the description of its functionality, PlanGuard appears to be a web-based SaaS product with a frontend dashboard and backend services for processing and analyzing cloud security data. It is not evident whether it includes real-time monitoring or is more of an audit/review tool.

The description states that PlanGuard was inspired by the need to reduce time spent switching between tools to understand runtime drift, compliance posture, and infrastructure changes. The platform aims to be a single workspace for cloud risk operations.

It claims to:

• Investigate runtime drift
• Explain security and compliance impact
• Recommend fixes before risks become incidents

The project evolved from an initial idea into a more feature-rich tool with:

• Website Security Posture Management (WSPM)
• Redesigned executive dashboard and core experience
• Rebuilt interfaces for findings, reports, assets, attack paths, and users
• Lightweight notification framework for cloud risk events

Inference: The positioning has shifted from a basic monitoring tool to a more comprehensive platform that integrates multiple aspects of cloud security and compliance. The use of AI tools like Codex and GPT-5.6 suggests an emphasis on automation and rapid iteration.

The description states that PlanGuard is designed for:

• Engineering teams
• Security teams

It aims to help these teams:

• Monitor cloud risk
• Understand what changed
• Take action before small issues become security incidents

Inference: The target customer appears to be organizations with cloud infrastructure and security operations, likely in mid-to-late stage startups or enterprises. The ICP is not explicitly defined beyond "cloud security teams" and "engineering teams."

Not evidenced.

The description does not state anything about pricing, monetization, or business model. It only describes the product’s features and functionality.

The project was built using:

• Frontend: React, TypeScript, Tailwind
• Backend: FastAPI, Python
• Database: PostgreSQL/Supabase
• Infrastructure: AWS, Docker, Terraform, OpenTofu
• AI tools: Codex, GPT-5.6

It was developed during the OpenAI 2026 hackathon.

Inference: The tech stack indicates a modern cloud-native SaaS product with a focus on developer experience and integration with cloud infrastructure. The use of AI tools like Codex suggests an emphasis on rapid development and iteration, which could be a signal of early-stage innovation or prototyping rather than a mature product.

Not evidenced.

There is no mention of:

• Revenue
• Customers
• Users
• Adoption
• Product usage metrics
• Deployment status

The project was submitted as a hackathon entry, and the description does not indicate any post-hackathon traction or development.

Not evidenced.

The description does not reference competitors, market size, or competitive positioning beyond stating that teams spend too much time switching between tools. No mention of existing platforms in the cloud security or compliance space is provided.

• No traction or revenue: The project is described as a hackathon prototype with no evidence of real-world usage.
• Unverified claims: All features and capabilities are self-reported; there is no independent verification.
• Single founder: The team size is listed as one, which may indicate limited execution capacity.
• AI tool dependency: Heavy reliance on AI tools like Codex and GPT-5.6 suggests a prototype or early-stage product, not a production-ready solution.
• Lack of clarity on business model: No information about monetization or pricing.

1. What is the current status of PlanGuard beyond the hackathon? Is it in active development or testing?
2. Have you conducted any user research or pilot testing with security teams?
3. How do you plan to monetize this platform, and what is your go-to-market strategy?
4. What are the key technical challenges that remain before a production-ready version?
5. Are there any existing partnerships or integrations in place?
6. What is the timeline for expanding support for additional cloud providers and compliance frameworks?