This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Understand Frappe and ERPNext projects as one connected model. Navigate DocTypes, inspect relationships, catch migration risks and export findings across your editor, terminal, AI tools and CI—without uploading your source.
Hey Product Hunt 👋
I built Frappe Inspector after repeatedly running into the same limitation while working with Frappe and ERPNext projects.
Editors understand Python, JavaScript and JSON individually, but they usually do not understand the conventions connecting a DocType schema to its controller, client script, hooks, patches, fixtures, Custom Fields and related DocTypes.
Frappe Inspector builds that missing project model locally.
The free Community edition includes:
• Frappe bench and app discovery
• DocType and field exploration
• Related-file navigation
• Frappe-aware completion and definitions
• Conservative diagnostics
• DocType relationship graphs
• Local project scans and Markdown reports
Universal Pro adds deeper project-wide inference, Git-based migration comparisons, Custom Field and Property Setter analysis, JSON/SARIF reports, advanced MCP tools and GitHub Action features.
Project files are analyzed locally as text. Frappe Inspector does not execute project code, run Bench, connect to Frappe sites or upload source code during normal analysis.
It is available for VS Code, Cursor, JetBrains IDEs, CLI, MCP-compatible AI clients and GitHub Actions. Universal Pro covers VS Code, Cursor, CLI, MCP and GitHub Actions; JetBrains Marketplace licensing is separate.
I would particularly appreciate feedback about:
1. False positives and unsupported Frappe patterns
2. Performance on larger benches
3. Migration problems that should be detected earlier
4. Features that would genuinely save time in everyday Frappe development
Thanks for checking it out. Blunt and technical feedback is very welcome.
Would love to see a diff view that highlights which hooks or controllers actually changed between two commits, right now I have to dig through git history manually to trace why a custom script stopped firing after a refactor.
About Frappe Inspector on Product Hunt
“Static analysis for Frappe and ERPNext projects”
Frappe Inspector was submitted on Product Hunt and earned 4 upvotes and 2 comments, placing #113 on the daily leaderboard. Understand Frappe and ERPNext projects as one connected model. Navigate DocTypes, inspect relationships, catch migration risks and export findings across your editor, terminal, AI tools and CI—without uploading your source.
Frappe Inspector was featured in Productivity (658.4k followers), Developer Tools (517.6k followers) and Artificial Intelligence (476.1k followers) on Product Hunt. Together, these topics include over 347k products, making this a competitive space to launch in.
Who hunted Frappe Inspector?
Frappe Inspector was hunted by Mohamed Tazi. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Frappe Inspector stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Mohamed Tazi