Vibecode ERPNext
track this build5 steps, step by step0%NOT REALLY · don't bother
ERPNext is not one app, it is roughly a dozen interlocking ones: a double entry ledger, stock with valuation methods, bills of material, purchase and sales cycles, payroll, and reports that accountants and auditors expect to look a certain way. An agent can absolutely one-shot the shape of any single module, and the result will feel great until you post a credit note, revalue stock, or try to close a fiscal year. The deeper joke is that the software is already free: the code is open source and self-hostable, so rebuilding it from scratch is the one move that makes no sense. If you pay, you are paying Frappe for hosting, upgrades and someone to call. The honest DIY option is either running ERPNext yourself or building a deliberately tiny ledger for one small business and accepting it will never be an ERP.
the project pack4 files · fastest path to a working personal build
You are building a lean indie version of ERPNext. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # ERPNext indie build ## Goal Build the smallest trustworthy replacement for the core ERPNext workflow for one developer or a tiny team. ## Scope A self-hosted mini ledger: items, contacts, sales and purchase invoices, payments, stock on hand, and correct double entry behind it all with P&L and balance sheet. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - Manufacturing: bills of material, work orders, capacity planning, none of it - Payroll, leave, expense claims and the statutory reports that go with them - Tax templates, multi-currency, and country specific compliance packs that took years to accumulate - Upgrades, migrations and a support contract when the ledger disagrees with the bank - The ecosystem: apps, integrations, consultants who already know the data model If those capabilities are essential, use ERPNext instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build brief Build a small self-hosted bookkeeping and stock app for a one-person business. This is NOT an ERP replacement and should not pretend to be one. Stack, no substitutions: - Python 3.12, Django 5, SQLite, Django admin as the primary UI - Plain Django templates for the few custom pages, no JS framework - Run with `python manage.py runserver`, no Docker, no cloud, no accounts, no telemetry - Secrets (SECRET_KEY only) read from .env via python-dotenv, ship .env.example Data model: - Account (code, name, type: asset/liability/equity/income/expense) - JournalEntry (date, memo) with JournalLine (account, debit, credit); enforce that each entry balances to zero at save time and refuse to save if it does not - Party (customer or supplier, single model with a flag) - Item (sku, name, unit, sale price, purchase price, current qty) - SalesInvoice and PurchaseInvoice, each with lines (item, qty, unit price); posting an invoice generates the matching JournalEntry and adjusts Item qty - Payment (party, date, amount, direction) that also posts a JournalEntry Behaviour: - Seed a minimal chart of accounts on first migrate: Cash, Bank, Accounts Receivable, Accounts Payable, Sales, Purchases, Inventory, Owner Equity - Invoices are draft or posted; posted invoices are immutable, corrections happen via a credit note that posts a reversing entry - Inventory valuation is simple average cost, and say so plainly in the UI Reports as read-only pages: - Trial balance for a date range - Profit and loss for a date range - Balance sheet as of a date - Stock on hand with average cost value - Each report has a CSV download Explicitly out of scope, do not build: manufacturing, payroll, multi-currency, tax engines, multi-user permissions, approval workflows, email sending. Deliver README.md with setup in under five commands, a seed script that loads a few months of fake invoices and payments, and pytest tests covering: unbalanced entries are rejected, posting an invoice moves stock and hits the ledger, and the balance sheet actually balances. ## Required capabilities - Python 3.12 and a machine that stays on - Willingness to keep your own backups - An accountant who will look at the numbers before you trust them ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a lean indie version of ERPNext. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # ERPNext indie build ## Goal Build the smallest trustworthy replacement for the core ERPNext workflow for one developer or a tiny team. ## Scope A self-hosted mini ledger: items, contacts, sales and purchase invoices, payments, stock on hand, and correct double entry behind it all with P&L and balance sheet. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - Manufacturing: bills of material, work orders, capacity planning, none of it - Payroll, leave, expense claims and the statutory reports that go with them - Tax templates, multi-currency, and country specific compliance packs that took years to accumulate - Upgrades, migrations and a support contract when the ledger disagrees with the bank - The ecosystem: apps, integrations, consultants who already know the data model If those capabilities are essential, use ERPNext instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build brief Build a small self-hosted bookkeeping and stock app for a one-person business. This is NOT an ERP replacement and should not pretend to be one. Stack, no substitutions: - Python 3.12, Django 5, SQLite, Django admin as the primary UI - Plain Django templates for the few custom pages, no JS framework - Run with `python manage.py runserver`, no Docker, no cloud, no accounts, no telemetry - Secrets (SECRET_KEY only) read from .env via python-dotenv, ship .env.example Data model: - Account (code, name, type: asset/liability/equity/income/expense) - JournalEntry (date, memo) with JournalLine (account, debit, credit); enforce that each entry balances to zero at save time and refuse to save if it does not - Party (customer or supplier, single model with a flag) - Item (sku, name, unit, sale price, purchase price, current qty) - SalesInvoice and PurchaseInvoice, each with lines (item, qty, unit price); posting an invoice generates the matching JournalEntry and adjusts Item qty - Payment (party, date, amount, direction) that also posts a JournalEntry Behaviour: - Seed a minimal chart of accounts on first migrate: Cash, Bank, Accounts Receivable, Accounts Payable, Sales, Purchases, Inventory, Owner Equity - Invoices are draft or posted; posted invoices are immutable, corrections happen via a credit note that posts a reversing entry - Inventory valuation is simple average cost, and say so plainly in the UI Reports as read-only pages: - Trial balance for a date range - Profit and loss for a date range - Balance sheet as of a date - Stock on hand with average cost value - Each report has a CSV download Explicitly out of scope, do not build: manufacturing, payroll, multi-currency, tax engines, multi-user permissions, approval workflows, email sending. Deliver README.md with setup in under five commands, a seed script that loads a few months of fake invoices and payments, and pytest tests covering: unbalanced entries are rejected, posting an invoice moves stock and hits the ledger, and the balance sheet actually balances. ## Required capabilities - Python 3.12 and a machine that stays on - Willingness to keep your own backups - An accountant who will look at the numbers before you trust them ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a production product version of ERPNext. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== PRODUCT.md ===== # ERPNext product brief ## Problem ERPNext is not one app, it is roughly a dozen interlocking ones: a double entry ledger, stock with valuation methods, bills of material, purchase and sales cycles, payroll, and reports that accountants and auditors expect to look a certain way. An agent can absolutely one-shot the shape of any single module, and the result will feel great until you post a credit note, revalue stock, or try to close a fiscal year. The deeper joke is that the software is already free: the code is open source and self-hostable, so rebuilding it from scratch is the one move that makes no sense. If you pay, you are paying Frappe for hosting, upgrades and someone to call. The honest DIY option is either running ERPNext yourself or building a deliberately tiny ledger for one small business and accepting it will never be an ERP. ## Product outcome A self-hosted mini ledger: items, contacts, sales and purchase invoices, payments, stock on hand, and correct double entry behind it all with P&L and balance sheet. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - Python 3.12 and a machine that stays on - Willingness to keep your own backups - An accountant who will look at the numbers before you trust them ## Explicit non-goals for v1 - Manufacturing: bills of material, work orders, capacity planning, none of it - Payroll, leave, expense claims and the statutory reports that go with them - Tax templates, multi-currency, and country specific compliance packs that took years to accumulate - Upgrades, migrations and a support contract when the ledger disagrees with the bank - The ecosystem: apps, integrations, consultants who already know the data model ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees. ===== ARCHITECTURE.md ===== # Architecture ## Starting brief Build a small self-hosted bookkeeping and stock app for a one-person business. This is NOT an ERP replacement and should not pretend to be one. Stack, no substitutions: - Python 3.12, Django 5, SQLite, Django admin as the primary UI - Plain Django templates for the few custom pages, no JS framework - Run with `python manage.py runserver`, no Docker, no cloud, no accounts, no telemetry - Secrets (SECRET_KEY only) read from .env via python-dotenv, ship .env.example Data model: - Account (code, name, type: asset/liability/equity/income/expense) - JournalEntry (date, memo) with JournalLine (account, debit, credit); enforce that each entry balances to zero at save time and refuse to save if it does not - Party (customer or supplier, single model with a flag) - Item (sku, name, unit, sale price, purchase price, current qty) - SalesInvoice and PurchaseInvoice, each with lines (item, qty, unit price); posting an invoice generates the matching JournalEntry and adjusts Item qty - Payment (party, date, amount, direction) that also posts a JournalEntry Behaviour: - Seed a minimal chart of accounts on first migrate: Cash, Bank, Accounts Receivable, Accounts Payable, Sales, Purchases, Inventory, Owner Equity - Invoices are draft or posted; posted invoices are immutable, corrections happen via a credit note that posts a reversing entry - Inventory valuation is simple average cost, and say so plainly in the UI Reports as read-only pages: - Trial balance for a date range - Profit and loss for a date range - Balance sheet as of a date - Stock on hand with average cost value - Each report has a CSV download Explicitly out of scope, do not build: manufacturing, payroll, multi-currency, tax engines, multi-user permissions, approval workflows, email sending. Deliver README.md with setup in under five commands, a seed script that loads a few months of fake invoices and payments, and pytest tests covering: unbalanced entries are rejected, posting an invoice moves stock and hits the ledger, and the balance sheet actually balances. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it. ===== AGENTS.md ===== # Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone. ===== MILESTONES.md ===== # Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations. ===== OPERATIONS.md ===== # Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted ERPNext capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
README.md
# ERPNext indie build ## Goal Build the smallest trustworthy replacement for the core ERPNext workflow for one developer or a tiny team. ## Scope A self-hosted mini ledger: items, contacts, sales and purchase invoices, payments, stock on hand, and correct double entry behind it all with P&L and balance sheet. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - Manufacturing: bills of material, work orders, capacity planning, none of it - Payroll, leave, expense claims and the statutory reports that go with them - Tax templates, multi-currency, and country specific compliance packs that took years to accumulate - Upgrades, migrations and a support contract when the ledger disagrees with the bank - The ecosystem: apps, integrations, consultants who already know the data model If those capabilities are essential, use ERPNext instead of pretending the gap is solved.
AGENTS.md
# Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs".
BUILD_PLAN.md
# Build plan ## Original build brief Build a small self-hosted bookkeeping and stock app for a one-person business. This is NOT an ERP replacement and should not pretend to be one. Stack, no substitutions: - Python 3.12, Django 5, SQLite, Django admin as the primary UI - Plain Django templates for the few custom pages, no JS framework - Run with `python manage.py runserver`, no Docker, no cloud, no accounts, no telemetry - Secrets (SECRET_KEY only) read from .env via python-dotenv, ship .env.example Data model: - Account (code, name, type: asset/liability/equity/income/expense) - JournalEntry (date, memo) with JournalLine (account, debit, credit); enforce that each entry balances to zero at save time and refuse to save if it does not - Party (customer or supplier, single model with a flag) - Item (sku, name, unit, sale price, purchase price, current qty) - SalesInvoice and PurchaseInvoice, each with lines (item, qty, unit price); posting an invoice generates the matching JournalEntry and adjusts Item qty - Payment (party, date, amount, direction) that also posts a JournalEntry Behaviour: - Seed a minimal chart of accounts on first migrate: Cash, Bank, Accounts Receivable, Accounts Payable, Sales, Purchases, Inventory, Owner Equity - Invoices are draft or posted; posted invoices are immutable, corrections happen via a credit note that posts a reversing entry - Inventory valuation is simple average cost, and say so plainly in the UI Reports as read-only pages: - Trial balance for a date range - Profit and loss for a date range - Balance sheet as of a date - Stock on hand with average cost value - Each report has a CSV download Explicitly out of scope, do not build: manufacturing, payroll, multi-currency, tax engines, multi-user permissions, approval workflows, email sending. Deliver README.md with setup in under five commands, a seed script that loads a few months of fake invoices and payments, and pytest tests covering: unbalanced entries are rejected, posting an invoice moves stock and hits the ledger, and the balance sheet actually balances. ## Required capabilities - Python 3.12 and a machine that stays on - Willingness to keep your own backups - An accountant who will look at the numbers before you trust them ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden.
.env.example
# Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
PRODUCT.md
# ERPNext product brief ## Problem ERPNext is not one app, it is roughly a dozen interlocking ones: a double entry ledger, stock with valuation methods, bills of material, purchase and sales cycles, payroll, and reports that accountants and auditors expect to look a certain way. An agent can absolutely one-shot the shape of any single module, and the result will feel great until you post a credit note, revalue stock, or try to close a fiscal year. The deeper joke is that the software is already free: the code is open source and self-hostable, so rebuilding it from scratch is the one move that makes no sense. If you pay, you are paying Frappe for hosting, upgrades and someone to call. The honest DIY option is either running ERPNext yourself or building a deliberately tiny ledger for one small business and accepting it will never be an ERP. ## Product outcome A self-hosted mini ledger: items, contacts, sales and purchase invoices, payments, stock on hand, and correct double entry behind it all with P&L and balance sheet. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - Python 3.12 and a machine that stays on - Willingness to keep your own backups - An accountant who will look at the numbers before you trust them ## Explicit non-goals for v1 - Manufacturing: bills of material, work orders, capacity planning, none of it - Payroll, leave, expense claims and the statutory reports that go with them - Tax templates, multi-currency, and country specific compliance packs that took years to accumulate - Upgrades, migrations and a support contract when the ledger disagrees with the bank - The ecosystem: apps, integrations, consultants who already know the data model ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees.
ARCHITECTURE.md
# Architecture ## Starting brief Build a small self-hosted bookkeeping and stock app for a one-person business. This is NOT an ERP replacement and should not pretend to be one. Stack, no substitutions: - Python 3.12, Django 5, SQLite, Django admin as the primary UI - Plain Django templates for the few custom pages, no JS framework - Run with `python manage.py runserver`, no Docker, no cloud, no accounts, no telemetry - Secrets (SECRET_KEY only) read from .env via python-dotenv, ship .env.example Data model: - Account (code, name, type: asset/liability/equity/income/expense) - JournalEntry (date, memo) with JournalLine (account, debit, credit); enforce that each entry balances to zero at save time and refuse to save if it does not - Party (customer or supplier, single model with a flag) - Item (sku, name, unit, sale price, purchase price, current qty) - SalesInvoice and PurchaseInvoice, each with lines (item, qty, unit price); posting an invoice generates the matching JournalEntry and adjusts Item qty - Payment (party, date, amount, direction) that also posts a JournalEntry Behaviour: - Seed a minimal chart of accounts on first migrate: Cash, Bank, Accounts Receivable, Accounts Payable, Sales, Purchases, Inventory, Owner Equity - Invoices are draft or posted; posted invoices are immutable, corrections happen via a credit note that posts a reversing entry - Inventory valuation is simple average cost, and say so plainly in the UI Reports as read-only pages: - Trial balance for a date range - Profit and loss for a date range - Balance sheet as of a date - Stock on hand with average cost value - Each report has a CSV download Explicitly out of scope, do not build: manufacturing, payroll, multi-currency, tax engines, multi-user permissions, approval workflows, email sending. Deliver README.md with setup in under five commands, a seed script that loads a few months of fake invoices and payments, and pytest tests covering: unbalanced entries are rejected, posting an invoice moves stock and hits the ledger, and the balance sheet actually balances. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.
AGENTS.md
# Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone.
MILESTONES.md
# Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.
OPERATIONS.md
# Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted ERPNext capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
$ choose a build depth, inspect the files, then open the complete pack in your agent · this prompt is generated from the build plan · improve it via PR
Because the price of ERPNext is not the software, it is the certainty. Businesses running real stock and real payroll are buying hosting they do not maintain, upgrades that do not break the ledger, and a support channel for the day something reconciles wrong. Self-hosting ERPNext is genuinely viable and plenty of people do it, but the moment the system is load bearing for invoicing or wages, paying someone else to own uptime and version upgrades looks cheap. A hand-built replacement inverts that: you become the vendor, on call, forever.
xManufacturing: bills of material, work orders, capacity planning, none of it
xPayroll, leave, expense claims and the statutory reports that go with them
xTax templates, multi-currency, and country specific compliance packs that took years to accumulate
xUpgrades, migrations and a support contract when the ledger disagrees with the bank
xThe ecosystem: apps, integrations, consultants who already know the data model
Nothing worth pointing at. That's why the prompt exists.
share on X ↗"I just replaced ERPNext ($5/mo) with one prompt"
Vibecode ERPNext
Not really. ERPNext's value is not the code: The moat is a decade and a half of accounting, tax and inventory edge cases, plus the switching costs of every business that already keeps its stock and ledger inside it. See the honest breakdown above.
How much does ERPNext cost?
ERPNext costs about $5/month (Frappe Cloud Sites (shared), checked 2026-08-18), which is $60 per year.
What do I lose by replacing ERPNext?
Honestly: Manufacturing: bills of material, work orders, capacity planning, none of it; Payroll, leave, expense claims and the statutory reports that go with them; Tax templates, multi-currency, and country specific compliance packs that took years to accumulate; Upgrades, migrations and a support contract when the ledger disagrees with the bank; The ecosystem: apps, integrations, consultants who already know the data model. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to ERPNext?
No mature open-source alternative worth pointing at, which is exactly why the one-shot prompt on this page exists.