Hello all,
I'm wondering if I can get some clarity around this topic as the Forge cost estimator assumes the developer knows the usage of their plugin.
I'm working on a very small plugin that would only index space attributes in JIRA so they can be JQL'd.
The entire plugin is just a manifest.yml file that declares the attributes so they be indexed. Over time we may add more attributes to the index.
The plugin itself does nothing else. It will not be deployed to the marketplace, it'll only be deployed on my employer's JIRA sites.
What would the forge cost be in this instance? The only close thing I can find on the estimator is the "Key Value Store", but I'm not sure of the storage needed for reads/writes to provide my employer an accurate estimate.
Any guidance here is appreciated.
Thank you
Hi @Pierre Ibrahim !
Since your Forge app is purely declarative and only defines attributes in the manifest.yml for Jira JQL indexing, your monthly Forge cost will be $0.
Because the app doesn't execute any backend functions or use Forge Storage (Key-Value), it consumes no billable Forge resources. The entity properties themselves are stored directly on the Jira Cloud platform (updated externally via REST API), which is already included in your existing Jira subscription at no extra charge.
Here is a quick breakdown of how this works:
For more technical details on property indexing and platform quotas, you can check out the official docs:
Hope this helps clear things up for your team!
Forge offers a generous free usage allowance for each service. Even if you generated costs for Atlassian, it would very likely fit this free budget.
We have public apps with ~100 installation and fairly little (but more than zero) logic, they happily fit the free budget.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.