django-helpdesk

Django-based helpdesk for tickets, queues and support communication.

5 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

django-helpdesk public ticket access checks

The advisory describes a public ticket lookup that did not validate its secret key.

Scope: Versions 0.3.0–2.6.0; patched in 2.6.1 (GHSA-9g24-qf73-cjxh).

Affected public-ticket configuration can disclose a ticket to a visitor who knows the ID and submitter email; see the full advisory for conditions.

Action: Use django-helpdesk 2.6.1 or a later compatible fixed build and review the public ticket and non-staff permission settings.

Primary source · Reviewed 2026-11-19

What lands where

  1. Supplied by

    Vendor or project

    VM image

  2. Operated by

    Your team

    Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.

Deployment boundaries by provider
  • Azure: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    Microsoft Marketplace ↗ · Source checked 2026-11-19

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodVM image
InfrastructureServers / containers
Django application, database and persistent files in a cloudimg Azure VM. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.
Licensing modelOpen Source / Open Core
BSD-3-Clause for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
LicenseBSD-3-Clause for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

7 of 12 fields researched (58%) · 5 documented · 2 unresolved. Evidence coverage is not a feature score.

Marketplace delivery
AvailableEvidence and scope for Marketplace delivery

The official Microsoft catalog identifies this customer-subscription VirtualMachine offer from cloudimg. The publisher package and upstream application have separate maintenance.

django-helpdesk selected Azure public offer · Source ↗ · Offer cloudimg1647283583153.django-helpdesk-ubuntu-24-04 ↗ — cloudimg; Virtual machine · Reviewed 2026-11-19

Documented · Editor reviewed.

Cloud commitment eligibility
Not eligibleEvidence and scope for Cloud commitment eligibility

The reviewed Microsoft public-offer catalog sets isMacc to false. This finding applies to this software offer, not separately billed Azure infrastructure or another negotiated agreement.

cloudimg1647283583153.django-helpdesk-ubuntu-24-04 public offer, reviewed 2026-11-19 · Source ↗ · Reviewed 2026-11-19

Explicitly unsupported · Editor reviewed.

Single sign-on
Not confirmedEvidence and scope for Single sign-on

The published v2.6.1 package integrates Django users and login views, but its installation/settings material does not establish a specific SAML/OIDC identity-provider integration. Using Django authentication backends is a customization path, not confirmation that a marketplace image includes configured SSO. Verify the backend, callback and user/permission mapping.

Published Django application authentication hooks; external federation remains unconfirmed · Source ↗ · Published application login routes ↗ · Reviewed 2026-11-20

Sources checked — unresolved · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

The v2.6.1 standalone guide supplies a setup script and Compose stack; it separately documents installation as a package in an existing Django application. Configure database, secrets, mail, site URL, reverse proxy and production settings. The demo server and default demo credentials are not a production deployment.

Published standalone versus embedded Django installation · Source ↗ · Deployment artifact ↗ (v2.6.1) · Integration into an existing Django application ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Minimum footprint / sizing
Not confirmedEvidence and scope for Minimum footprint / sizing

The published installation material identifies the Python/Django application, database and production services but gives no complete CPU/RAM/storage minimum. Development/demo allocations do not establish capacity for ticket mail, attachments, concurrency or HA; obtain a workload-specific sizing plan for the selected image/version.

Published application topology; numeric production sizing remains unconfirmed · Source ↗ · Reviewed 2026-11-20

Sources checked — unresolved · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

BSD-3-Clause for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

django-helpdesk; software terms only, excluding cloud charges, labour and separately licensed services · Source ↗ · Reviewed 2026-11-19

Documented · Editor reviewed.

Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence

Reviewed upstream v2.6.1 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence.

django-helpdesk upstream application; verify compatibility with the selected package · Source ↗ · Reviewed 2026-11-19

Documented · Editor reviewed.

Show all fields (5 not researched)
SCIM provisioning
Not researched Supply a public source.
Compliance attestations
Not researched Supply a public source.
Security controls
Not researched Supply a public source.
Air-gapped operation
Not researched Supply a public source.
Operating cost estimate
Not researched Supply a public source.

Scope & considerations

The third-party VM is distinct from an upstream-supported appliance; confirm installed package versions and apply security updates. Use django-helpdesk 2.6.1 or a later compatible fixed build and review the public ticket and non-staff permission settings.

Community & maintenance

The reviewed upstream contributor history includes gwasser, rossp, uhurusurfa, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Category fit

Customer support
Django-based helpdesk for tickets, queues and support communication.

Compare within Customer support

  • Chatwoot Self-HostedSelf-hosted customer-support inbox combining live chat, email and messaging conversations.
    • AWS
    • Azure
    • Google Cloud
    • DigitalOcean
    Customer-operated · Open Source / Open Core
  • Combodo iTop (Community)Community IT service-management application with tickets, configuration records and service workflows.
    • Hostinger
    Customer-operated · Open Source / Open Core
  • Deskpro Private — Self-HostedCommercial helpdesk installed on customer servers or in customer-controlled private infrastructure.
    • AWS
    Customer-operated · Commercial Only
  • DiscourseSelf-hosted discussion and community platform for workplace collaboration and customer support communities.
    • AWS
    • Google Cloud
    • DigitalOcean
    • Hetzner
    • Linode
    • Vultr
    Customer-operated · Open Source / Open Core
  • Frappe HelpdeskSelf-hosted support desk for tickets, knowledge content and service operations.
    • Azure
    Customer-operated · Open Source / Open Core
  • Jira Service Management Data CenterCommercial self-managed IT service management platform deployed on customer-operated infrastructure. New Data Center subscriptions are restricted to eligible existing Atlassian customers.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • LibreDeskSelf-hosted shared inbox and customer support desk.
    • Railway
    • Hostinger
    Customer-operated · Open Source / Open Core
  • Live Helper ChatSelf-hosted customer live chat and support communications.
    • DigitalOcean
    Customer-operated · Open Source / Open Core

Showing 8 of 14 other listings in Customer support. These products address related workflows; read their category-fit notes before comparing scope. See all of Customer support →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • Microsoft Marketplace ↗ · Azure

      Marketplace offer · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

      Django application, database and persistent files in a cloudimg Azure VM. The third-party VM is distinct from an upstream-supported appliance; confirm installed package versions and apply security updates.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked
  5. Community & maintenance evidenceChecked

Suggest a correction · Back to directory