ERP & Business Apps solution
Run ERPNext Locally with FlyEnv
ERPNext environments can combine Python, MariaDB, Redis, a web server, and frontend tooling. FlyEnv helps manage these related local services around the ERPNext project.
Local project stack
Services FlyEnv can manage around ERPNext
About ERPNext
ERPNext is an open-source ERP built on the Frappe Framework for accounting, sales, inventory, manufacturing, HR, and operational workflows. Its model is based on configurable DocTypes, role-aware forms, reports, and business processes rather than a standalone Python request server alone.
Local development uses Bench to manage sites, Python environments, assets, workers, and process commands. A normal stack includes MariaDB and Redis; Node.js is used for asset workflows, while a scheduler, Socket.IO process, and worker queues are part of the Frappe process model.
Core capabilities
- DocTypes
- Accounting ledger
- Inventory workflows
- Reports and print formats
- Role permissions
- Frappe Bench
Common use cases
- Accounting and invoicing
- Inventory and procurement
- Manufacturing operations
- HR and payroll workflows
- Custom business applications on Frappe
ERPNext development is a Bench-managed multi-process stack
Unlike a simple Python site, a local bench coordinates the site database, Redis-backed queues, assets, workers, and scheduler.
- Bench and Python environment
- Creates sites and runs Frappe or ERPNext commands such as `bench start`.
- MariaDB and Redis
- MariaDB stores site data; Redis supports cache, queues, and Socket.IO-related services.
- Workers, scheduler, and Socket.IO
- Process background jobs, scheduled documents, and realtime updates during realistic development.
- Node.js asset workflow
- Required by Bench asset building; it is not a replacement for ERPNext application processes.
Project resources
For installation commands, supported versions, and project-specific configuration, refer to the official ERPNext documentation.
Typical local stack
The exact services depend on the project, its release, and its local configuration. This is a common local setup, not a fixed requirement.
How FlyEnv helps
Manage the Python runtime
Keep the project runtime available alongside its services.
Run MariaDB and Redis
Keep core data and queue services together locally.
Use a local application URL
Configure domains and HTTPS when browser testing needs them.
Start the full stack together
Use a Startup Group for the multi-service environment.
Set up the local environment
Project installation stays with the upstream documentation. FlyEnv manages the runtimes, databases, web servers, and supporting services around it.
- 1Follow ERPNext documentation for the project installation and bench workflow.
- 2Select the Python runtime required by the project release.
- 3Start MariaDB and Redis for the services the project uses.
- 4Keep Node.js available when the selected build workflow needs it.
- 5Configure the local web server, domain, and HTTPS in FlyEnv.
- 6Save the application services in a Startup Group for repeatable starts.
Watch the demo
Run ERPNext and its Frappe services together as a managed local stack.
Run ERPNext locallyRelated solutions
Ready to run ERPNext locally?
Use FlyEnv to manage the runtimes, databases, web servers, and services around your local ERPNext environment.