Request Tracker (RT)
Self-hosted ticketing, request tracking and service workflows.
4 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
Request Tracker 6.0.4 security release
Best Practical recommends upgrading for the multiple security issues listed in RT 6.0.4.
Scope: RT 6.0.4 security corrections; individual issues have separate conditions and ranges. The reviewed AWS AMI is RT 6.0.3.
Launching the older vendor AMI does not apply the newer application security fixes.
Action: Upgrade the RT 6.0.3 AWS image’s application through the supported 6.0.4-or-later process and check database/plugin compatibility.
Primary source · Reviewed 2026-11-19
What lands where
Supplied by
Vendor or project
VM image
Runs in
Documented customer environment
Request Tracker application and persistent database in the Best Practical AWS AMI.
- AWS: Customer cloud account
- AWS
Servers / containers
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
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
AWS 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 method | VM image |
|---|---|
| Infrastructure | Servers / containers Request Tracker application and persistent database in the Best Practical AWS AMI. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure. |
| Licensing model | Open Source / Open Core GNU GPL-2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. |
| License | GNU GPL-2.0 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.
6 of 12 fields researched (50%) · 5 documented · 1 unresolved. Evidence coverage is not a feature score.
- Marketplace delivery
AvailableEvidence and scope for Marketplace delivery
The reviewed AWS offer delivers Amazon Machine Image (AMI) from Best Practical Solutions. Its package version is RT 6.0.3 (August 2026); verify the contained application and required entitlements separately.
Request Tracker (RT) selected AWS public offer; infrastructure and support charges are separate · Source ↗ · Offer prodview-j7nw37pratobq ↗ — Best Practical Solutions; Amazon Machine Image (AMI); package RT 6.0.3 (August 2026) · Reviewed 2026-11-19
Documented · Editor reviewed.
- Single sign-on
AvailableEvidence and scope for Single sign-on
RT 6.0.4 documents web-server SSO using REMOTE_USER, including Kerberos through Apache modules. Configure WebRemoteUserAuth, user matching/autocreation, fallback and continuous-session policy; the external system handles its own MFA. LDAP/password lookup and REST tokens are separate authentication paths.
Versioned RT external user authentication through a configured web-server trust boundary · Source ↗ · Versioned RT authentication configuration ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
The RT 6.0.4 distribution documents configure, dependency checks, installation, database initialization and web-server setup. Set the database driver, service permissions, mail gateway, HTTPS and secrets for your topology. The upstream source distribution and third-party marketplace image are separately versioned artifacts.
Published RT 6.0.4 source installation · Source ↗ · Deployment artifact ↗ (rt-6.0.4) · Reviewed 2026-11-20
Documented · Editor reviewed.
- Minimum footprint / sizing
Not confirmedEvidence and scope for Minimum footprint / sizing
The versioned manual identifies the Perl/web-server and supported relational database dependencies but does not establish a workload-specific whole-system CPU/RAM/storage minimum. Ticket volume, attachments, indexing and mail processing drive sizing; marketplace instance options are not a 100-user, 1 TB HA capacity plan.
RT 6.0.4 dependency guidance; numeric production and HA sizing remains unconfirmed · Source ↗ · Reviewed 2026-11-20
Sources checked — unresolved · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
GNU GPL-2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Request Tracker (RT); 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 rt-6.0.4 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence.
Request Tracker (RT) upstream application; verify compatibility with the selected package · Source ↗ · Reviewed 2026-11-19
Documented · Editor reviewed.
Show all fields (6 not researched)
- Cloud commitment eligibility
- Not researched Supply a public source.
- 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 vendor image is RT 6.0.3, while upstream 6.0.4 is a separate release. Check application updates after launching the AMI. Upgrade the RT 6.0.3 AWS image’s application through the supported 6.0.4-or-later process and check database/plugin compatibility.
Community & maintenance
The reviewed upstream contributor history includes sunnavy, obra, alexmv, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.
Category fit
- Customer support
- Self-hosted ticketing, request tracking and service workflows.
Compare within Customer support
- Chatwoot Self-HostedSelf-hosted customer-support inbox combining live chat, email and messaging conversations.
- AWS
- Azure
- Google Cloud
- DigitalOcean
- Combodo iTop (Community)Community IT service-management application with tickets, configuration records and service workflows.
- Hostinger
- Deskpro Private — Self-HostedCommercial helpdesk installed on customer servers or in customer-controlled private infrastructure.
- AWS
- DiscourseSelf-hosted discussion and community platform for workplace collaboration and customer support communities.
- AWS
- Google Cloud
- DigitalOcean
- Hetzner
- Linode
- Vultr
- django-helpdeskDjango-based helpdesk for tickets, queues and support communication.
- Azure
- Frappe HelpdeskSelf-hosted support desk for tickets, knowledge content and service operations.
- Azure
- 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
- LibreDeskSelf-hosted shared inbox and customer support desk.
- Railway
- Hostinger
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
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- AWS Marketplace ↗aws.amazon.com
- GitHub COPYING (GPL-2.0) ↗raw.githubusercontent.com
- GitHub Releases ↗github.com
- Request Tracker 6.0.4 security release ↗github.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- AWS Marketplace ↗ · AWS
Marketplace offer · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Request Tracker application and persistent database in the Best Practical AWS AMI. The vendor image is RT 6.0.3, while upstream 6.0.4 is a separate release. Check application updates after launching the AMI.
- AWS Marketplace ↗ · AWS
- Infrastructure evidenceChecked
- Licensing evidenceChecked
- Community & maintenance evidenceChecked
- Community, governance or adoption evidence ↗github.com
- Upstream project ↗github.com