Self-Hosted Task Tracker in Kazakhstan: The Complete 2026 Guide

A self-hosted task tracker in Kazakhstan makes sense when it matters to the company to store task data in the country, when the company runs Jira Data Center with end of support coming in 2029, or when the bill for cloud licenses in US dollars is growing faster than the team. In exchange, the company takes on the server, backups, updates, SSO and monitoring, and this needs to be prepared for in advance.

This guide is for IT company executives, heads of IT departments and team leads deciding whether to move their tracker to their own servers. We cover the reasons, areas of responsibility, hosting options, a comparison of cloud, self-hosted and air-gapped, a readiness checklist and owner roles.

Why self-hosted in 2026

Storing data in the country. A task tracker contains names, work emails, sometimes phone numbers and customer documents in attachments. Some companies and their customers want such data stored in Kazakhstan. A server at a Kazakhstan hosting provider or in your own data center solves this.

Atlassian is leaving self-hosted. Jira Server has been unsupported since February 15, 2024. New Jira Data Center licenses haven’t been sold since March 30, 2026, and on March 28, 2029, Data Center will no longer be supported. After that, the license is read-only and Marketplace apps are disabled. Atlassian’s cloud offers storage regions in the US, EU, Asia and other countries, but not in Kazakhstan. More in our article on the end of Jira Data Center.

Cloud pricing. Jira Cloud Standard costs $7.91 and Premium $14.54 per user per month, plus another $5.42 for Confluence Standard (as of October 2026, annual billing). Cloud Plane Pro costs $6, Business $13. For a 100-person team, that’s a noticeable line in the budget, in US dollars, and it doesn’t shrink over time.

Kazakhstan context. Foreign SaaS is paid with a corporate card in US dollars, and vendors don’t provide closing documents that meet Kazakhstan accounting standards. A self-hosted tracker on a server at a Kazakhstan hosting provider is paid in tenge under a contract with completion certificates. For accounting, it’s an ordinary infrastructure expense rather than a payment to a foreign service.

What the company takes on

In the cloud, the vendor is responsible for keeping the system running. With self-hosting, all of that shifts to you.

Area	What to do	Minimum practice
Server	Allocate resources, update the OS, close unnecessary ports	A dedicated VM for the tracker, SSH access by key only
Backups	Copy the database, files and configuration	Daily backup, a copy off the main server, a restore test once a quarter
Updates	Install new versions of the tracker and its dependencies	Backup before updating, a staging environment for major versions
Access and SSO	Connect corporate authentication, deactivate departing employees	SSO or LDAP if available in your edition; an offboarding procedure
TLS and network	Certificate, domain, external access or VPN-only	HTTPS is mandatory; the security team decides on VPN
Monitoring	Watch availability, disk, memory, errors	Uptime check and an alert for disk filling up
Email	Notifications to users	Your own SMTP or the company’s email service

The most common mistake we see is a backup nobody has ever restored. It exists right up until the first outage.

Where to host the tracker

A VPS at a Kazakhstan hosting provider

The simplest route for teams of up to several hundred people. A virtual machine at a local provider, a contract and payment in tenge, data physically in the country. The hosting provider maintains the hardware; everything above the operating system stays with you. For Plane, the vendor specifies a minimum of 2 cores and 4 GB of RAM and recommends 8 GB for production.

Your own data center or server room

This suits companies that already have infrastructure, virtualization and admins. The upside: full control and integration with internal services without going through the internet. The downside: the load on your own team and redundancy requirements. If the tracker becomes a critical system, you’ll need a second node or at least a rehearsed procedure for restoring onto different hardware. Decide in advance how many hours of downtime the company can tolerate, and design the redundancy setup around that.

Air-gapped environment

A fully isolated network with no internet access. Needed by banks, the public sector and companies with strict security requirements. The tracker must be able to receive licenses and updates offline. Plane has an Airgapped edition for this: offline licenses and updates, a local AI model, and functionality on par with the Commercial edition.

Cloud, self-hosted or air-gapped: a comparison

Criterion	Vendor cloud	Self-hosted	Air-gapped
Where the data is	With the vendor; Kazakhstan isn’t among Atlassian’s regions	On your server in Kazakhstan	In the company’s isolated network
Data stays in Kazakhstan	No	Yes, with a server in Kazakhstan	Yes
Who updates	The vendor	You	You, via offline packages
Payment	Card in USD	Hosting in tenge, paid edition in USD if needed	Vendor license and your own infrastructure
Launch	A day	From a few days, including setup	Weeks, together with the security team
GitHub and Slack integrations	Out of the box	Work with internet access	Internal only
AI features	Vendor’s cloud models	Depends on edition and settings	Local model
Load on the team	Minimal	Requires a technical owner	Requires a technical owner and security team sign-off

The cloud remains a reasonable choice if the tracker holds no personal data, the team is small and there are no security requirements. But for most Kazakhstan IT companies with client projects, the conversation quickly runs into data storage.

Which trackers can be installed on your own server

The realistic shortlist for 2026 looks like this.

