How much does Jira cost? Atlassian's pricing page answers with a number, and for most teams it is the wrong one. The figure at the top of the page is a blended rate for a 300-person company, the annual price is not a discount at every headcount, and the line that decides your bill, who counts as a user, is in an FAQ further down.
This guide covers what each Jira plan actually costs per user, what the Free plan gets you and where it ends, how annual billing works, and the seat math that decides most teams' bill. Every figure comes from Atlassian's own price tables, checked on September 30, 2026.
In this article
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
Jira Pricing Plans at a Glance
Jira Cloud has four plans. Most teams with more than 10 users end up on Standard.
| Plan | Price per user per month | Users | Storage | Support |
|---|---|---|---|---|
| Free | $0 | Up to 10 | 2 GB | Community |
| Standard | $9.05 | Up to 100,000 | 250 GB | Local business hours |
| Premium | $18.30 | Up to 100,000 | Unlimited | 24/7 for critical issues |
| Enterprise | Through sales, annual only | Up to 100,000 per site | Unlimited | 24/7 for all issues |
Standard and Premium prices are monthly billing for users 1 to 100. Larger teams pay less per user, because monthly billing is graduated by user band.
How Jira Pricing Actually Works
Jira charges per user, and Atlassian defines a user as anyone "who can log in to one of your Jira sites and who exists in User Management." Whether that person uses Jira every day or once a quarter makes no difference.
Monthly billing is graduated, like income tax brackets. Each user is billed at the rate of the band that user falls in:
| Users | Standard, monthly | Premium, monthly |
|---|---|---|
| 1 to 100 | $9.05 | $18.30 |
| 101 to 250 | $7.65 | $13.70 |
| 251 to 1,000 | $6.40 | $9.55 |
So a 300-person company on Standard pays $9.05 for its first 100 users, $7.65 for the next 150, and $6.40 for the last 50. That works out to $2,372.50 a month, which is where the $7.91 average comes from. Rates keep falling past 1,000 users, but if you are in that range you are talking to Atlassian sales anyway.
On monthly billing, Atlassian charges each month for "the exact number of Jira users you have." Remove a user and next month's bill drops. Annual billing works differently, because it is sold in flat user bands.
Jira Free Plan: What You Get and Where It Ends
Jira Free is a real plan, not a trial. It is generous where engineers notice and limited in the places that matter once a team grows.
What is included: unlimited work items and spaces, custom workflows and custom fields, and board, backlog, list, timeline, calendar, and summary views. Reports, dashboards, the mobile apps, and the Marketplace all work on Free. A team of six engineers can run real sprints on it for years.
Where it ends:
10 users
The hard ceiling, and the one that ends the plan. An 11th user moves the whole site onto a Standard trial and then a paid plan.
Every user is an admin
Free has no user roles and no permission settings on spaces or work items. Anyone on the site can change workflows, delete work, and see everything. That is fine for five engineers and uncomfortable once anyone outside engineering joins.
100 emails per day, site-wide
Notifications and automation emails share one daily cap. When you hit it, email stops until the next day. A busy team of eight hits this sooner than you would expect.
150 automation steps per month
Per subscription, not per user. Two or three active automation rules can use that up in the first week of the month.
2 GB of storage and Community support
Screenshots fit. Screen recordings and log files fill it fast. Support means the public Atlassian Community forum.
Free also has no Rovo AI and no guest access. Both start on Standard.
The 11th User
The 11th user is the step that catches small teams out. When a Jira Free site goes over 10 users, Atlassian automatically moves it onto a 7-day free trial of Standard. When the trial ends, the whole site is on a paid plan, and every user is billed, not just the new one.
The 11th user is rarely an engineer. More often it is the support lead who wants to see whether a customer's bug is fixed, a product manager, or a designer. One login from outside engineering can turn a free tool into a $1,200-a-year line item, and nobody decided to buy it.
Jira Standard: $9.05 per User per Month
Standard is the plan most paying Jira teams are on. It adds the controls that Free leaves out:
- User roles and permissions. Admins, regular users, and permission settings on spaces and work items, plus work item-level security.
- Guests and anonymous access. Free guest access for people outside your company, and the option to make spaces publicly viewable.
- No email cap. Notifications stop counting against a daily limit.
- 400 automation steps per user per month. A 20-person team gets 8,000 steps, pooled.
- 250 GB of storage, data residency, and audit logs for site changes.
- Rovo. Search, Chat, and Agents, with 25 Rovo credits per user per month.
- Business-hours support from Atlassian in your region.
At 20 users, Standard costs $181 a month on monthly billing. For a single engineering team without cross-team planning needs, it stays the right plan for a long time.
Jira Premium: $18.30 per User per Month
Premium is priced for organizations with several teams that depend on each other. What it adds:
- Plans. Atlassian's advanced planning tool for tracking work across teams and spaces, with cross-project dependencies, capacity management, scenario modeling, and a deeper work type hierarchy.
- Approvals and custom onboarding for teams with change control.
- Sandbox and release tracks. Test changes and apps before they reach production, and control when Atlassian's own cloud updates reach your users.
- Unlimited storage, 750 automation steps per user, and 70 Rovo credits per user per month.
- 24/7 support for critical issues and a 99.9 percent uptime SLA.
- Admin insights, IP allowlisting, and space archiving.
Jira Standard vs Premium
Premium costs 2.02 times as much per user. The useful question is not whether its features are good but whether you have the problem they solve.
Premium earns its price when
- Several teams ship work that depends on each other
- Leadership needs a cross-team roadmap in Jira, not in slides
- You need a sandbox to test workflow or app changes
- Downtime has a contractual cost and you need the 99.9 percent SLA
Standard is enough when
- One or two engineering teams with their own backlogs
- Dependencies are handled in standups, not in a planning tool
- Business-hours support is fine
- Nobody has asked for Plans by name
The usual trigger for Premium is Plans. If your program manager rebuilds a cross-team roadmap in a spreadsheet every quarter, Premium is probably worth it. If nobody has that job, Standard is the right answer.
Jira Enterprise
Enterprise is annual only and priced through Atlassian sales. It adds up to 150 Jira sites under one subscription, Atlassian Analytics and the Data Lake, Atlassian Guard Standard included (on other plans, SSO and SCIM need a separate Guard subscription), 1,000 automation steps and 150 Rovo credits per user, 24/7 support for all issues, and a 99.95 percent uptime SLA. If your security team has not asked for centralized identity or multi-site administration by name, you do not need it yet.
Monthly vs Annual Billing: The Band Trap
Most SaaS products give a flat discount for paying annually. Jira does not. Annual Jira subscriptions are sold in flat user bands, and Atlassian says it charges "for the tier that most closely matches your user count." Every team in a band pays the same price, whether it sits at the bottom of the band or the top.
| Users | Standard, annual | Premium, annual | Annual beats monthly from |
|---|---|---|---|
| 1 to 10 | $900 | $1,850 | 9 users |
| 11 to 15 | $1,350 | $2,750 | 13 users |
| 16 to 25 | $2,250 | $4,600 | 21 users |
| 26 to 50 | $4,550 | $9,150 | 42 users |
| 51 to 100 | $9,050 | $18,300 | 84 users |
The last column compares the annual band price with 12 months of monthly billing at $9.05 or $18.30 per user. The break-even points match on both plans.
A team of 26 pays about 61 percent more by committing for the year. A team of 48 saves about 13 percent. Same plan, same features, and the gap comes entirely from where your headcount sits in the band.
The practical rule: before choosing annual, check where you will be in the band over the coming year. If you are just above a band floor and not hiring fast, pay monthly. If you are near a band ceiling, annual is the cheaper option, and within the band, adding people costs nothing until the next renewal pushes you into the next band.
The Seat Math: Who Actually Needs a Jira License
On paid plans, every person with a Jira login is a billed user, and the pricing page does not show that cost because it depends on who you invite.
Jira bills everyone who can log in. There is no free read-only seat for your own staff. Free guest access sounds like the answer, but Atlassian's guest rules exclude it:
- Guests must be outside your organization. Atlassian says the purpose of the feature is to invite users outside of your organization, and you cannot convert current or former paid users into guests.
- Each guest can belong to only one space per site.
- Guests are free up to 5 per paid user, and they are only available on Standard, Premium, and Enterprise.
Anonymous access, also on paid plans, makes a space viewable without a login, which is not something you want for spaces that hold customer bug reports.
So your support agents, customer success managers, and account managers who need to know whether a bug is fixed are full Jira users. Three scenarios for a B2B software company, all on Standard:
| Team | Users | Monthly billing | Annual billing |
|---|---|---|---|
| 9 engineers on Free, plus 3 support agents | 12 | $108.60 a month, from $0 | $1,350 a year, from $0 |
| 22 engineers, plus 6 support and CS | 28 | $253.40 a month, up $54.30 | $4,550 a year, up from $2,250 |
| 40 engineers, plus 8 support and CS | 48 | $434.40 a month, up $72.40 | $4,550 a year, no change |
The middle row is the one to notice. Six people who only read a status field push an annual subscription from one band to the next, and the bill goes up $2,300 a year. The last row shows the opposite case: on an annual plan with room in the band, adding them costs nothing until renewal.
The expensive Jira decision is rarely Standard or Premium. It is how many people you give a login to so they can read one field.
The Costs That Are Not on the Pricing Page
Four more lines are worth budgeting for before you commit.
Marketplace apps. Cloud apps from the Atlassian Marketplace are generally billed against your site's Jira user count, not the number of people who use the app. Every extra Jira user can add a little to each paid app on the site.
Rovo usage. Rovo is included on every paid plan with a monthly credit allowance per user, 25 on Standard, 70 on Premium, and 150 on Enterprise. Search does not use credits, and Chat and Agent requests do. Atlassian is not charging for usage beyond the allowance today and has committed to at least 90 days' notice and an explicit opt-in before that changes. Budget nothing for it now, and keep an eye on it.
SSO and SCIM. On Free, Standard, and Premium, single sign-on and user provisioning need a separate Atlassian Guard Standard subscription. Only Enterprise includes it.
A service desk, if you add one. Jira Service Management is no longer sold on its own. It comes inside Atlassian's Service Collection at $25 per agent per month for the first 15 agents on Standard. The Jira vs Jira Service Management guide covers who needs which license.
Where Jira Pricing Bites B2B Software Teams
Jira pricing bites B2B software teams when support needs to follow customer-reported bugs. The pattern is predictable. Engineering runs Jira happily, on Free or Standard. Then support starts asking about customer-reported bugs, and the request ends one of three ways.
Buy them seats. Simple, and it grows. Once support is in, customer success wants in, then account managers want in for their escalated accounts. On a Free site, the first of them can be the 11th user.
Have them ask an engineer. Free on paper and expensive in practice. Every "is this fixed yet?" message interrupts the person you least want interrupted, and the answer is stale by the time it reaches the customer. The guide to support and engineering communication covers why this loop is so hard to break.
Bring the status to support. Support stays in the help desk it already pays for, engineering stays in Jira, and the work item's status and comments move between the two. Nobody buys a seat to read a field.
If your support team works in HubSpot, HubSpot has its own Jira integration. Its documentation says syncing between a ticket and its Jira issue can take from one to twenty-four hours, comment sync has to be switched on for each ticket, and Jira status arrives as a read-only property. That is workable for occasional escalations and thin for a team that escalates every day.
IssueLinker was built for the third option. From a HubSpot ticket, support creates a Jira work item in one click, drafted from the ticket conversation, in the project where engineering already works. Comments sync both ways on every linked ticket, and Jira status flows back to the ticket as it changes, so support sees the fix land and replies to the customer the same day. Support never needs a Jira login. The setup is in the Jira HubSpot integration guide.
Stop buying Jira seats so support can read a status
IssueLinker links HubSpot tickets to Jira work items and syncs comments and status both ways. Support answers from HubSpot, engineering stays in Jira, and nobody becomes the 11th user. Flat monthly price, unlimited users, setup in about fifteen minutes.
To compare fairly: IssueLinker costs $39 a month regardless of headcount, which is about four Jira Standard seats on monthly billing. If two or three support people need status and you already pay for Jira, buying the seats is often the simpler call. The math changes when those people would be the 11th, 12th, and 13th users on a Free site, when they push an annual plan into the next band, or when support needs comments and status to arrive in the ticket, not in a second tool they have to remember to check.
How to Pick a Jira Plan
Pick the plan for the limit you have actually hit, not for the feature list.
A real plan, not a demo. Run sprints, boards, and workflows without paying anything. Plan for the end of it: decide now who the 11th user will be and what that costs.
Permissions, guests for outside collaborators, no email cap, and enough automation for most teams. The right plan for most software companies until cross-team planning becomes someone's job.
Worth it when Plans replaces a roadmap spreadsheet someone maintains by hand, or when downtime has a contractual cost. Not worth it for the extra storage alone.
Multiple sites, Guard included, and Atlassian Analytics. If nobody has asked for those by name, the sales conversation will not pay off yet.
Five Ways to Keep the Jira Bill Down
None of these are tricks. They are the places Jira budgets usually leak.
Before your next renewal
- Check where your headcount sits in its annual band. Near the floor, monthly billing is cheaper. Near the ceiling, annual is.
- Remove users who have left or changed roles. Anyone who can still log in is billed, active or not.
- Use guests for real outside collaborators, such as contractors and agencies. They are free up to 5 per paid user.
- Separate the people who work in Jira from the people who only need to know a status. Only the first group needs a seat.
- Check whether you are on Premium for one feature. If it is only storage or support hours, Standard costs half as much.
Is Jira Worth the Price
Per seat, Jira is one of the cheaper options in its category. Standard at $9.05 sits just under Linear's Basic plan at $10 billed annually, and Jira's Free plan covers 10 users with no limit on work items. GitHub Issues is cheaper still for teams that already pay for GitHub. If you are still choosing a tracker, the Linear vs Jira comparison and the Jira alternatives guide cover the tradeoffs beyond price.
The bigger cost of Jira is rarely the per-seat rate. It is the seat count, and the annual band that count lands you in. Teams that are happy with their Jira invoice keep the user list to people who work in Jira and connect everyone else some other way.
