Does your architecture have hidden risks?

Paste your project idea, Cursor output, README, or stack decision below. PostIdea analyzes it across five dimensions and returns a scored risk assessment in 15 seconds. Free. No signup.

Ready to check your architecture risk?

Check your architecture risk →

What gets scored

The risk engine runs two layers. First, an LLM extracts structured signals from your text — chosen database, service architecture, expected user scale, external integrations, authentication complexity. Second, a deterministic rules engine converts those signals into scores. Same input always produces the same output.

This is not a code quality tool. It's an architecture sanity check. It catches microservices-at-500-users, custom-auth-solo, and offline-plus-realtime contradictions before you commit to them.


Five scoring dimensions

1. Overengineering

Flags architectural complexity that exceeds your stated requirements. Microservices chosen for 500 users. Kubernetes on a solo team. Redis caching layer with no caching requirement. Each adds 3-6 months of operational overhead with no benefit at your scale.

2. Contradictions

Detects mutually exclusive requirements. Realtime + offline-first simultaneously. Multiple databases with no clear separation of concern. OAuth complexity for an internal tool. These are architectural conflicts that will surface as bugs in production.

3. Scalability

Checks for missing infrastructure that will break under load. Auth with no session invalidation strategy. Schema flexibility combined with complex relationships. AI features with no data pipeline described. These are the gaps that cause 3am incidents.

4. Auth & Security

Scores authentication complexity against team size and risk profile. Custom auth system built solo scores CRITICAL. JWT-only with no revocation scores HIGH. Basic password auth for a fintech app scores DANGEROUS. Auth failures are primary risks, not secondary.

5. Vendor Lock-in

Tracks dependency on high-lock-in platforms. Firebase, Supabase, PlanetScale, Vercel, Heroku. Each integration point is a migration surface if pricing changes or the service shuts down. Not inherently bad, but you should know the exit cost before you commit.


Who this is for

Solo developers and small teams using AI coding tools — Cursor, Claude Code, GitHub Copilot — who want a sanity check before committing to an architecture. Also useful for freelancers validating a client's proposed stack before agreeing to build it.

If you're already 6 months into a build, this tool won't help. It's for the decision point — before you've written line 1.


See a real verification example

After you get your risk score, see how PostIdea's verification engine checks whether a real implementation matched its spec.

See the e-commerce verification case study →


Ready to check your architecture risk?

Check your architecture risk →