Custom apps · Atlassian Cloud · built on Forge
Two situations bring people here. A migration from Server or Data Center has a part that does not move — an in-house plugin, ScriptRunner scripts written in Groovy, a Marketplace app whose Cloud edition does less. Or a team already on Atlassian Cloud needs something no Marketplace app does. In both we build the Forge app — or tell you, before the build starts, that Cloud cannot do it.
For Solution Partners and migration teams. These three stop a cut-over more often than the data does.
Built in-house years ago, or bought from a vendor that never went to Cloud — a Jira workflow extension, a Confluence macro the customer’s process depends on. We rebuild what Atlassian Cloud’s APIs allow as a Forge app, and say plainly which parts they do not.
Scripted listeners, post-functions and scheduled jobs call a Java API that Cloud does not have. Some move to ScriptRunner’s own Cloud edition or to Automation, and we say so when they do. The rest we re-implement with Forge triggers, workflow modules and the REST APIs.
The app exists in Cloud, but the one feature the customer relies on did not make it across. A small companion app can fill that gap instead of holding up the cut-over.
No migration needed to be here. If Jira or Confluence Cloud is where the work happens and an app is missing, this is the same job.
An issue panel, a custom field, a workflow check, a dashboard gadget, a Confluence macro — built around how your team actually works instead of bending the process to what an app happens to offer.
Not everything belongs on the Marketplace. We build private apps installed by link on your site — the way the Enterprise edition of Automation Map is distributed.
Jira or Confluence connected to a system of your own, a report nobody can build from the standard gadgets, data from Assets where people need to see it. Built on Atlassian Cloud’s APIs.
The apps below are ours and are on the Atlassian Marketplace today — for Jira, for Jira Service Management, and Feedback for Confluence. A custom app gets the same engineering.
Our custom work is covered by non-disclosure agreements, so you will find no client names and no case studies on this page. On a call we can walk you through how a comparable case was approached — without naming anyone. MOY Apps on LinkedIn
Code that ran inside Jira’s or Confluence’s own process, direct database access, deep changes to their own screens — Cloud does not offer those. We name those parts in the scoping, before the build starts.
If Automation, the Cloud edition of the app you already use, or an app on the Marketplace — ours or somebody else’s — does the job, we say so. Bulk changes to Jira schemes, roles and fields, for one, are what Bulker already does.
For Jira, Jira Service Management and Confluence — no new Server or Data Center plugins. Forge is Atlassian’s platform for Cloud apps, and it keeps the app’s data inside the Atlassian site it is installed on.
Moving data, users and projects stays with the Solution Partner running it. We take the part that has no Cloud equivalent, and fit into your plan.
Yes. A migration is one reason to need a custom app, not the only one. If Jira or Confluence Cloud lacks something your team needs and no Marketplace app provides it, describe it and we will tell you whether Forge can do it.
Both. Where a Solution Partner runs a migration, we work to their plan and timeline. An organisation without a partner can write to us directly.
Script by script. Groovy written against Server’s Java API does not run in Cloud. Some scripts can be rewritten for ScriptRunner’s Cloud edition or replaced by Automation; the ones that cannot, we re-implement as a Forge app. The scoping says which is which.
Rarely all of it. Cloud apps run outside Jira and Confluence and talk to them through their APIs, so anything that relied on running inside the product has to be redesigned. Often the need behind it can be met another way; we say which part cannot, before the build.
That is agreed per project and written into the scope: who owns the source code, who maintains the app, and what happens when Atlassian changes the platform. Tell us the arrangement you need.
That can be arranged. Who faces the customer is agreed per project and written into the scope, like ownership and support.
Either a fixed price for the project or time and materials, depending on the case. There is no price list; the quote follows the scoping and covers exactly that scope.
In Forge hosted storage, inside the Atlassian site the app is installed on. If a design needs an outside service, the scope says so before the build, because it changes what a security review has to look at.
Two or three sentences are enough to start. The form files a ticket in our service desk, and a person replies within one working day.