When one custom Forge app beats three Marketplace subscriptions
Marketplace apps are priced on your whole site's user count, so an app bought for one team is paid for everyone. When replacing several of them with one small custom Forge app makes sense, what it costs you instead, and when to keep buying.
Build or buy is an old question. On Atlassian Cloud it has a twist: what you buy is priced on everyone, even when only one team uses it.
We publish apps on the Atlassian Marketplace, so we are not about to argue against buying apps. Most of the time buying is right: someone else maintains the app, ships improvements and answers support, and the cost is predictable. But there is a pattern we see on almost every site we review, and it is worth naming, because it quietly costs more than anyone has added up. We wrote about the audit side in Pay for the 20% You Use; this is the build side.
The pattern
A team needed one feature. It was not native, so someone found an app that had it and installed it. The app does forty other things too, but that team uses the one. Two years later the site has several apps like this, each bought for a single feature, each used by one or two teams, and each priced on the full user count of the product it runs in.
Because Cloud apps are licensed for the same number of users as their host product, a Jira site with a thousand users pays a thousand-user price for an app that thirty people use for one thing.
Start with an inventory, not an opinion
Before deciding anything, list every installed app with four facts:
- What it is used for, in one sentence, from the people who use it.
- How many people use it, from audit logs, field usage and macro usage, not from memory.
- Which of its features are used. Often it is one or two.
- What it costs at your current tier.
Then ask three questions of each one. Is the feature native now? Atlassian keeps shipping, and features that needed an app a few years ago sometimes no longer do. Is it used by a small subset of people? Is it one feature out of a large app?
What a custom Forge app is
Forge is Atlassian’s own platform for building apps. A Forge app runs on Atlassian’s infrastructure, inside your site, and an app built for your organisation can be installed privately without ever being listed on the Marketplace.
That matters for three reasons. Your security review covers a platform you have already approved, the same way it does for Marketplace apps built on Forge. There is no per-user price: you are not paying a thousand-user tier for thirty users. And the app does exactly what your teams need and nothing else, so there are forty fewer features to configure, explain and keep secure.
When three single-feature apps share a theme, one small Forge app with three modules can often replace all of them.
What it costs you instead
A custom app is not free, and pretending otherwise is how these projects disappoint:
- Building it. A small, focused app is days or weeks of work, not months, but it is real work.
- Maintaining it. Atlassian evolves the platform, deprecates APIs and changes requirements. Someone has to keep the app current, which is a small, ongoing commitment.
- Running it. Forge has its own usage-based pricing. A small internal app usually uses little, but it belongs in the budget.
- Supporting it. There is no vendor to raise a ticket with. That is you, or a partner.
The honest comparison is the subscriptions’ cost over three years against the build plus three years of upkeep. Sometimes custom wins clearly. Sometimes it does not.
When to keep buying
Keep the Marketplace app when its feature set is deep and you use a lot of it, test management and advanced reporting are good examples; when it is used broadly and heavily across the site; when the vendor carries certifications or compliance commitments you need; or when the app is cheap enough at your tier that the conversation is not worth having.
The short version
Marketplace apps are priced on your whole user count, so an app bought for one team is paid for everyone. Inventory what each app is used for, by how many people, and which features, then ask whether the feature is now native, whether a small subset uses it, and whether it is one feature of a large app. Where several single-feature apps cluster, one custom Forge app can replace them, at the cost of a build and a modest ongoing commitment. That inventory and recommendation is part of what our Atlassian team does.
Planning a move, or cleaning up after one?
We assess Data Center to Cloud migrations, size the ScriptRunner rewrite, move teams off other tools, and clean up what a migration leaves behind. You talk to the people who do the work.
Related reading
Pay for the 20% You Use: Shrinking Your Atlassian App Footprint Without Losing the Workflow
Most Atlassian Marketplace bills pay for features nobody uses. An honest usage audit and a focused custom Forge app turn pay-per-seat-forever into pay-once-you-own-it, with a better fit for your team.
After the Cloud migration: cleaning up what the move left behind
The cutover went well. Then the administrators find (migrated) everywhere: duplicate schemes, roles and screens, and notes under every field. Why the duplicates exist, how to consolidate them safely, and how to keep the new site from drifting back into the old one.
Moving off Smartsheet to Jira and Confluence: what lands where
Move everything to Jira is the wrong plan. A Smartsheet estate is many kinds of things wearing the same grid. How to sort sheets by what they really are, migrate only the live ones, use templates instead of one-offs, and handle the formulas, automations and forms that never move on their own.