Jira Self-Hosted: A Setup Checklist for Your Team in 2026
Setting up jira self hosted? Use this 2026 checklist to plan hosting, security, backups, upgrades, and recovery. Read now before launch.
Running Jira on your own infrastructure can give your team control over hosting, security, and integrations. It also means you own the work that a hosted service would handle, including capacity planning, backups, upgrades, and incident response.
Skip one important check and a routine upgrade can become a long outage. A rushed migration can also leave teams without reliable permissions, reporting, or recovery plans when they need them most.
But here's the truth: a dependable Jira self-hosted setup starts with a checklist, not an installation command. Use this guide to plan the environment, test the deployment, protect your work, and prepare your team for launch. You’ll also find practical questions to resolve before choosing a long-term setup.
Jira Self-Hosted Setup Checklist: 10 Steps to Complete
Work through these steps in order. Each one addresses a decision that can affect the next, from licensing and infrastructure to user readiness.
- Confirm the product and licensing path. Atlassian Server support ended in 2024, so self-managed Jira generally means Jira Data Center. Confirm your current subscription, eligibility, and support arrangements directly with Atlassian before planning a new deployment.
- Define the hosting requirement. Decide whether the system will run in your own data center, a private cloud, or another approved environment. Write down required network boundaries, data residency needs, and any rules for restricted or disconnected networks.
- Estimate capacity. Count active users, projects, automation rules, and expected growth. Include peak usage, such as sprint planning or quarterly reporting, rather than sizing only for an average workday.
- Choose an architecture. Decide whether you need a single node or a clustered deployment. A small pilot may work on a simpler setup, while high availability needs additional planning for load balancing, shared storage, and database resilience.
- Prepare the operating environment. Check supported operating systems, Java requirements, database compatibility, storage performance, and network access against Atlassian’s current technical guidance. Keep development, test, and production environments distinct.
- Plan identity and access. Choose how people will sign in, how groups will be managed, and which administrators need elevated access. Map permissions to real team responsibilities instead of granting broad access for convenience.
- Design backups and recovery. Set backup frequency, retention, encryption, and off-site storage. Define recovery time and recovery point objectives, then test restoration before the system becomes a critical team dependency.
- Review integrations and customization. List apps, scripts, authentication links, and external services. Check compatibility with your target Jira release and decide who will maintain each connection after upgrades.
- Run a rehearsal. Test installation or migration in a non-production environment. Verify workflows, permissions, notifications, search, reports, and recovery procedures with representative projects and teams.
- Prepare the launch and ownership plan. Name the people responsible for upgrades, monitoring, support, and security reviews. Give teams a clear change window, a way to report issues, and a rollback plan.
Here's why: a checklist makes hidden dependencies visible early. For example, an identity decision can affect access testing, while an app compatibility issue can change the upgrade schedule.

Choose an Architecture That Fits Your Team
Start with workload and availability needs
Estimate how many people will use Jira at the same time, not just how many accounts you have. A team of 500 people may have much lower concurrency than a smaller organization running intensive build and planning workflows.
Consider the impact of downtime, too. If teams can pause work for a few hours, a simpler architecture may be acceptable. If Jira supports daily operations across multiple departments, plan for redundancy and a tested recovery route.
Separate environments and responsibilities
A test environment gives administrators a safe place to check upgrades, app compatibility, and workflow changes. Keep it close enough to production to make tests meaningful, but protect it from being mistaken for the live system.
Assign clear ownership for the operating system, application, database, network, and identity service. When an incident occurs, a named owner for each layer helps the team find the right person without delay.
Protect Jira with Practical Security Controls
Limit access and strengthen sign-in
Use a central identity provider when appropriate, require strong authentication, and remove accounts promptly when people leave. Give administrative permissions only to staff who need them, and review those permissions on a schedule.
For example, a product team may need permission to manage its own project settings without receiving global Jira administration rights. A narrower role reduces the chance that an accidental change affects every team.
Secure the network and sensitive information
Restrict administrative interfaces to trusted networks, use encrypted connections, and keep secrets out of scripts and shared notes. Review what integrations can access, especially when they connect Jira with build systems or customer support platforms.
Decide how long audit records and backups should be retained, who can access them, and how they are protected. A security plan works best when those details are part of routine operations rather than an emergency response.
Plan Backups, Upgrades, and Ongoing Operations
Make recovery a tested routine
A successful backup is one you can restore. Schedule regular recovery tests in a separate environment, record the steps, and check that restored projects, attachments, permissions, and integrations behave as expected.
Suppose your team can tolerate losing no more than one hour of work. Your backup schedule and recovery process must support that goal, and a test should confirm it in practice.
Use a controlled upgrade process
Review release notes, supported apps, and technical requirements before each upgrade. Test the planned version in a staging environment, then schedule production work when administrators and key team representatives are available.
Keep a rollback approach ready, and monitor performance after the change. A quick check of login, search, workflows, notifications, and key integrations can catch problems before they spread across teams.
Prepare Projects and People Before Launch
Make workflows easy to understand
Start with a small set of workflows that match how teams actually work. For example, a software team might use “To Do,” “In Progress,” “In Review,” and “Done,” while a service team may need triage and approval stages.
Standardize only where shared reporting or handoffs require it. Too many custom fields and statuses make Jira harder to maintain and can leave teams unsure which option to choose.
Train teams with real tasks
Show people how to create and update issues, find work, and use their team’s boards. A short exercise—such as moving a sample task through review—often teaches more than a long presentation of every feature.
Choose project champions who can answer routine questions during the first weeks. Gather feedback after launch and adjust confusing workflows before workarounds become habits.
ONES.com as a Jira Self-Hosted Alternative
ONES.com combines project management and knowledge management in one platform, with deployment choices that include Cloud, On-Premise, Private Cloud, and Air-gapped environments. ONES Project is its project management product and a Jira alternative; ONES Wiki is its knowledge management product and a Confluence alternative. They are sold separately.

