Forge apps that feel like Atlassian.
We build on Atlassian Forge - the modern, serverless app platform for Jira, Confluence, and Jira Service Management. Marketplace-ready or private, UI Kit or Custom UI, we know the stack and the review process end to end.
Six surfaces across the Atlassian ecosystem.
Forge gives you access to Jira, Confluence, and JSM. These are the surfaces we're asked to build on most.
Jira issue panels
Custom panels that appear on every issue, pulling context from external systems or enriching the issue with data your team needs without leaving Jira.
Project & global pages
Full-page Forge apps scoped to a project or available site-wide. Dashboards, admin tools, reports - anything that needs more than a panel.
Confluence macros
Inline and block macros that bring live data into Confluence pages. Dynamic content, not just embeds.
Content byline & actions
Byline items and content actions that extend Confluence pages - add reviewers, trigger workflows, surface approval status, all without leaving the page.
JSM portal & queue customisation
Custom fields, portal extensions, and queue views for Jira Service Management. We know the JSM data model and the limits of what Forge can do inside it.
Marketplace submission
Listing copy, screenshots, security review responses, privacy policy, EAP navigation. We've been through Atlassian's review process enough times to know the path.
A team that's navigated Forge from day one.
Forge is still evolving. Working with a team that's tracked it from the start is worth more than it sounds.
Forge runtime fluency
We know the sandbox limits, the async invocation model, the storage APIs, the remote call constraints - and how to build around them without working against them.
UI Kit and Custom UI
Both rendering models, chosen for the right reason. UI Kit for speed and Atlassian-native feel; Custom UI when the app needs it. We don't default to one.
Connect migration
If you have an older Connect app, we know the migration path - what Forge can replace directly and what needs rethinking. We won't promise a lift-and-shift that isn't real.
OAuth 2.0 & scopes
Atlassian's permission model is granular and matters at review time. We scope apps correctly from the start rather than patching after rejection.
Enterprise readiness
Multi-tenant data isolation, admin-controlled settings, audit logging. The things enterprise procurement checklists ask about, handled as first-class concerns.
Post-launch support
30 days included after launch. Retainer optional after that. Either way, you get the runbooks and the knowledge transfer before we leave.
A predictable shape, with room for the work to surprise us.
Every project is different in the middle. The beginning and end aren't.
Conversation
A call. We listen to what you're trying to build, ask hard questions about what Forge can and can't do, and leave with enough to write a proposal - or the conviction that we're not the right fit.
Discovery sprint
We map the app to Forge's surfaces and permissions, sketch the user flows, and produce a written architecture document. You decide whether to go ahead.
Build
Weekly demos. A shared channel. A staging install on a real Jira or Confluence site from day one. You see the app grow in the actual environment.
Submit & handover
Marketplace submission if you're going public. Code handover, deployment runbook, and 30 days of post-launch support included. Retainer optional after that.
Have an Atlassian Forge project in mind?
Tell us the shape of what you're trying to build. We'll tell you whether we're the right fit, and what a realistic plan looks like.
Contact us