Tick& is a free, open-source and self-hostable ITSM ticketing platform designed for internal service desks: IT departments, public-sector IT services, and shared support teams. IT asset management is deliberately out of scope — there is no hardware inventory or license management.
What it covers
The full ITIL lifecycle: incidents and requests, problems, and changes, built on a common foundation of actors, unified timelines, tasks, solutions, approvals, and relationships between objects.
Service commitments (SLA and OLA) with business calendars, public holidays, reminders, and escalation. A four-hour deadline set on Friday at 5 PM falls on Monday, not Saturday.
A rule engine with a simulator: run a fictional ticket through the engine to see what a rule would do before applying it to a real ticket.
Knowledge base with a public FAQ, conditional catalog forms, satisfaction surveys, and a self-service portal.
Email notifications and inbound email collection, scheduling, statistics, and CSV/PDF exports.
What makes it different
Tenant isolation is enforced at the database level, not by the application. Organizations form a hierarchy, and isolation relies on PostgreSQL Row-Level Security rather than application-level WHERE conditions that developers can accidentally forget.
Permissions are defined as object × action × scope, and the absence of authorization means denial.
Permissions follow the active profile, never the union of profiles. Someone who is a technician at one site and a requester at headquarters does not inherit the combined permissions of both roles.
Extensible without forking: extensions are loaded into the process, declare their permissions through a versioned manifest, receive their own PostgreSQL schema, and can be removed without leaving behind database objects.
French and English from day one, covering both the interface and emails. Authentication supports local accounts as well as LDAP and Active Directory.
Installation
Tick& can be deployed using Docker — with published images and a provided Compose file — or using standalone archives for servers where container engines are not allowed, with a dedicated archive for each platform.
Dependencies: PostgreSQL and Redis.
Before using it
No service desk is currently using Tick& in production. A public demonstration environment runs continuously on the published images, exercising the deployment path every day, but no real support tickets have been handled there.
Version 0.1 is tagged, but not yet battle-tested: breaking changes between minor versions should be expected until the interfaces have been exercised by users other than the author.
Try it without installing anything: https://tick-demo.tickand.fr
Five demo accounts are available on the login screen, one for each profile. The environment is reset every hour.
EU
tick0001 
