Open-source project
osTicket/osTicket avatar
osTicket/osTicket

osTicket's easiest install is a clone of the develop branch, and its database floor is MySQL 5.5

The osTicket open source ticketing system official project repository, for versions 1.8 and later

4,007 stars1,856 forksPHPGPL-2.0

At a glance

What is it?
osTicket is a PHP support ticket system that takes inquiries from email, phone and web forms into one agent interface. The deployment section is four commands, the requirements name two web servers and a database version that went out of support years ago, and the contributor instructions point into the folder the install tells you to delete.
Who is it for?
The project fits a support team that wants email and web intake in one place, runs its own web server, and is prepared to read the deploy script before pointing a document root at it. It does not fit a team on a modern database or on a server outside the two named.
Can I use it commercially?
Yes, with conditions. GPL-2.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
Is it still maintained?
Yes. The repository last received commits 151 days ago.
What is it written in?
Mainly PHP, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • osTicket/osTicket4,007 ★ · +84
Star history
Repository2026-09-262026-11-15
osTicket/osTicket3.9k4k

84 Stars in the last 50 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The easiest install clones the repository, not a release

The deployment section opens by saying the software now supports bleeding-edge installations, and that the easiest way to install and track updates is to clone the public repository.

The commands are short:

bash
git clone https://github.com/osTicket/osTicket

followed by a deploy into a document root, and then, for every later update, a pull and a second deploy.

What follows from the word easiest is worth pausing on. Cloning the default branch gives you the tip of the development line, not a tagged release. The repository's default branch is called develop, and the releases list shows two minor lines in flight at once, with the two most recent tags cut on the same day within two minutes of each other.

So the recommended path is the least reproducible one available: no version argument, no tag to record, and an update that is a pull. An installation that records what it deployed has to record a commit rather than a version, because there is no version in the command.

A sensible operator clones a tag instead and keeps the deploy script. The page does not offer that as the easy path, and does not say the easy path is unsuitable for production.

Two deploy commands that differ by one flag, and a directory to delete

The two deploy invocations are the only two commands on the page:

bash
git pull
php manage.php deploy -v /var/www/htdocs/osticket/

The first deployment, earlier in the section, adds a setup flag to the same script and the same target directory. Nothing on the page explains what the difference is, so a reader has to infer that one flag means a first install and the other means an update.

After the install, the page says to configure the server to serve the folder, visit the page, install as usual, and then delete the setup folder out of the deployment location when finished.

That last instruction is the interesting one, because of what is in the tree. The repository root holds the application's entry points: the login, index, ticket, file, profile, captcha, avatar, account and view scripts, plus the client and secure include files. They are at the root rather than in a public directory, so whatever document root you point at is the document root for the application.

Deleting the installer directory afterwards is therefore load-bearing advice rather than housekeeping, and it is the only security instruction on the page.

MySQL 5.5 as a floor, and two named web servers

The requirements are four lines and two of them age badly.

An HTTP server running Microsoft IIS or Apache. PHP between 8.2 and 8.4, with 8.4 recommended. The database driver extension for PHP. And a MySQL database at version 5.5 or greater.

That database floor is the problem. Version 5.5 of that database reached the end of its support life years ago, so the stated minimum is a version no current distribution will install and no current security update will patch. A reader taking the requirement literally is choosing an unsupported database before they have chosen a support ticket system.

The server list is narrower than most PHP applications. Two servers, and the repository ships a configuration file for one of them at its root, which is why the page can get away with naming only two: the rewrite rules for the other are part of what an administrator configures themselves.

The recommendations list is longer and reads like a checklist for an installation rather than a requirement: fourteen PHP extensions, from the character-type library through the image, internationalisation, compression and DOM modules, plus a caching module enabled and configured. None of them is marked optional.

The localization rules live in the folder the install says to delete

The contributing section has a localization subsection, and it points at a file by path.

Localizing strings in new code requires following a few rules, and the file containing them is inside the setup directory, under a documentation subdirectory within it.

That is the same directory the deployment section tells you to remove from the deployment location once installation is finished. So a contributor who installs first, follows the instructions, and then tries to follow the localization rules finds the document gone from their deployment.

The translation workflow itself is described well. The interface is described as completely translatable, language packs are published on the download page, missing languages can be requested through a translation crowdsourcing project, and a language that reaches full translation gets reviewed before it is published. There is also an in-browser translation site for the strings themselves.

