r/frappe_framework

Hello people, I am developing a voice based AI agent on top of ERPNext and it’s a pretty cool setup, Currently we have achieved a voice agent able to handle local slangs of people handling manufacturing factories. It is pretty cool to see full erp system working with no person actually handling and an AI agent working behind the scenes to fully handle ERP systems. If Anyone wants to have this implemented in your setup pls do contact, post onboarding this setup might save you so much time that you cannot even imagine at this point.

We're looking to hire paid interns who can help us develop and implement frappe in our organisation. The role is based in Delhi, India. But we are happy to hire to help us remotely as well. DM if interested.

Frappe Local

We spend a lot of time working with Frappe, and one thing kept bothering us.

Sometimes you just want to spin up a local Frappe site to explore an app, test an idea, or reproduce an issue. Instead, you end up installing dependencies, configuring services, or figuring out Docker before you can even get started.

So we built Frappe Local to scratch our own itch.

The goal is simple: make running Frappe locally as effortless as possible.

Frappe Local bundles everything needed under the hood, so you don't have to worry about installing or configuring the various moving parts yourself. It handles the setup while giving you a clean desktop interface to manage your local benches and sites.

Current beta includes:

• Create and manage local benches
• Create and manage sites
• Start and stop services from a desktop app
• Docker managed behind the scenes
• Cross-platform (macOS available today, more platforms coming)
• Free and open source

It's still an early beta, so expect rough edges. We're already using it internally and thought it might be useful to share with the community.

GitHub: https://github.com/lubusIN/frappe-local

Quick walkthrough: https://www.youtube.com/watch?v=UImalRAxq3s

Would love to hear your thoughts. Is this something you are looking to simplify? What would you like to see in a tool like this?

I love Frappe Manager for Frappe Frameworks installation but the last stable release is from august 2025 (v 0.18.0). To use 0.18.0 ve already have 2 patches fixing errors in my company and Frappe v16 can not be installed with that lately. For local use, the development version (0.19.0) can be used and everything works but I am afraid to put the development version on production, are you doing it?

Or you rather use Docker on production or even bare metal installation. Not sure what is better. For local development, I think Frappe Manager or Docker is better if you develop several project with various Frappe versions etc.

hi guys

I'm running jitsi, gitea, matrix,netbird, synapse-admin + authentik

i use authentik for SSO, all these are based on docker.

the thing is after all that setup, my ubuntu vps have 2.7 gb out of 8gb occupied, with 100gb space, and 4vcpu

at first i was trying to install ERPnext for my teams that use this vps service, someone told me its absurd to install ERPnext on your vps with all that setup and daily driver services that your team depends on it.

he says look at jitsi for example, you have to always give space and free ram available, i can use multiple services for that but im enchanted with ERPnext somehow, can somebody guide me?

I built a Swagger-like Developer Portal for Frappe 🚀

https://github.com/raisulislam0/frappe\_doc

One thing that always frustrated me while developing in Frappe/ERPNext was API discovery.

Need to call a whitelisted method?

Search through source code

Figure out the full module path

Guess parameter names

Check if it expects GET or POST

Open multiple tabs to inspect DocTypes and child tables

So I built frappe_doc.

It's a Frappe app that automatically scans all installed apps and generates a live developer portal from your codebase.

Features

✅ Discover all @frappe.whitelist() APIs automatically

✅ Parse Python type hints and Google-style docstrings

✅ Search APIs by app, module, route, arguments, DocType, etc.

✅ Generate ready-to-copy frappe.call() and curl examples

✅ "Try It Out" functionality to execute API calls directly from the UI

✅ Explore DocType schemas with expandable child-table trees

✅ AST-based scanning (doesn't import or execute your code)

✅ Works with custom apps and ERPNext out of the box

Example

Instead of searching through code to find:

@frappe.whitelist() def apply_for_leave(...): ...

frappe_doc automatically generates:

API route

Parameter documentation

Return information

Example requests/responses

Interactive testing form

Frappe JS snippet

cURL snippet

DocType Explorer

One feature I'm particularly happy with:

Child tables are displayed as expandable trees, so instead of jumping between multiple DocTypes, you can inspect the entire document structure in one place.

Example:

Sales Order └── Items ├── item_code ├── qty ├── rate └── warehouse

Why AST?

The scanner uses Python's ast module rather than importing modules, which means:

No code execution

Safe on production servers

No side effects during scanning

Looking for feedback

Would this be useful in your workflow?

I'm interested in hearing:

Features you'd like to see

Limitations you encounter with Frappe APIs today

Whether you'd use something like this in production

GitHub: https://github.com/raisulislam0/frappe\_doc

Feedback and contributions are welcome!

We've open-sourced something we've been using internally called Frappe Brewery 🍺

• It started as a small script to extract metadata from Frappe app repositories.
• Then we needed JSON endpoints for tooling.
• Then we needed validation.
• Then submission workflows.

Eventually it turned into a full app registry.

A few things it does:

• Extracts app metadata from repositories
• Tracks compatibility and installation information
• Generates static JSON indexes
• Provides APIs for tooling and integrations
• Uses GitHub issues and PRs for submissions
• Can be self-hosted on Cloudflare Pages

Registry Website

Registry GitHub Worlkflow

One design goal was keeping it lightweight and easy to fork. You can run a public registry, a private company registry, or a curated collection of apps for a specific use case.

We're planning to use it as a building block for some of our other Frappe projects, but it felt useful enough to release on its own.

Curious to hear feedback from others building tools around the Frappe ecosystem. What metadata or discovery features do you wish existed today?

GitHub Repo:
https://github.com/lubusIN/frappe-brewery

Our Public Registry:
https://frappe-brewery.lubus.in/

Read More:
https://lubus.in/blog/introducing-frappe-brewery-an-open-app-registry-for-frappe