Support that every
role can move faster on.
billetsys is an open-source support ticket system that keeps the whole case — status, ownership, conversation, attachments, and product context — in one record. Five roles, one shared model, a focused screen for each.
One record for
the whole case.
Instead of splitting status, ownership, communication, and files across different tools, billetsys keeps them connected to the same ticket — from the first report through investigation to final resolution.
Built around roles
User, Superuser, TAM, Support, and Admin each get a focused view — plus an External Contributor stub for third parties who reply by email.
Conversation in context
Public and private message threads live on the ticket, with role-scoped visibility and a Markdown editor for rich replies.
Email that stays in sync
Outgoing notifications, an incoming mail endpoint, and IMAP/POP3 polling all feed the same ticket history.
Scoped and secure
Role-based authorization, session handling, captcha-protected flows, and TLS 1.3 throughout.
Five roles,
one support process.
The role model separates customer-facing work from operational support and system administration, so every screen stays focused on what matters for that role. Each role carries its own customizable badge throughout the app.
Create tickets, follow progress, and exchange messages with support.
SuperuserA customer-side power user coordinating tickets across a company scope.
TAMTechnical Account Manager tracking customer activity across companies.
SupportWork the queue, update assignments, and reply with attachments.
AdminManage companies, users, categories, entitlements, and reference data.
External ContributorA stub role for third parties who receive and reply to tickets by email.
Everything a support team needs.
Full case lifecycle
Status, assignment, category, entitlement, versions, ratings, and external issue references on every ticket.
MessagesPublic & private threads
Reply in the open or keep notes private to your role group, all in the ticket history.
KnowledgeArticles & search
A shared knowledge base with tags and a global Ctrl+K search across tickets and articles.
Two-way email
Notifications out, plus incoming mail via an endpoint or IMAP/POP3 polling into the same ticket.
MigrationCSV ticket import
Bulk-onboard a backlog from another helpdesk; the framework extends to Jira and Bugzilla.
ExportPDF documents
Turn tickets and reports into portable documents for archiving, review, and sharing.
The latest release.
- Role badges — Each role is distinguished by a customizable icon and color.
- Ticket & article references — Cross-reference and mention across records.
- CSV import — Bulk-onboard tickets from external helpdesks.
- Markdown editor — Rich content for messages and articles.
- Email integration — Incoming endpoint and mailbox polling.
- TLS 1.3 — Secure transport throughout.
Quarkus, PostgreSQL,
React & TypeScript.
A Quarkus backend on Java 25 talks to PostgreSQL, while a React + TypeScript frontend built with Vite uses shadcn/ui and Tailwind CSS. Build it with Maven and Make.
The complete manual.
Introduction
What billetsys is, the ticket lifecycle, roles, communication, and knowledge.
GuideGetting Started
Set up PostgreSQL, start support services, and run the app in dev mode.
ReferenceRoles
User, Superuser, TAM, Support, Admin, and the External Contributor stub.
ReferenceTickets
Core information, the lifecycle, and how a case is followed end to end.
ReferenceOutgoing notifications, incoming mail, and mailbox polling.
ReferenceSecurity
Authentication, authorization, sessions, and password protection.
Free to use,
free to modify.
billetsys is released under the Eclipse Public License v2.0. Use it, fork it, contribute back — no subscriptions and no vendor lock-in.
Running billetsys ?
mnemosyne systems offers support contracts for companies that depend on billetsys. Direct access to the maintainers, priority response and development.