Why one Jira app instead of four

The per-app tier

Atlassian prices Marketplace apps for Jira Cloud by the number of users on the site, not the number of people who use the app. A 100-user site pays the 100-user price for a time-tracking app even if only the delivery team logs time. That's reasonable for one app. It compounds when a team needs several.

The arithmetic at 100 users

We checked the published Cloud list prices at the 100-user tier in September 2026 for four widely used apps covering the jobs our suite does:

Prices change, so check the Marketplace listings for today's figures. The shape of the problem doesn't change: separate apps, separate bills, each at the full tier.

What a suite changes

Reporting, timesheets, budgets and AI spend all read the same things: issues, worklogs, people and rates. Four apps means four copies of that data, four permission models and four settings pages. A suite keeps one of each, which is why each module after the first costs a fraction of the one before it to build — and why seven modules can sit under one price.

Our planned launch price is $400 a month at 100 users for all seven modules, including diagramming, workflow automation and email handling, and free for teams of ten or fewer. Modules that ship later are included for existing customers at no extra cost.

The honest caveat

Bastion Helix is not available yet: all seven modules are built and running in our own test Jira site, but the Marketplace listing isn't live. The established apps have years of edge cases behind them. The live demos on this site run the real module code on sample data, so you can judge for yourself before trusting any of this.