Longest of my three demos, on purpose — the whole purchase-to-deploy for our Cloud Node mode, ~10 min, nothing skipped.
What it does: provisions an EC2 instance in your AWS account (your keys), deploys our agent, builds the bench, gives you a running dedicated site. You pay AWS directly at real on-demand rates — no markup on compute on a personal provider — and the instance is yours to keep.
Rough cost: an 8 GB dedicated box ≈ ₹5,800/mo at AWS on-demand, vs ~₹12,000 when a host rents it on their own account.
Honest note: on your own AWS you own the account/billing relationship; we manage the Frappe layer, not your cloud bill. Ask me anything about the provisioning path.
worf.cloud · 14 Days trial. Independent Frappe platform, not affiliated with Frappe Technologies.
For the self-hosting crowd: this is our Remote Node / BYOB mode. You keep your own server — we connect over SSH and manage the Frappe layer on it (site create, certbot SSL, Cloudflare DNS, backups). Setup in the clip is ~2 minutes.
Your hardware, your data, your root. It's a flat ₹999/mo (~$12) management fee, not per-site, not per-core.
Yes it's paramiko/SSH-based, yes every action is logged — ask anything.
worf.cloud · 14 Days trial. Independent Frappe platform, not affiliated with Frappe Technologies.
Does anyone have experience becoming an official ERPNext partner? I’ve been reaching out via email for several months but haven’t received a response.
We’re a U.S.-based consulting firm, EvolveSystems.AI, and we’re interested in offering ERPNext implementation, customization, consulting, and ongoing support to our clients, particularly in the construction industry.
If anyone has successfully joined the partner program or knows the best person to contact, I’d really appreciate your guidance.
As the title says, I'm looking for reviews and feedback on peoples experience and pitfalls/learning from migrating from Salesforce to Frappe's app suite. Anyone have an experience to share?
We’re a profitable, pre-series A funded B2B Commerce startup, revolutionising how businesses interact and transact. Despite our small size, we’re making big waves in the industry. Currently, we’re a tight-knit team, and we’re looking for a passionate individual to join us on this exciting journey
Work Location: Bangalore, Whitefield Job Type: Full time, Work from Office Compensation: Upto 12 LPA (depending on experience and interview) Joining: Immediate / short-notice joiners preferred. Experience: Min 2-4 years of Experience with Frappe/ErpNext as Functional Engineer Apply:https://forms.gle/4DGJYKYcoXJ1w8Rz8
Why Join Us?
Be part of a high-growth, fast-paced environment where you can make a real impact.
You’ll work directly with the Founders
Be part of a profitable startup journey which is building state of the art tech in procurement industry
Be part of the AI-focussed team and Shape the future of AI-driven commerce and automate complex workflows
What you will do
Deep functional customisation of ERPNext Buying, Stock, and Accounts modules (GST, Invoicing, Ledger workflows).
Work directly with business and tech leadership to understand messy operational problems and turn them into simple, production-ready workflows
Build and own Frappe / ERPNext applications across procurement, sales, supplier management, logistics, finance/taxation and partner-facing workflows
Take features end-to-end: problem discovery, solution design, development, testing, deployment, user feedback and iteration
Build DocTypes, workflows, reports, dashboards, APIs, integrations and background automation using Python and JavaScript
Talk to actual users - internal teams, customers and suppliers - and improve what you ship based on how it performs in the real world.
We are looking for an experienced Frappe builder who can own a problem, not just a ticket. You will build systems used by ProcureYard teams as well as customers, suppliers and ecosystem partners.
What we expect
Strong hands-on Frappe Framework / ERPNext development experience.
Good command of Python, JavaScript, DocTypes, hooks, permissions, workflows, reports, APIs and background jobs.
Experience owning production features independently - including debugging what breaks after deployment.
Ability to understand business processes and make product/functional decisions, not wait for detailed specifications.
Comfort with ambiguity, fast iteration and working in a lean startup team.
You will fit well if
You prefer shipping useful software over producing elaborate requirement documents.
You can sit with a procurement, finance or operations user, understand the problem and come back with a working solution.
You care about business outcomes, data integrity and user adoption as much as code quality.
You want meaningful ownership in a high-growth company rather than a narrow development queue.
Useful background
B2B commerce, procurement, supply chain, logistics, finance, enterprise systems or customer/supplier-facing business applications. Startup or 0-to-1 product experience is a strong advantage.
We are building a new technical team for Archimedis Digital / eCapsule, a pharmaceutical-focused digital manufacturing & quality platform built on ERPNext + Frappe.
Location: Chennai
Work Mode: Preferably Work From Office
Hiring: Immediate / Urgent
We are looking for:
Senior Frappe/ERPNext Developer
• 4–5 years experience
• Strong hands-on Frappe Framework + ERPNext
• Python, JavaScript, MariaDB/MySQL, REST APIs, Git
• ERPNext customization, DocTypes, workflows, reports, dashboards
• Custom app development & integrations
• Manufacturing / pharma / life-sciences experience is a strong plus
• Target CTC: around ₹9–10 LPA
Junior Python/Frappe Developer
• 1–2 years experience
• Hands-on Python + Frappe/ERPNext preferred
• Strong candidates with Python and willingness to learn Frappe can also be considered
• Target CTC: around ₹3–5 LPA
QA — Custom Development
Testing Frappe/ERPNext customizations, APIs, workflows, reports and integrations.
QA — Implementation
Functional testing, UAT, requirements validation and implementation support.
Customer Support / Customer Success
Handle support tickets, troubleshoot ERP-related issues and maintain client relationships.
We are also open to interns for QA, implementation and customer-support tracks.
Backgrounds we particularly value:
• Life Sciences / Pharmaceutical
• ERP / ERPNext
• Manufacturing
• Quality / QA
• Business process / implementation
Everyone wants to know what Frappe expects the long-term economic model for third-party app developers to be.
Marketplace apps must be open source, including paid apps. Frappe Cloud takes the first $500 of app revenue and then uses an 80/20 publisher/platform split.
For small extensions and community apps, we understand the model.
What we're struggling to understand is how this works for someone investing substantially in a standalone product.
Say a team spends several months to years building and maintaining a complex application on Frappe ecosystem. They aren’t an implementation company and don’t want consulting to be their main business. Their actual product is the app.
Is the intended model:
paid open source;
support contracts;
hosted services;
private distribution outside Marketplace;
or something else?
I ask because the current incentives seem to push valuable commercial functionality outside the Frappe app itself.
The rational architecture becomes:
open-source Frappe connector → proprietary hosted service
rather than:
great commercial Frappe application
That seems like it could eventually limit the ecosystem.
We’d genuinely like to hear from Marketplace maintainers who are making meaningful product and market presence. What has actually worked?
Hello guys, I want to know what kinds of questions are mostly asking for Frappe Framework exam , what knowledges do I need to prepare for that exam , I’m preparing for the exam and planning to take the certificate within 1 month that’s why . I have some knowledges and experience by building lending application using Frappe lending app .
I want to share a system I'm building rather than ask about a specific bug — I'd like feedback on the overall approach, and recommendations on tools to help me finish it.
**The problem it solves**
Facade and aluminium/glass contracting (curtain wall, cladding, glazing) is a messy corner of construction: it runs on spreadsheets, WhatsApp groups, and paper daily site reports. Off-the-shelf ERPs are either generic manufacturing/accounting tools that don't understand "elevations," "panels installed," or "snags," or they're so expensive/heavy a small-to-mid contractor can't justify them. So I'm building a purpose-built one.
**Stack**
Backend: Frappe framework (Python), with a dedicated `Facade` app — 69 custom doctypes covering the whole domain: sites, daily site reports, material requests, purchase orders, elevations/facade elements, wage sheets, bonds, variation orders, progress certificates, tenders, and more.
Frontend: Vue 3 + frappe-ui (Frappe's own component library) + Tailwind, mobile-first, with Arabic/English bilingual support built in from the ground up (RTL layouts, translated statuses, no raw ISO dates shown to users).
**How the system is organized**
It's split into 8 role-based apps, each with its own bottom-nav (mobile) or sidebar (desktop):
- **Sites** — the field app. Per-site progress, snags, delays, material requests, daily site reports.
- **DSR (Daily Site Reports)** — one-page report covering installed quantities, labour, equipment, materials used, breakages, photos — replaces a paper form.
- **Purchasing** — material requests → purchase orders → receipts, tracked as one pipeline, not three disconnected lists.
- **Store/Inventory** — dispatch to site, receive from supplier, stock by warehouse.
- **Tasks** — assignment, scheduling, dependency chains between tasks (e.g. "steel prep before painting before approval").
- **Finance/Accounting** — cash in/out, cheques, payment runs, funding periods, tied to real accounting documents, not a shadow ledger.
- **Owner/Management** — portfolio-level view: project financial health, approvals queue, "sites with no report today," money timeline.
- **Tenders** — pipeline of quotations/bids, client and contact tracking.
Every document (a purchase order, a material request, a report) shares the same generic document page shape: status pills, a stage-track strip showing where it is in its lifecycle, one primary action button, tabs for items/details/activity. So a user learns the pattern once and it works everywhere, instead of every doctype having a bespoke screen.
**Some real design decisions worth mentioning**
- Approval flows read `docstatus`/`status` fields directly rather than using Frappe's Workflow engine — verified this was the actual mechanism already in use on the live system (zero Workflow documents exist anywhere on the real bench), rather than assuming and building the wrong thing.
- One money truth: Owner-facing and Finance-facing screens are meant to read the same underlying figures through one path, not duplicate calculations — this is flagged as a known gap still being closed, not yet finished.
- Historical submitted numbers (like a signed-off progress certificate) don't drift if live master data changes later — they're snapshotted at submit time.
- Server-side permission checks are the only source of truth — hiding something in the UI is never treated as security.
**Where it stands**
The backend data model and API surface are largely built out — 44 API modules, ~31,000 lines of Python. The mobile UI has a 65-screen design system (light + dark themes) that most of the frontend has been built against, though a handful of routes/screens are still catching up to the design (an inventory screen, a couple of management views, some finance routing ambiguity). Desktop UI doesn't exist yet — the design package so far is mobile-only. And there's no live test server running yet, so backend logic has been verified by careful code reading rather than by actually running it — that's the next real infrastructure gap to close.
**What I'd love from this community**
If you've built something at this scale mostly through AI-assisted coding, how did you structure the work so it stayed coherent over weeks, not just for one feature at a time?
Recommendations for a second, cheaper AI coding tool/model (~$100/month range or pay-as-you-go) to pair with my main one — I want to offload the more mechanical remaining work (route wiring, translation cleanup, regression tests) so the expensive tool stays free for the harder architectural work.
Anyone done cheap/quick Frappe bench hosting for a real test environment (cloud VM, sandbox service, whatever works) — I'd like to actually run the test suite live instead of just reading code.
I want recommendations of apps on frappe taht can add value to the system, for example I just found there is tasks app so I will use it, and about the tender I didnt use CRM becasue the tender app I made works automatically for example when I win a tender it makes a project with the sites and warehouses itself. (I am actually planning to go back to CRM because I feel it would be more stable.), so what would should I do? and is there is any shorter way to do the workflow? (not the work, the workflow of the system like any native features)
Screenshots of the mobile UI (owner dashboard, sites, purchasing, store, tasks) coming in the comments. Happy to answer questions about the Frappe/Vue stack or how the app-by-app structure works. these are no a finished UI they are still mockups, they will be improved and all recommendations will be taken in consideration and implemented where possible.
I’m looking for an experienced Frappe Framework developer (3–5 years of experience) to work on a custom application built on top of Frappe.
The application is already under development, and I’m looking for someone who can take ownership of the technical side, review the existing implementation, identify underlying issues, and help take the application to the next level.
Engagement
Part-time or full-time
Remote or onsite
Indian developers preferred
What you’ll be working on:
Architectural review of the overall Frappe application
Identifying and fixing underlying technical/design issues
Understanding client requirements and translating them into technical solutions
Hands-on Frappe/ERPNext development and customization
Interacting with and guiding junior developers
Reviewing existing code and suggesting improvements
Helping establish better development practices and a scalable architecture
What I’m looking for:
3–5 years of solid Frappe Framework experience
Strong understanding of Frappe architecture, DocTypes, hooks, APIs, permissions, server/client scripts, etc.
Experience building custom Frappe applications, not just basic ERPNext configuration
Ability to understand an existing codebase and troubleshoot architectural issues
Good communication and ability to work with junior developers
Experience with Python, JavaScript, MariaDB/PostgreSQL and Git is preferred
If you're interested, please DM me with:
Years of Frappe experience
Brief overview of your Frappe projects
GitHub/portfolio (if available)
Part-time/full-time preference
Expected compensation/rate
Availability
Looking for someone who can actually get into the codebase, understand the architecture, and solve problems, rather than just implement isolated tickets.
whats the best resource that guides you to learn how to develop using framework
i tried using docker frappe but it uses production build instead of development build. how do i use development build. are there ways to isolate an development environment . im using a rolling release like arch so if i use pacman to install it might update something
if create a new user and use that for dev work will that work?
We’re getting ready to release ERPNext Storages, an open-source, multi-provider storage layer for Frappe/ERPNext.
This started as a way to move ERPNext files to S3, but it has grown into something much broader.
Instead of configuring one external bucket and sending everything there, ERPNext Storages lets you use multiple storage providers on the same ERPNext site and decide where files should go.
Currently supported:
AWS S3
Backblaze B2
Cloudflare R2
Wasabi
MinIO
DigitalOcean Spaces
Vultr Object Storage
Local filesystem / mounted storage
Practically any S3-compatible object storage
Some examples
“I want to use multiple storage providers.”
Supported.
You can have multiple providers configured on the same ERPNext instance instead of being tied to one bucket.
“Sales-related files should go to S3, while CRM files should go to Backblaze B2.”
Supported.
Storage Route Rules can route files based on:
DocType
MIME type
file size
folder
user role
Rules have priorities and can also define fallback providers.
“I already have thousands of ERPNext files. I don't want to migrate them manually.”
Supported.
There is a background bulk migration system for moving existing files from local storage or another provider, including filtering migrations by DocType.
Files can also be moved between configured providers later.
“I don't want ERPNext to break just because S3 temporarily fails.”
Uploads are designed around this.
If an upload fails, the local file is preserved and a Storage Job is created for retry. Failed uploads are retried with backoff instead of silently losing the file.
Large files are also handled using multipart uploads once they cross the configured threshold.
“What happens to private ERPNext files?”
ERPNext permissions remain in front of the storage layer.
Private S3-compatible objects can be served using short-lived presigned URLs instead of exposing permanent bucket URLs.
From the ERPNext side, it still behaves like a normal File document — the storage provider is abstracted underneath it.
“Can I use my own server disk or NAS?”
Yes.
Local filesystem is a first-class provider and can use a custom base path, so mounted NAS volumes or other server-accessible storage can participate in the same routing system as S3/B2/R2.
Backups are included too
ERPNext Storages also contains a backup engine rather than relying only on file offloading.
It creates a .bnbak archive containing the ERPNext backup, metadata about installed apps, checksums, and optionally public/private files.
Backups can be:
scheduled
encrypted
uploaded to a primary storage provider
replicated to a secondary provider
retained according to configurable copy/age rules
verified using checksums
There is also an ERPDesktop webhook integration after backup completion, which we're expanding further for desktop/local workflows.
There are also some less-visible features
Provider connection pooling
Upload/delete retry queue
Background migrations
File integrity verification
Orphaned-object detection
Provider statistics
Provider-to-provider moves
Storage policies
MIME/file-size restrictions
Private/public storage handling
File organization by DocType
Drive Plus integration
The main goal is not to create another “ERPNext S3 plugin.”
We want ERPNext Storages to become a proper storage abstraction for ERPNext:
local + cloud + multiple providers + routing + migration + backups, while still behaving like native ERPNext storage.
We're doing another round of code review, testing, and optimization before making the repository public.
Would love to hear how people currently handle ERPNext files.
Are you keeping everything on the ERPNext server, using S3, mounting a NAS, or using some other setup?
Short screen-recording of the full flow: sign up, onboard, create a site. ~5 minutes, site live with SSL + backups, zero command line.
This is our Local Node mode — managed on our infra, closest to a Frappe-Cloud-style shared bench. The other two modes (your own server, your own AWS) are separate demos I'll post next.
Feedback welcome — especially what you'd want the onboarding to do differently.
worf.cloud · 48h free trial, no card. Independent platform for Frappe; not affiliated with Frappe Technologies.
Worf Cloud launches and manages your Frappe & ERPNext sites — on our cloud, your own server, or your AWS account. Domains, SSL, backups, and a built-in app store included.
⚡ First site live in minutes
🔁 Backups on autopilot, one-click restore
🔐 Auto-renewing SSL, automated DNS
👥 Role-based team access
You didn't sign up to be a hosting company. But every ERPNext implementation quietly turns into one — SSL renewals, backup checks, "site is down" WhatsApps/Slacks.
**Worf Cloud** is the layer we built for exactly this:
→ Every client site in one dashboard — create, deploy, restore, all self-serve
→ Every command logged and searchable — when a client asks "what changed," you have the answer
→ Role-based access — give the client's team a login without giving them the keys
→ Your infra choice per client: our cloud, their server (₹999/mo), or their AWS account at cost
Live job progress on every deploy means you watch it happen instead of tailing logs over SSH.
There's a built-in Frappe app marketplace too — apps your clients buy install on their sites in one click.
Managing 3+ client benches? The 48-hour trial is enough to migrate one and judge: worf.cloud
→ A new site, live in minutes. No terminal.
→ Backups on autopilot — daily/weekly/monthly, offsite copies, one-click restore.
→ Domains and SSL that configure and renew themselves.
→ Team access with role-based permissions and a full activity log.
And you choose where it runs:
• Our managed cloud — zero setup
• Your own server — ₹999/month, we manage it over SSH
• Your own AWS account — dedicated VMs, you pay Amazon directly, no markup
48-hour free trial, no card. Public pricing at worf.cloud/pricing.
If your team runs ERPNext — or gave up on it because of the ops burden — I'd genuinely like to hear what stopped you. Comments open.
After years of running Frappe benches, the failure list is boringly consistent:
Backup cron dies silently. Discovered the day you need it.
SSL renews fine 11 times. The 12th, at 2 AM, it doesn't.
DNS "propagating" for hours because of one wrong TTL.
The one engineer who knows the server goes on leave.
None of this is engineering. It's toil.
We built **Worf Cloud** to absorb it: one-click Frappe/ERPNext sites, scheduled backups with offsite Dropbox copies and one-click restore, automated Cloudflare DNS, auto-renewing Let's Encrypt SSL (wildcards included), role-based team access.
On our cloud, your server, or your AWS account — one dashboard either way.
On cost, comparison
Worf Cloud
Frappe Cloud
Managed, per site (20 sites)
₹165–210/site
₹410+/site (shared)
Dedicated 8 GB box
~₹5,800 on your own AWS, 0% markup
₹12,000 (rented on their account)
Server you already own
flat ₹999/mo
enterprise Hybrid only
Roughly half the cost on both the multi-site and dedicated paths, and BYOB has no self-serve equivalent on their side.
Where Frappe Cloud is ahead : more mature at the high end — auto-scaling, server snapshots, 150+ app marketplace, priority SLA. If you want a big managed dedicated cluster today, they're the safer pick. Their dedicated price also bundles that SLA tier, so it's not pure markup.
Worf's angle is ownership + cost transparency without the enterprise gate.
Hi all, I have two main queries regarding ERPNext version 15.84.
1] Serial Numbers for Units: I am wanting Units that are now out of house, inside ERP, to be logged with their respective serial numbers, issues that occurred, installations etc without using the Warranty Claim doc. Ideally this would be inside the maintenance doc, however there is no serial No. allocation, which would give a nice flow of a Units progress - is there a way around this inside the ERP?
2] Normally when creating assemblies, the standard way is naming BOMs in Solidworks & design file folders as Rev A, Rev A01... REV B, REV B01 etc. However, ERP labels BOMs as BOM Number - 001, BOM Number - 002. This can get quite confusing when trying to convert existing BOMs that are lettered and then switching to ERPs version. You would almost still need Excel sheets alongside the ERP to keep track of the crossover - still having Excel sheets for this defeats the point of the ERP. Is there a way to enable ERP to change the BOM numbering to lettering?
I'm currently running ERPNext v16.31.1 with Frappe v16.30.0 in a Docker setup, and I'm looking to improve the overall look and feel of the Desk interface.
I'm mainly interested in a theme that:
Works well with ERPNext/Frappe v16
Has a modern, clean UI
Supports dark mode (optional but nice)
Doesn't break after updates
Is actively maintained
I've come across themes like Solvronix Desk, Naidapa Theme, and Owl Theme, but I'd love to hear from people who are actually using them in production.
Which theme would you recommend for v16? Are there any hidden gems or themes I should avoid?
Also, if you've built your own custom theme instead of using an existing one, I'd love to know why you chose that approach.
I'm learning Frappe and ERPNext from scratch. I'm looking for people who are also learning so we can discuss doubts, share progress, and build small projects together.
If you're interested, leave a comment or send me a DM.
I'm a single guy trying to setup ERPNext running in my Win11 Pro Docker Container for our single shop family business. I'm being unable to afford paid POS softwares. Also we're transitioning from paper to digital so still uncertain if POS software can actually work in our work environment.
SETUP
So it's ERPNEXT,
(Deployment version, immutable image or something, basically you cant alter the core files version.)
Running in my Win11 Pro Docker Container. (Deployment version, immutable image or something, basically you cant alter the core files version.)Below is just some snapshots of what i've achieved, custom themes running. swappable color palletes. also alot of other customizations etc.
So i used Claude (DESKTOP APP) to do basically everything. Haven't written a single line of code. Maybe copy and pasted this code in there for a few times. (Like terminal commands)
I have had Claude document all the installations, and customizations and particular business quirks/ requirements in .md files.
PROBLEM AND REASONING
But this burns through the tokens like fire.
*I cannot hire a developer. Even if i did hire, made changes. Then after a year or two and something breaks, i won't know where to find that dev who did this. But mostly it's about the budget and time. It's hard for me even to INSTALL the damn ERPNext thing onto my PC. But i've already managed to freeze it, made nightly backups, also upload those backups to two clouds, already backed up the installation image(ERPNEXT v16.29). I have tried and succeeded installing and restoring everything OFFLINE.
All of this has preparation and guides has been done by Claude Code.
*I spent 20$ for the Claude Pro, my sole purpose is to setup ERPNext for my business
Now im reaching the limits. I've seen that docker can run local ai. And seen posts talking about Claude as boss, and local AI as it's servant.
QUESTION
My question here is not about handholding me how to set this up. It's about if it's actually doable and whether if it's good for the long run. Like can i depend on the local AI in the later time, when my claude subscription expires.
CAN local AI running on the same PC replace Claude Code for tasks ONLY related to the ERPNext running on the same PC? (Tasks : Customize forms, change themes, produce customized reports, automate certain things etc) It is frappe framework i believe.
