Customer portal
Customers open tickets, follow replies, and keep their support history in one place.
What it does
Tickets, replies, files, and ownership.
Staff workflow
Staff assign tickets, set priorities, filter queues, and close requests when the support work is done.
Chat-style replies
Public replies, internal notes, unread markers, pasted files, and inline previews fit the conversation flow.
Admin control
Manage products, customers, staff accounts, API tokens, webhooks, audit events, and maintenance.
Agentic?
AI-ready, without built-in AI.
Pappice does not ship a bot or pick an AI provider. You create a normal account, assign the product role you want, and issue an API token. The token inherits that account's permissions, so an external agent can act only inside the boundaries you choose.
For review-first workflows, the Internal contributor role is the narrow option: it can read tickets and add internal notes, but it cannot send public replies or edit tickets.
How it works
One binary. One SQLite database.
Pappice is built for small VPS deployments: run the binary, point it at a writable data directory, and put HTTPS in front. Application state lives in SQLite, attachments stay on disk, and email/webhook work is stored durably before delivery. The operational shape stays boring enough to back up and understand.
- Built with Go 1.26+
- Embedded SQLite driver
- Embedded HTML, CSS, and JavaScript
- Small instances around 20-30 MB RAM
- Role-scoped API tokens
- Stable webhook delivery IDs
- Idempotent ticket writes
- Built-in backup and restore
Install and deploy
Use the latest release.
The deploy guide resolves the latest release tag and covers nginx, systemd, Docker Compose, backups, restore, and upgrades. You can also try the public demo first.