Project management · By MithTech
Open sourceSprints on the ERPNext you already runPulse, agile project management for ERPNext
Pulse adds a board, sprints, OKRs and retros to ERPNext's own Projects and Tasks. Open source; we can install and run it for you.
MIT licence. Run it yourself, or we run it for you.
Works with what you run?
Your records end up in ERPNext's own Projects and Tasks, set up beside what you run.
What Pulse does
Sprints with a backlog
Plan the sprint from the backlog; it closes itself on its end date.
- We set it up Needs ERPNext: we set up ERPNext Projects beside what you run.
- Ends up as a Pulse Sprint holding ERPNext Tasks.
A board on your own tasks
Drag a card and the ERPNext Task moves; everyone sees it live. ERPNext alone has a status board, not sprints.
- We set it up Needs ERPNext: we set up ERPNext Projects beside what you run.
- Ends up as the Task's Board State.
Partly built
Epics and releases
Group tasks under an epic and label each task with its release.
- An epic is a task that groups tasks; a release is a label, not a record.
- We set it up Needs ERPNext: we set up ERPNext Projects beside what you run.
- Ends up as fields on the Task.
OKRs, risks and retros
Objectives with check-ins, a risk register, retrospectives and change requests beside the board.
- We set it up Needs ERPNext: we set up ERPNext Projects beside what you run.
- Ends up as Objectives, Risks and Retrospectives.
Burndown, velocity and more
Burndown, burnup, velocity, cumulative flow and cycle time, read from the same tasks.
- We set it up Needs ERPNext: we set up ERPNext Projects beside what you run.
- Ends up as a report on the sprint.
Hours on the task, cost on the project
Time logged on a task reaches ERPNext's project costing and can be billed.
- We set it up Needs ERPNext: we set up ERPNext Projects beside what you run.
- Ends up as a Timesheet on the project.
One task, from the backlog to the burndown
BacklogComplete
SHOP-11, "Returns page for the shop", is pulled into the team's sprint.
BoardComplete
It moves to In Review, then Done: each move is the Task's Board State in ERPNext.
HoursComplete
An hour logged on it lands in a Timesheet on the project.
BurndownComplete
The sprint's burndown counts it done today.
Where Pulse stops
Going live: who does what
Tell us how the team plans work today: Jira, a sheet or a board.
Install Pulse on your ERPNext site: it's MIT, so either of us can.
Bring projects and issues over as ERPNext Projects and Tasks, with keys.
Run one sprint on it; we stay on call.
Support and upgrades with your ERPNext, as long as you want them.
Who you pay, for what
- Pulse
- Nothing: it's open source under the MIT licence.
- Your host or Frappe Cloud
- Hosting: the same site as your ERPNext.
- MithTech
- Set-up, moving your work over and support, in a written proposal.
What you own
Your projects and tasks were ERPNext records all along: remove Pulse and they stay. The code is MIT: read it, fork it or run it without us.
Questions about Pulse
No. ERPNext's Projects module gives tasks a Kanban, Gantt and calendar view, but no sprints, backlog, epics, OKRs or retrospectives. Pulse adds those on the same Project and Task records, so a sprint board and the project's hours and costs live in one database. If you only need a status board, ERPNext's own Kanban may be enough.
Yes. Pulse is a Frappe app that works on ERPNext's own Projects and Tasks; it adds fields and screens around them rather than a separate database. That is the point: delivery data and business data stay in one system. If you run Tally or other books, we can set up ERPNext Projects beside them.
Pulse is open source under the MIT licence, and the code is public on GitHub. You can install it on your own ERPNext site, read every line, change it and run it with no contract with us. What we sell is the work around it: installing, shaping it to your team and keeping it running.
For sprint-based delivery on ERPNext, often yes: boards, sprints, epics, releases, the usual agile reports and OKRs are covered. Jira's plugin ecosystem is not, and there is no one-click importer. We map projects to ERPNext Projects and issues to Tasks, and name anything that has no counterpart before you decide.
They stay. Projects and tasks were ERPNext records all along, readable in ERPNext and exportable with its own tools. What leaves with Pulse is the board, the sprint model, the governance records and the reports. And because the licence is MIT, anyone can keep running Pulse without us.
Not yet. Gantt on the board, swimlanes with work-in-progress limits and a command palette are on Pulse's roadmap, not in the code today. ERPNext's own Gantt view of tasks still works alongside Pulse. If one of these decides it for you, tell us, and we'll say what it would take.