So the process is well documented and the one file a code contributor needs is in the only place the installer tells you to remove.

Two different minimum versions on the same page

The repository description says it is the official project repository for versions 1.8 and later.

The upgrading section says something different: osTicket supports upgrading from 1.6-rc1 and later versions, and recommends reviewing an upgrade guide on the documentation site or a plain text file at the repository root, after taking a backup of the attachment files, the database and the codebase.

Both statements can be true at once, and the likely reading is that the description describes what is supported now while the upgrade path describes what existing installations may come from. But a reader has to guess which number applies to them, because the two are never reconciled and they use different forms: a version and a release candidate.

The backup advice is the part to take seriously. Three things are named, and one of them is the attachment files, which are not in the database and are the thing an administrator is most likely to forget.

The credits list a deleted project and a misspelled package

There are seventeen entries in the list of open source projects the software is supported by, and they are the most revealing paragraph on the page for anyone deciding how old this dependency set is.

One entry is annotated as deleted. The link goes to a project page for a dropdown library with the note that the project no longer exists, and it is still listed as something the software is supported by.

One entry is misspelled in the visible text: the JSON services package is written with the letters transposed, while its link points at the correct name.

And several links point at hosting that has moved on. One of the two mail libraries is linked on a forge rather than a package index, one timezone library is linked on a repository host rather than its own site, and the cryptography library is linked at a forge URL that looks like a mirror rather than a project page.

None of this affects a reader who installs the release tarball. All of it tells you the credits were written once and not revisited, which is worth knowing before you read anything else on the page as current.

Contributing means forking, and the root is the application

The contributing instructions are four sentences and they describe a specific workflow.

Create your own fork, use a branching model to create a new feature, publish the feature in your fork, and send a pull request to begin the conversation about integrating it. So there is no patch by mail, no issue-first requirement, and a branching convention rather than a commit convention.

That is workable for a project with an active contributor community and a fork-heavy culture, and it puts the review burden on the maintainers rather than on a committer.

The repository root is worth one more look for that reason. Four documentation files sit there, an issue template, a security policy, an upgrade guide and a release-notes file, alongside eighteen application scripts and two include files. There are directories for the API, the knowledge base, the staff control panel, the pages, the assets, the installer and the setup scripts, plus a web server configuration file.

So the same directory a contributor forks is the directory a web server is pointed at, which is the design that makes the deploy-then-delete advice necessary rather than optional.

Editorial conclusion

The project fits a support team that wants email and web intake in one place, runs its own web server, and is prepared to read the deploy script before pointing a document root at it. It does not fit a team on a modern database or on a server outside the two named. Three things to check before you install. Which branch you are deploying, because the page's easiest path clones the development branch rather than a release. Which server you run, because the requirements name two and the repository ships an IIS configuration file. And what you do with the installer directory, because the page tells you to delete it while the contributor guide points inside it.

Frequently asked questions

What does osTicket do?

It is a support ticket system that brings inquiries created by email, phone and web-based forms into one multi-user web interface, where incoming tickets are saved and assigned to agents. Tickets and responses are managed, organised and archived in the same place.

how to install osticket

Clone the repository into an empty folder, then deploy from inside it with a management script that takes a setup flag and a target document root, for example deploying into a web root path. Later updates are a git pull followed by the same script with a different flag.

What are osTicket's server requirements?

An HTTP server running Microsoft IIS or Apache, PHP between 8.2 and 8.4 with 8.4 recommended, the mysqli extension, and MySQL 5.5 or greater. A list of fourteen further PHP extensions and a configured caching module are given as recommendations.

How much does osTicket cost per month?

The page describes the software as completely free and available under the GPL version 2 licence, and separately offers a commercial support service. No price is given on the page itself.

Does osTicket have an API?

The repository contains an api/ directory and the tree is built around a staff control panel and a knowledge base, but the page does not document the API, its authentication, or its endpoints anywhere in the text shown here.

How do I contribute to osTicket?

Fork the project, use a branching model to create the feature, publish it in your fork, and send a pull request. Localization is handled through a crowdsourcing project with language packs published on the download page once a language reaches full translation.

Official sources

  1. Issues
  2. License: GPL-2.0
  3. osTicket/osTicket on GitHub
  4. README
  5. Releases
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/osticket-osticket.svg)](https://hysenlabs.com/projects/osticket-osticket)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/osticket-osticket.svg)](https://hysenlabs.com/projects/osticket-osticket)

Was this useful?