Atlassian Forge Metering

- An Atlassian principal engineer described metering their Forge serverless platform for over 300M daily events with telemetry contracts. - Their architecture uses exactly‑once processing, data lake pipelines, and auditability to support billing trust and chargeback. - The case offers concrete primitives for platform teams that must provide auditable usage metrics and entitlement enforcement. (x.com)

Atlassian says its Forge billing system now processes about 300 million usage events a day, turning app activity into invoices without losing or double-counting records. (atlassian.com) Forge is Atlassian’s serverless platform for Jira and Confluence apps, hosted and scaled by Atlassian rather than by app developers on their own infrastructure. Atlassian says all new extensibility features now ship on Forge, after ending new Connect app publishing on the Marketplace. (developer.atlassian.com 1) (developer.atlassian.com 2) The billing push became urgent when Forge moved to consumption-based pricing on January 1, 2026. Atlassian says developers get a free monthly allowance, with overage charges billed in arrears and first paid invoices generated on February 1, 2026, for January usage. (developer.atlassian.com) A meter in this context is a usage counter with rules attached: one team measures function time in gigabyte-seconds, another measures storage or logs, and all of them emit events in a shared format. Atlassian says each service team must send telemetry that follows a common “telemetry contract,” including units, attribution, and required fields. (atlassian.com) Those events flow from Forge services into StreamHub, Atlassian’s internal event bus, then through a usage pipeline that standardizes, validates, deduplicates, and normalizes records before they reach commerce systems. Atlassian says the same pipeline also feeds usage and cost data back into the developer console and APIs. (atlassian.com) The engineering problem is trust. Atlassian says billing systems on a revenue path cannot behave like a black box, so the platform was built to preserve attribution back to apps and sites and to make usage records auditable across pipeline stages. (atlassian.com) That audit trail matters because Forge pricing is granular. Atlassian’s current schedule charges, for example, $0.000025 per gigabyte-second for Forge Functions over 100,000 GB-seconds a month, $1.005 per gigabyte for log writes over 1 GB, and $1.929 per 1 million SQL compute requests over 100,000 requests. (developer.atlassian.com) Atlassian says volume is expected to keep climbing from roughly 300 million events a day to more than 600 million within six months and 1 billion within a year. That makes the Forge billing stack less like a monthly invoice generator and more like core platform infrastructure that has to stay correct under constant load. (atlassian.com) The company’s account is also a template for other internal platforms that need chargeback, quotas, or entitlement enforcement. Once a platform starts charging by usage, every missing field, duplicate event, and broken attribution chain becomes a finance problem as well as an engineering one. (atlassian.com)

Get your own daily briefing

Scout delivers personalized news, insights, and conversations tailored to your role and industry.

Download on the App Store

Shared from Scout - Be the smartest in the room.