Capable builds apps that teams depend on every day - diagrams, calendars, approvals, publishing, markdown, and more - all running natively inside Confluence and Jira. As the suite has grown, so has the scale: Capable apps now process 12 million invocations per month, sustaining roughly 15,000 invocations per hour across the entire product family.

Every one of those invocations runs on Atlassian Forge - Atlassian's serverless, cloud-native app platform.

Here's how - and why - that matters.

Why Forge?

Forge is Atlassian's next-generation development platform. It shifts responsibility for hosting, runtime, and core infrastructure from app vendors to Atlassian itself. Apps built on Forge run in a managed, serverless environment, with auto-scaling, security isolation, and data residency handled at the platform level.

Starting September 2025, all new Marketplace apps must be built on Forge, and legacy Connect support is being phased out. For Capable, this isn't a migration - it's where the apps have been built from day one.

12 Million Invocations. No Overhead.

Capable's product suite spans eleven apps across Confluence and Jira:

• Capable for Confluence - our all-in-one suite that combines all of our features into one app.
• Diagrams for Confluence/Jira - Excalidraw, drawio-compatible, BPMN, Mermaid, PlantUML, and 20+ more.
• Calendars for Confluence - Team scheduling and deadline management within Confluence
• Approvals for Confluence - Structured approval workflows for Confluence pages
• Publishing for Confluence - Publish Confluence content externally
• Markdown for Confluence/Jira - Markdown rendering for Confluence and Jira
• Assets, Macros, Search - Utility apps enhancing core Confluence functionality

Together, these apps handle 12 million function invocations per month. At peak, that's 15,000 invocations hitting Forge every hour. Forge's serverless architecture absorbs this automatically - scaling up during busy working hours across global time zones and scaling down during quieter periods - without a single server to provision or monitor.

All Data Stored in Atlassian

User-defined data (UGC) - approvals, diagrams, calendar events - lives natively within your Confluence or Jira instance.

Diagrams are processed securely and they are handled transiently and never stored in our infrastructure.

We are planning to make all of our apps 'Runs on Atlassian' (RoA) and 'Architected for Atlassian' (A4A) as the necessary features become available, such as Forge Containers and Customer Managed Egress. This transition is projected for the end of 2026 and will enhance customer trust by ensuring even greater integration and reliability and reducing our infrastructure even further.

The only external storage required at the moment is for Slack integration with the Approvals feature, which can be easily disabled if not needed from the global settings and is not applicable for apps that don't provide approvals.

Reliability at Scale

Handling 15,000 invocations per hour (that's 250 requests each minute!) demands robust engineering. Capable respects Forge's rate limits through efficient design - smart batching, pre-filtering, async processing where needed. This delivers consistently low error rates and reliable performance at volume.

Every invocation runs in its own isolated environment - spun up and destroyed per request, ensuring zero cross-tenant interference. The architecture degrades gracefully, with platform-managed retries for transient issues.

Capable instruments every invocation, tracking execution duration, error rates, and throughput across all eleven apps. This data drives continuous optimization, keeping performance tight even as usage grows.

Security Without Compromise

Forge apps run entirely within Atlassian's security perimeter:

• Platform-enforced isolation: Per-invocation sandboxes, no shared state
• Data residency compliance: Executes in your product's region
• Atlassian-managed auth: No vendor credentials needed
• "Runs on Atlassian" qualified where possible: Minimal external dependencies

This security is structural - enforced by the platform itself.

Why This Matters for Customers

When a team installs Capable Diagrams and an engineer creates a C4 architecture diagram, or a project manager sets up an approval workflow, they shouldn't think about infrastructure. They shouldn't wonder where their data lives, whether the app will slow down their instance, or what happens at scale.

Forge turns infrastructure into a platform guarantee. For Capable customers, this means:

• Consistent performance - Auto-scales whether serving 100 or 100,000 users
• Enterprise-grade security - Platform-enforced controls, no extra reviews
• Minimal downtime risk - Serverless eliminates single points of failure
• Future-proof - Benefits from Atlassian's ongoing Forge investments

Built for What Comes Next

12 million invocations per month is today's number. As Diagrams adds libraries, Approval workflows grow more sophisticated, and Publishing reaches wider audiences - that number will climb.

Building on Forge means scaling up requires no architectural changes. The platform handles it. Capable stays focused on features that help teams communicate visually, work efficiently, and ship with confidence.

Atlassian built Forge to be the foundation of the next generation of cloud apps. Capable is proud to be building on that foundation - at scale, securely, and reliably.

Capable builds apps for Confluence, Jira, and monday.com. Recognised as an Atlassian Codegeist 2024 Winner and Partner of the Year Finalist (x2), Capable is trusted by teams worldwide for diagramming, approvals, calendars, publishing, and more.

Find out more about Atlassian Forge