English
Peppermint Hosting
Run a self-hosted help desk: collect support tickets, assign them to agents, and track them to resolution.
No setup fees-
One click deploy -
1 GB RAM Memory needed -
15 GB Disk Space Needed -
From 2 € Price
Official links
Peppermint’s official links and original website
Peppermint Website
More
Tech
- Docker image
- pepperlabs/peppermint:latest
- Default port
- 3000
- Database
- postgres
How Peppermint works
Peppermint organises support work around tickets linked to clients and assigned agents. A ticket can carry a description, priority, status, comments, notes, and attachments, giving the team one record for the issue and its handling history. Client pages bring related requests together for easier reference.
The interface also provides agent and administrative functions for managing access and service activity. The catalogue uses a known default administrator login, which must be changed immediately. More importantly, the official Peppermint repository was archived on 17 July 2026 and is read-only, so future maintenance, security fixes, and compatibility work should not be assumed.
Key Peppermint features
A compact ticket queue can replace informal support requests spread across chat messages or spreadsheets. Priorities and statuses make work visible, while notes and attachments retain the context used to resolve an issue. Client history helps an agent understand whether a new request relates to an earlier problem.
The hosted configuration cannot use inbound email, outbound notifications, or email recovery because application email is disabled. Combined with the archived upstream, that makes Peppermint a poor choice for a critical public help desk. Evaluate it with non-sensitive data and maintain a clear export or replacement plan.
Peppermint vs Zendesk
Peppermint is a compact self-hosted ticket and client workspace whose upstream repository is now archived. Zendesk is a provider-managed customer-service platform spanning ticketing, messaging, voice, help-centre content, analytics, workforce functions, administration, and a large integration marketplace.
Zendesk may suit organisations that require an actively maintained commercial service, multiple customer channels, vendor support, and enterprise administration. Peppermint may still be useful for examining a simple ticket workflow, but the archived codebase and disabled application email materially limit its suitability for operational support.
Who uses Peppermint
Small internal teams can use Peppermint to test ticket ownership, priorities, client records, notes, and attachments. Developers may inspect it as a reference implementation, while organisations considering migration can evaluate whether its compact workflow covers the records they need.
Do not select Peppermint for a mission-critical queue without accepting the project-status risk. The operator should change the default password, restrict access, avoid sensitive production data, test exports, and define how tickets would be moved if the image stops receiving compatible or secure upstream releases.
Self-hosting Peppermint: requirements and cost
Peppermint load depends on tickets, clients, agents, attachments, notes, searches, concurrent sessions, and PostgreSQL activity. PostgreSQL stores tickets, clients, agents, comments, notes, attachments, statuses, priorities, and application settings. Peppermint database memory is separate from the exported application figure, which activates the approved plan adjustment.
AvaHost maps Peppermint to Plan 2 at €5. The one-click Peppermint stack includes PostgreSQL, which remains unmanaged by AvaHost. Peppermint includes automated HTTPS on a custom domain, application updates, and scheduled backups. Change the default administrator password immediately. Application email is disabled, so email ticket intake, notifications, and password recovery are unavailable; the archived upstream status also requires a replacement and data-export plan.
F.A.Q
Peppermint starts at €5 on Plan 2 after capacity is added for PostgreSQL. The plan can support a modest evaluation queue, but ticket volume, attachments, agents, searches, and concurrent sessions affect demand. The upstream repository is archived, so cost should not be the deciding factor for a critical support deployment.
AvaHost provisions PostgreSQL for tickets, clients, agents, notes, comments, attachments, priorities, statuses, and settings. Peppermint receives PostgreSQL with the stack, but database administration remains the operator’s responsibility. Preserve the database, uploaded files, application secret, and administrator account together, and test an export because the archived upstream creates a higher migration and maintenance risk.
Peppermint can run on a custom hostname with automated HTTPS after DNS points to AvaHost. Restrict access where possible, change the default `admin@admin.com` password immediately, and avoid exposing a test queue publicly. After a domain change, verify sign-in, attachments, client pages, ticket links, and any stored absolute URLs.
The official Peppermint repository was archived and made read-only in July 2026, so continued fixes and compatibility work should not be assumed. AvaHost also disables application email, removing inbound email tickets, notifications, and email recovery. Use it only where those risks are acceptable and a tested migration path exists.