Get Started
  • Forge App Development

The automation only one person knows
The integration held together by a script
The connect app stuck in security review

None of it was meant to be permanent

Trundl builds Forge apps that replace them. Fixed scope. Live in weeks.

Book a Forge Assessment
  • Forge App Development

Sound familiar?

The marketplace app does 80%. The other 20% runs on hope.

Every release of your Connect app dies in security review for
three weeks.

One person built the script that holds it together. That person has
PTO next week

  • Forge App Development

What changes

Your users stop noticing

Forge apps run inside Atlassian. Same UI. Same permissions. Same data residency. Indistinguishable from native.

Security review stops being a project

SOC 2, GDPR, and your internal policies are in the runtime. Teams that used to lose three weeks clear review on the first pass.

The timeline
shrinks

Rapid Deploy methodology. Fixed scope. Defined timeline. This is not our first Forge build.

The 2 am
pages stop

One Atlassian-managed runtime replaces your fragile APIs, aging Connect apps, and undocumented scripts.

  • Our Engagements

Pick your starting point.

Every engagement is fixed scope and defined timeline.

Forge Value Assessment

  • 1 - 2 weeks

Know what to build, what to buy, and what to retire.

Forge Value
Assessment
Stakeholder interviews. Workflow gaps mapped. ROI sized. You get an executive-ready brief with a build/buy/retire recommendation your team acts on Monday.
Deliverables:
Use-case shortlist (5–10 opportunities), reference architectures, compliance notes, T-shirt estimates, prioritized roadmap. Activities: Stakeholder interviews, system and workflow discovery, risk review, ROI sizing.

Forge
Accelerator

  • 2 - 4 weeks

Prove it works before you fund it. Working prototype in your sandbox.

Forge
Accelerator
Working prototype in your sandbox. Tested against your success metrics. Ends with a demo day and a clear go or no-go.
Deliverables:
Working prototype, success metrics dashboard, adoption plan, path-to-production checklist. Activities: Rapid UX flows, Forge event listeners, permissions modeling, user testing, demo day.

Production
Build

  • 4 - 8+ weeks

Same for Hardended. Tested. Documented

Production
Build
Hardened. Tested. Documented. Deployed with a rollout plan that has names and dates on it.
Deliverables:
Production-ready app, full documentation, SLAs, observability dashboards, rollout plan. Activities: Hardening, performance testing, security review, change management, go-live support.

Managed Extensibility

  • mONTHLY
Better every quarter. No new headcount
Managed
Extensibility
Managed releases. Dependency updates. Incident response. Your apps compound value instead of collecting dust.
Deliverables:
Use-case shortlist (5–10 opportunities), reference architectures, compliance notes, T-shirt estimates, prioritized roadmap. Activities: Stakeholder interviews, system and workflow discovery, risk review, ROI sizing.
  • Know Your Options

Forge vs Connect vs custom APIs

Three ways to extend Atlassian. One has the lowest total cost of ownership.

Forge

Security

Sandboxed runtime. Data residency by default.

Speed

Weeks. No infrastructure to build.

Governance

Scoped permissions. Atlassian-managed updates.

Maintenance

You maintain app logic. Atlassian maintains the rest.

Adoption

Native UI. Zero friction.

Connect

Security

Your infrastructure. Your compliance burden.

Speed

Months. You host everything.

Governance

Self-managed. Manual update cycles.

Maintenance

You maintain the full stack.

Adoption

iFrame-based. Users notice.

Custom API

Security

Fully custom. Fully your responsibility.

Speed

Months to quarters. Full stack.

Governance

No built-in governance.

Maintenance

Highest ongoing burden.

Adoption

Separate experience. Training required.

  • Forge is not always the answer. But when it is, the gap between Forge and the alternatives is not close.
  • Know Your Options

Forge vs Connect vs custom APIs

Three ways to extend Atlassian. One has the lowest total cost of ownership.

Security

Speed

Governance

Maintenance

Adoption

Forge

  • Sandboxed runtime. Data residency by default.
  • Weeks.
    No infrastructure to build.
  • Scoped permissions. Atlassian-managed updates.
  • You maintain app logic. Atlassian maintains the rest.
  • Native UI.
    Zero friction.

Connect

  • Your infrastructure. Your compliance burden.
  • Months. You host everything.
  • Self-managed. Manual update cycles.
  • You maintain the full stack.
  • iFrame-based. Users notice.

Custom API

  • Fully custom. Fully your responsibility.
  • Months to quarters. Full stack.
  • No built-in governance.
  • Highest ongoing burden.
  • Separate experience. Training required.
  • Forge is not always the answer. But when it is, the gap between Forge and the alternatives is not close.
  • Get Started