• Plane is closest to Jira: work items, cycles, modules, epics, Pages and Wiki, automations, a Jira importer. The Community Edition under AGPL-3.0 is free with no user limit. Commercial adds paid features, and Airgapped works without internet. Plane lists SOC 2 Type II and ISO 27001:2022 certifications for both the cloud and self-hosted.
• OpenProject is for projects with Gantt charts and budgets, licensed under GPL.
• YouTrack is closed source, free for up to 10 users, and aimed at JetBrains teams.
• Redmine is old and stable, with a dated interface.

Jira Data Center will keep working for existing customers until March 2029, but new licenses aren’t sold. So building a new environment on it in 2026 makes no sense: you’ll have to migrate anyway in two and a half years.

We described a step-by-step Plane installation with environment variables, backups and updates in our Docker guide to installing Plane.

Who owns the system

A self-hosted tracker breaks down organizationally, not technically. You need two owners with clear areas of responsibility.

Role	Area of responsibility	Usually who
Technical owner	Server, updates, backups, monitoring, SSO, incidents	DevOps, system administrator or a contractor
Process owner	Project structure, statuses, work item types, permissions, templates	Head of PMO, team lead, product manager
Security lead	Requirements for access, logs, network segmentation	Security specialist
Executive sponsor	Budget, priorities, decision on a paid edition	CTO or head of IT

If there’s no technical owner on staff, maintenance is handed to a contractor under an agreement with a clear response time. The key is to put this in writing before installation, not after the first outage.

Common mistakes when moving to your own server

Installing it “just to try” and forgetting about it. The tracker is deployed on a test machine, the team starts working in it, and three months later the test machine has become production without backups or monitoring. The fix is simple: treat the installation as production from day one, or honestly delete it after the test.

Backing up only the database. Attachments, images in descriptions and the configuration file are stored separately from the database. Without them, restored tasks have no files, and without the configuration containing the encryption keys, some data may not come back up.

Putting off updates. The longer a system goes without updates, the more painful it is to jump several versions. A regular monthly update window is cheaper than one big migration a year.

Not planning for employee departures. Without SSO, a departed employee keeps access to customer tasks until someone remembers to deactivate them. An access revocation procedure is needed from day one, even if you connect SSO later.

Migrating everything indiscriminately. Five years of tasks, archived projects and broken filters get moved along with the useful data. Migrate active projects and keep the archive in an export.

Self-hosted readiness checklist

1. It’s clear what data will be in the tracker and where the company wants to store it.
2. The tracker and edition are chosen, and you’ve checked which edition includes SSO and the permissions you need.
3. The hosting site is chosen: a provider in Kazakhstan, your own data center or an isolated environment.
4. A technical owner and a process owner are assigned.
5. There’s a domain, a TLS certificate and SMTP for notifications.
6. A daily backup of the database and files is set up, with a copy off the main server.
7. A test restore from backup has been carried out.
8. Monitoring of availability and disk space is set up.
9. An update procedure and update window are documented.
10. A procedure for granting and revoking access is documented.
11. A pilot team has worked in the system for two to four weeks.
12. There’s a plan for migrating data from the old system and a rollback plan.

If six of the twelve items aren’t done yet, it’s too early to go to production. Better to spend a week preparing than to rebuild tasks from chat history later.

How we do it

We start with a diagnostic: what data will be in the tracker, what the security team requires, who will own it, and how many people will be using the system a year from now. Then we install the tracker on a server in Kazakhstan, set up backups, TLS, SSO and monitoring, and run a pilot with one team. After the pilot, we bring in the remaining teams and hand the system over to its owners with documented procedures, or take on maintenance ourselves.

Details are on the Jira and Plane task tracker implementation page: stages, timelines and what’s included in the outcome.

---

Sources. Data Center timeline: atlassian.com/enterprise/data-center. Atlassian data storage regions: data residency documentation. Pricing: Jira, Plane. Plane server requirements: self-hosting documentation. Plane repository: github.com/makeplane/plane. Prices are as of October 2026 and may change.

Terms in plain words

Self-hosted

The tracker is installed on a server the company controls: at a local hosting provider or in its own server room. The company itself is responsible for updates, backups and security.

Air-gapped

An installation in a network completely cut off from the internet. Licenses and updates are delivered offline; banks, the public sector and companies with strict security requirements choose this setup.

VPS

A virtual server rented from a hosting provider. With a hosting provider in Kazakhstan, data stays in the country and payment is in tenge under a contract.

Backup

A copy of the system’s database, files and settings. It’s only useful if restoring from it is tested regularly.

SSO and LDAP

Ways to connect the tracker to the corporate account system. Employees sign in with their work login, and when someone leaves, access is revoked centrally.

TLS

Encryption of the connection between the browser and the server, which is what gives you HTTPS. Without it, passwords and task contents travel over the network in plain text.

SMTP

The protocol for sending email. The tracker uses an SMTP server to send users notifications about tasks.

SOC 2 Type II and ISO 27001

International information security standards and audits. A certificate shows that the vendor has data protection processes in place, but it doesn’t replace a review by your own security team.