Custom apps for Jira and Confluence
When the Marketplace has no app for it, we build one: Forge apps for Atlassian Cloud and plugins for Data Center, specified, tested and supported.
When a custom app makes sense
Most needs are met by configuration, automation rules or an existing Marketplace app, and we check those first. A custom app earns its place when the logic is specific to your business, when data has to move between Jira and an in-house system, or when a Marketplace app does a tenth of what you need at the price of the whole.
- Approval matrices and validations that follow your own rules
- Custom fields and issue panels filled from your ERP, CRM or HR system
- Integrations with in-house systems through REST APIs and webhooks
- Confluence macros that show live data from Jira or your own services
- Jira Service Management portal extensions and imports into Assets
- Reports and dashboard gadgets the built-in ones cannot do
Atlassian Cloud: Forge apps
On Cloud we build with Forge, Atlassian's own app platform. The app runs on Atlassian's infrastructure, so there is no server for you to host, patch or secure, and an app that keeps its data inside Atlassian can follow your Cloud data residency. The interface uses UI Kit or Custom UI, data lives in Forge storage or behind your own API, and the app is installed privately on your site or listed on the Marketplace.
Private app or Marketplace listing
Most custom apps are installed only on your site. If the app is useful to other companies, we can prepare it for a Marketplace listing.
Moving Connect apps to Forge
Atlassian is phasing out Connect in favour of Forge. We move existing Connect apps to Forge so they keep working.
Data Center: plugins
On Jira, Confluence and Jira Service Management Data Center we build P2 plugins with the Atlassian Plugin SDK, installed through the Universal Plugin Manager. Because these products become read-only on 28 March 2029, we design new Data Center work so its logic can move to Forge, and we can build the Cloud version alongside your migration.
How we build
The same way for a small validator and for an integration with your ERP.
- A written specification and a mock-up of the screens before any code
- A staging site for testing before anything reaches production
- Automated tests for the business rules
- Documentation for admins and a short guide for the people who use the app
- Updates when Atlassian changes its APIs, under a support agreement
What it costs
A custom app is priced from the written specification: a fixed price for a defined scope, or a day rate for work that will keep evolving. The effort depends on the number of screens and integrations, whether the app must run on Cloud, Data Center or both, and how much existing data it has to handle. A field validator or an issue panel is a small job; an integration with an in-house system is a project of weeks. Support and updates after launch are a monthly fee.
Trusted by
Questions we get asked
Forge or Connect?
Forge, for anything new. Atlassian is phasing out Connect, and Forge apps run on Atlassian's infrastructure with no separate hosting.
Can one app work on both Cloud and Data Center?
Not as the same package: Forge apps and Data Center plugins are built differently. We keep the business rules in one place where we can, so the two versions behave the same.
Does our data leave Atlassian Cloud?
Not if the app only uses Forge storage and Atlassian's APIs. If it has to talk to your own systems, we show you which data goes where before we build.
Who owns the source code?
That is agreed in the contract before work starts, including whether the code is handed over to you.
Talk to a certified admin
Tell us what you run and where it hurts. One call tells you what we would do first.
Donatas Jonušas
Chief Business Development Officer, TeamBit
