Aprocy
The PM tool where every task lives inside a process that runs.
- Role
- Design + Engineering
- Timeline
- Ongoing · 2026
- Stack
- React + Vite · NestJS · PostgreSQL · Railway
Tasks float. Processes don't.
Most PM tools are task lists with extra columns. The process behind the tasks (the order, the resources, the branching logic) lives in someone's head or a Notion doc nobody reads.
Aprocy inverts the model: a process is a first-class object, not a folder. Every task exists inside a process step. Every resource (a customer ID, a payment URL, an account handle) is typed and linked to the step that needs it. Every time you run a process, it creates a tracked instance with a full audit trail.
Processes as templates, runs as instances.
The hardest decision was separating the process definition from the execution. A process template is versioned. You can diff v2.4 against v2.5, roll back, write notes. A run is a live instance of that template: it tracks who is blocked, what values have been filled, and what percentage is complete.
This split keeps the template clean while giving operations teams the real-time view they actually need. The alternative, merging template and run into one object, is how most tools end up with a graveyard of half-done copies of the same checklist.
- MVP
- Live in pilot
- 80+
- Process templates
- 0
- Floating tasks
Aprocy is piloting with early teams. The typed resource registry turned out to be the feature that keeps people. Once a team has encoded their customer data model into a process template, the tool becomes load-bearing. The next milestone is analytics: closing the loop from run history to process improvement suggestions.