django-helpdesk

Azure Applications 1 variation

django-helpdesk is an open source ticket tracker for support teams, with queues, a public web portal for raising and tracking tickets, a knowledge base and a staff interface.

Base
Hardened build
minimal ports, security patches applied at build time
Access
Unique credentials
generated on first boot, readable only by root
Verified
Boots working
services pass a health gate before release
Support
24/7, 365 days
by email and live chat, 24 hour response SLA

Variations

This product is available in the build below. Open it for the operating system, cloud and version detail, or read its deployment guide.

ProductCloudOperating systemVersion
django-helpdesk on Ubuntu 24.04 Azure Ubuntu 24.04 Standard View · Guide

Overview

django-helpdesk is a mature open source ticket tracker and helpdesk built on the Django web framework. Requests arrive into queues that carry their own priorities and escalation rules, and anyone can raise a ticket and follow its progress from a public web portal without being given an account. Support staff sign in to a dashboard, filter and search the ticket list, take ownership of work, add public or private follow ups, record time spent and resolve tickets, while a searchable knowledge base answers the questions that come up again and again.

Attachments, saved searches, reporting and a REST API round it out, so it suits an internal IT or facilities team, a customer support desk, or any organisation that wants a self hosted ticket system it controls entirely inside its own cloud account rather than a hosted service.

Why the cloudimg image

cloudimg delivers django-helpdesk as a complete appliance rather than a Python library you have to build a project around: it is installed at a pinned upstream release into a dedicated virtual environment, hosted by a production Django project, served by gunicorn behind an nginx reverse proxy and backed by PostgreSQL on the same instance, with two ready made queues and a knowledge base article already configured so the portal takes tickets the moment first boot finishes. The appliance is self contained and needs no mail server: email is entirely optional configuration. Security is the reason to take this image rather than assemble it yourself. No credential of any kind ships, not even a placeholder, and nothing is listening on the public port in the image at all, so there is no window in which a fresh instance is reachable with a known password. First boot generates a unique Django secret key, a unique database password and a unique staff password into a root only file, and only then brings the public site up. Sign in details are never written to the system journal or the authentication log. Every deployment is paired with a step by step deploy guide and backed by 24/7 cloudimg support.

Common uses

  • Run an internal IT or facilities support desk with queues and priorities
  • Let people raise and track tickets from a public portal with no account
  • Answer repeat questions from a searchable staff maintained knowledge base