Summary
Project-management software for organisations that run very different kinds of projects. Projects nest to any depth, each with its own board, workflow, fields and permissions, so the same product can be shaped to fit the work rather than the other way round.
What EnzeMeta is
Most project tools assume a fixed shape: a project, a board, some tasks. Real organisations do not fit that shape. A consultancy runs technical and non-technical projects side by side; other organisations break work down into phases, sites or buildings. EnzeMeta was designed so the same software can represent all of them.
Designed for reuse
The adaptability is in the product itself, not in custom builds.
- Projects nest to any depth and can be viewed as a tree or a graph
- Each project has its own statuses, categories, priorities and a Kanban board
- Custom fields in eleven types, from text and dates to selections and people
- Project templates that copy structure, workflow and members to start new work quickly
- Organisation-level terminology, so "Projects" can become "Cases" or anything else
- Fine-grained permissions per project and per status, including time-limited guest access
Day-to-day work
Around that core sit the features teams use daily: assignments with due dates, multiple assignees, comments and mentions; files; project and personal calendars; a "My Work" view; an audit trail; and real-time notifications with deadline reminders. The interface is available in English and Macedonian, with guided tours for new users.
Engineering behind it
Unbounded hierarchies are easy to draw and hard to get right. Permissions are inherited down the tree without being copied to every level, list views must agree with direct access checks, a project can never be moved under its own descendant, and traversal is iterative so that deep trees do not exhaust the stack. Each of these is covered by tests.