Projects, tasks and discussions on your server. Plan work, review results and keep the full context in each task.
Plans, progress and results, all on one board.
Keep the brief, decisions and results together. The project defines the workflow; the task holds the details.
Search by title and filter by project, stage or assignee. Switch between list and board while keeping your filters.
How tasks workMarkdown descriptions, discussions, checklists and attachments. Keep due dates, priority and participants alongside the task, with a history of changes.
Task detailsInvite colleagues by email and assign roles. Decide who can see projects, update tasks and accept work. Add individual permissions where needed.
Team and permissionsThe web interface saves prepared actions on your device. The queue shows what is waiting to send and what the server has confirmed. Conflicts are yours to resolve.
Saving and deliveryThese are the capabilities of the upcoming 0.1 release, planned for 9 November 2026. The demos use sample data without a tracker connection.
One installation serves a team with multiple projects. PostgreSQL, attachments and email settings stay on your infrastructure.
You manage deployment and backups
Connect GrigTasks through a dedicated driver to read, update and review tasks from GrigDesk. The tracker also works independently: its web interface and API do not require GrigDesk.
Capabilities and connectionThe driver is distributed separately. Files are available in the tracker’s web interface.The first release, 0.1, is planned for 9 November 2026. Packages and verified installation instructions will be published with the release. Documentation and a sample interface are available here now.
GrigTasks is a standalone product with its own server, database and web interface. A separate driver connects it to GrigDesk if you use both products.
On your server: data in PostgreSQL, attachments in the installation’s file storage. Your team manages access, updates and backups.
After the first successful visit, the web interface can use its saved shell and available local data. Prepared actions wait in the queue. Server confirmation is shown separately; conflicts need a manual decision. Invitations and team administration require a connection.
Yes. The API-only distribution supports custom clients and integrations. The full distribution adds the web interface to the same API. Both use a separate mail service.
While the release is being prepared, explore the tracker and its installation requirements.
Prepare for launchRelease in preparation