Two weeks to a decision you can act on.

One business day to respond. 30-minute scoping call. No pitch.

  • Also From Trundl

Related Atlassian services

Marketplace Apps

When an existing app fits but needs configuration.

Custom Jira Apps

When the requirement goes beyond Forge.

Atlassian Integrations

Salesforce. ServiceNow. Slack. The connections.

  • FAQs

Common questions about Forge app development

What is Atlassian Forge?

Forge is Atlassian’s cloud-native app development platform. Apps built on Forge run inside Atlassian’s own infrastructure, which means data stays within Atlassian’s trust boundary, permissions are scoped automatically, and there is no separate hosting to manage. For enterprise teams, it is the most governed path to extending Jira, JSM, and Confluence with custom functionality.

Connect apps run on your infrastructure and render inside Atlassian products via iFrames. Forge apps run directly within Atlassian’s sandboxed runtime. In practice, Forge gives you data residency by default, Atlassian-managed security updates, and a native UI that users cannot distinguish from core product features. Connect offers more architectural flexibility but shifts the entire compliance and hosting burden to your team.

A typical assessment takes one to two weeks. A proof of concept runs two to four weeks. A production build ranges from four to eight weeks depending on complexity. Rapid Deploy methodology uses fixed scopes and defined timelines, so both sides know exactly what the engagement looks like before it starts.

Forge runs inside Atlassian’s FedRAMP-authorized, SOC2-certified cloud infrastructure. Data residency controls are available by default. Your app inherits Atlassian’s compliance posture rather than needing to build its own. A compliance review is included in every Forge Assessment to map the platform against your specific regulatory requirements.

A use-case shortlist of five to ten opportunities, reference architectures for priority items, compliance notes, T-shirt cost estimates, and a prioritized roadmap. The output is an executive-ready brief with a build, buy, or retire recommendation for each use case. The goal is a clear decision framework, not a pitch for more work.

In many cases, yes. The assessment evaluates your current Connect apps and flags which ones are strong candidates for migration based on complexity, maintenance cost, and compliance requirements. Not every Connect app needs to move, but the ones that do typically see reduced maintenance overhead and a stronger security posture.

Forge has platform constraints, particularly around long-running processes and certain UI customizations. Those limits surface during the assessment, not after the build starts. When Forge is not the right fit, the recommendation covers alternatives including Connect, marketplace apps, or custom integrations. The assessment exists specifically so your investment goes to the right path, even if that path is not Forge.

Can't find your answer?

Contact Us
What is Atlassian Forge?

Forge is Atlassian’s cloud-native app development platform. Apps built on Forge run inside Atlassian’s own infrastructure, which means data stays within Atlassian’s trust boundary, permissions are scoped automatically, and there is no separate hosting to manage. For enterprise teams, it is the most governed path to extending Jira, JSM, and Confluence with custom functionality.

Connect apps run on your infrastructure and render inside Atlassian products via iFrames. Forge apps run directly within Atlassian’s sandboxed runtime. In practice, Forge gives you data residency by default, Atlassian-managed security updates, and a native UI that users cannot distinguish from core product features. Connect offers more architectural flexibility but shifts the entire compliance and hosting burden to your team.

A typical assessment takes one to two weeks. A proof of concept runs two to four weeks. A production build ranges from four to eight weeks depending on complexity. Rapid Deploy methodology uses fixed scopes and defined timelines, so both sides know exactly what the engagement looks like before it starts.

Forge runs inside Atlassian’s FedRAMP-authorized, SOC2-certified cloud infrastructure. Data residency controls are available by default. Your app inherits Atlassian’s compliance posture rather than needing to build its own. A compliance review is included in every Forge Assessment to map the platform against your specific regulatory requirements.

A use-case shortlist of five to ten opportunities, reference architectures for priority items, compliance notes, T-shirt cost estimates, and a prioritized roadmap. The output is an executive-ready brief with a build, buy, or retire recommendation for each use case. The goal is a clear decision framework, not a pitch for more work.

In many cases, yes. The assessment evaluates your current Connect apps and flags which ones are strong candidates for migration based on complexity, maintenance cost, and compliance requirements. Not every Connect app needs to move, but the ones that do typically see reduced maintenance overhead and a stronger security posture.

Forge has platform constraints, particularly around long-running processes and certain UI customizations. Those limits surface during the assessment, not after the build starts. When Forge is not the right fit, the recommendation covers alternatives including Connect, marketplace apps, or custom integrations. The assessment exists specifically so your investment goes to the right path, even if that path is not Forge.