MORA

Project: MORA

Self-reported basis: The description is entirely from the author’s own submission to a hackathon, unverified and without independent corroboration.

Commercial due-diligence read: MORA appears to be a portfolio webapp built as a hackathon project that enables users to publish a professional portfolio using proof-based content. It is not evidenced to have revenue, customers or traction beyond the author’s own account. The single most important open question is whether this project will evolve into a product with sustainable commercial traction.

The description states:

• MORA is a "portfolio webapp" that allows users to sign up, authenticate (with password or magic link), and publish a portfolio from proof-based content.
• It supports editing, previewing, and publishing a live portfolio on the web.
• It was built with Next.js, Supabase, Tailwind, Vercel, and AI for server-side generation of the portfolio blueprint.

Inference: The product is an early-stage tool that enables users to generate and publish a professional portfolio using data they provide or have in their accounts (e.g., social proof). It is not evidenced to be a marketplace, SaaS platform, or developer tool.

Confidence: Low — based on self-reporting only.

The description states:

• Tagline: “Turn your social proof into your professional presence.”
• The author claims it was built to generate a portfolio in under 30 seconds legally with user data.
• It is positioned as a solution for users who want a quick, easy-to-use portfolio webapp.

Inference: MORA positions itself as a tool that helps professionals quickly build and publish a digital presence using existing proof (e.g., social media, work history, etc.). The positioning implies ease-of-use and speed, but no evidence of market demand or user adoption is provided.

Confidence: Low — claims are self-reported and unverified.

The description states:

• MORA is for users who want a quick portfolio webapp generated under 30 seconds.
• It supports authentication via password or magic link, suggesting it targets individuals (not enterprises).

Inference: The target customer appears to be individual professionals or creators looking to quickly publish an online presence using their own data and proof. No evidence of segmentation beyond this.

Confidence: Low — no evidence of customer personas, user research, or market validation.

The description states:

• MORA allows users to authenticate, edit, preview, and publish a portfolio.
• It uses Supabase for authentication and data persistence and is deployed on Vercel.

Inference: No pricing model or monetization strategy is described. The product appears to be free-to-use with no indication of paid features or tiers.

Confidence: Low — no evidence of business model, pricing, or revenue streams.

The description states:

• Built with Next.js, Supabase, Tailwind, Vercel.
• Uses AI models for server-side generation of the portfolio blueprint.
• Authentication is handled via Supabase and supports password and magic-link sign-in.
• Deployment is on Vercel.

Inference: The technical stack suggests a modern web app built with a frontend framework (Next.js) and backend-as-a-service (Supabase). It is deployed in a cloud environment, indicating some level of production readiness. However, no evidence of scalability, performance, or security audits is provided.

Confidence: Medium — the tech stack is described but not validated for robustness or maturity.

The description states:

• The app was built in a hackathon (OpenAI 2026).
• It is deployed and usable on Vercel.
• The author shipped a polished auth flow and end-to-end publishing pipeline.

Inference: MORA is at an early stage, likely a prototype or MVP. There is no evidence of user adoption, revenue, or growth metrics.

Confidence: Very low — no traction data is provided.

The description states:

• No mention of competitors or market positioning beyond its own functionality.

Inference: The competitive landscape is not described. It is unclear whether MORA competes with portfolio builders like Behance, Dribbble, or other SaaS tools for personal branding or developer portfolios.

Confidence: Low — no competitive analysis or market differentiation provided.

• No revenue or customer data: The product is not evidenced to have any users or monetization.
• Single-founder project: Built by one person (Param Mittal), which raises questions about scalability and team capacity.
• Hackathon origin: Likely a prototype, not a mature product.
• No pricing or business model: No indication of how the product will be monetized.
• Unverified claims: All descriptions are self-reported and unverified.

Confidence: Medium — risks are inferred from lack of evidence, not explicit data.

1. What is your plan to acquire users beyond the hackathon context?
2. Have you validated demand for this product with potential users?
3. How do you intend to monetize MORA?
4. What are your plans for scaling beyond a single developer?
5. Are there any existing competitors or substitutes in the market that you’re aware of?
6. What is the long-term vision for MORA beyond its current MVP?