The platform may suit teams that want self-hosted deployment options, Jira-compatible workflows, and fewer separate add-ons to manage. Cloud and self-hosted deployments have feature parity, so teams can assess deployment needs without treating the self-hosted version as a reduced feature set.
Core capabilities: pain, capability, result
- Fragmented project tracking: ONES Project brings work planning and execution into one project management environment, helping teams coordinate tasks and progress.
- Difficulty adapting processes: Custom workflows and fields let teams reflect their approval steps and work categories, reducing reliance on informal workarounds.
- Sprint planning overhead: Sprint management supports planning and tracking work across iterations, giving teams a clearer view of commitments.
- Manual recurring tasks: Automation helps handle repeatable workflow actions, freeing administrators and project leads from some routine updates.
- Limited progress visibility: Built-in reporting gives teams ways to review project activity without assembling every view through separate add-ons.
- Tool sprawl for project knowledge: ONES Wiki can provide a separate knowledge management option alongside ONES Project when teams want related capabilities from one provider.
- Restricted hosting requirements: On-Premise, Private Cloud, and Air-gapped deployments give organizations choices for different infrastructure and network constraints.
- Concern about feature gaps in self-hosting: Feature parity between cloud and self-hosted versions helps teams plan around deployment requirements while retaining the platform’s capabilities.
Application scenarios
A regulated organization with restricted network access could evaluate an Air-gapped deployment for project work that must remain within a disconnected environment. Its administrators should still validate security, operations, and integration requirements during a pilot.
A growing software team could test ONES Project with Jira-compatible workflows, sprint management, and built-in reporting. ONES.com offers a free plan for up to 30 seats, which can help a team evaluate the platform before a broader rollout.
Common Challenges and Practical Fixes
- Unclear infrastructure ownership: Application, network, and database responsibilities can overlap. Name an owner for each area and agree on escalation paths before launch.
- App incompatibility during upgrades: A key integration may not support the target release. Maintain an app inventory, verify compatibility in staging, and replace or defer incompatible components before production changes.
- Backups that have never been restored: A backup may be incomplete or unusable. Test restoration regularly and record how long recovery takes.
- Permission sprawl: Broad access often persists after an urgent setup. Use role-based access, review memberships on a schedule, and remove elevated permissions when they are no longer needed.
- Low adoption after launch: Teams may fall back to private trackers if workflows feel confusing. Train people with realistic tasks, invite feedback, and make small adjustments based on recurring friction.
Frequently Asked Questions
What does self-hosted Jira mean?
Self-hosted Jira runs in infrastructure that your organization manages, such as its own data center or a private cloud. Your team takes responsibility for hosting, updates, security controls, monitoring, and recovery. In 2026, confirm the available Jira Data Center options and licensing terms with Atlassian, because Jira Server support ended in 2024.
What should I check before installing Jira Data Center?
Check the licensing path, supported operating environment, database compatibility, storage, network access, identity setup, and app compatibility. Estimate current and future usage, decide how much downtime your team can tolerate, and document backup and recovery targets. A non-production rehearsal can expose missing dependencies before the production rollout.
How often should I back up a self-hosted Jira instance?
Set the schedule around how much work your organization can afford to lose and how quickly it must recover. A team with frequent changes may need more frequent backups than a small group with limited activity. Test restoration regularly; a schedule alone cannot confirm that your recovery process works.
Can I move a self-hosted Jira setup to another environment?
Migration is possible, but the effort depends on the Jira edition, version, integrations, customizations, and destination architecture. Inventory apps and dependencies, rehearse the move in a test environment, and validate workflows, permissions, search, and reporting afterward. Confirm current Atlassian migration guidance before setting a production date.
Conclusion
A successful Jira self-hosted deployment depends on more than getting the application running. Confirm the licensing path, size the environment, secure access, rehearse upgrades, test recovery, and prepare teams to use their workflows.
But here's the truth: infrastructure control also brings ongoing responsibility. A careful checklist helps you spot risks before launch and gives administrators a practical routine for keeping the service reliable. If you are comparing approaches, assess Jira Data Center alongside platforms such as ONES.com against your hosting, workflow, and support requirements.