Bitbucket
Platform · this deep dive is built from the official pages of the platform itself and of the tools that support it.
Overview
Bitbucket is a Git repository hosting service from Atlassian (Australia), built into the company's own ecosystem: Jira, Jira Service Management, Atlassian Administration. Atlassian itself describes the product as "Code & CI/CD, powered by AI and the Atlassian platform" and puts the emphasis on tying code to Jira issues and on the Pipelines build system.
As a place to work with an audience, this platform is nothing like the social networks you are used to. Bitbucket has no feed, no following of authors, no recommendations and no ad manager. A public repository here is a way to hand out code and documentation, not a way to gather readers. Most workspaces are private: the product is sold to teams, not to authors.
One important detail: for commercial pages the bitbucket.org address leads away to the Atlassian site — during our check bitbucket.org/product/pricing returned a 302 redirect to atlassian.com/software/bitbucket/pricing. The rules and the help centre also live on Atlassian domains, not on Bitbucket ones.
Who's here
The only quantitative claim about the audience that we found on the official product page is a statement by Atlassian itself: "15 million developers build on Bitbucket", that is, 15 million developers. This is a company's marketing claim about its own product, not an independent measurement; the page does not spell out the period over which "build on" is counted, and the figure carries no date.
Bitbucket does not publish breakdowns by country or language. According to our check of the page markup, the interface language of the homepage is English; we found no declared language versions in the homepage markup.
An indirect indication of who is here is the design of the product itself: workspaces with paid seats, integration with Jira, corporate access management through Atlassian Administration. This is a platform for teams, not for individual authors.
Getting started
The basic unit is not an account but a workspace. The help centre describes it like this: "A workspace is where you will create repositories, collaborate on your code, and organize different streams of work in your Bitbucket Cloud account". Repository addresses are built from its identifier: www.bitbucket.org/<workspace ID>/<repo name>, and changing the identifier changes every link to repositories, snippets and static sites. Choose the identifier once and for the long term.
The creation flow has changed: the help centre states that workspaces are no longer created in Bitbucket but in Atlassian Administration, which is also where user management happens. An alternative for a small team is to create a project inside an existing workspace and assign permissions there.
Plans. The pricing page lists: Free — $0 for up to 5 users; Standard — $3.65 per user per month; Premium — $7.25 per user per month. The same page states that extra resources are bought in packs: 1,000 build minutes or 100 GB for $10 a month, and that academic and community subscriptions come with 5 GB of LFS storage and 500 Pipelines minutes for free.
What each plan includes, according to the help page on plans and billing: Free — 50 build minutes a month and 1 GB of large file storage; Standard — 2,500 minutes and 5 GB; Premium — 3,500 minutes and 10 GB. Overage charges are on the same page: $10 per 1,000 additional build minutes per billing period and $10 per 100 GB of storage.
What you can publish
The content here is repositories, files, snippets, wiki pages and pull request discussions. Atlassian frames the size limits as thresholds a repository crosses as it grows: at 2.0 GB a warning appears telling you that you are more than halfway to the 4 GB limit, and once 4 GB is exceeded pushes stop being accepted with the message "Repository is over the size limit (4 GB) and will not accept further additions". The same page says that by default there is a block on pushing files larger than 100 MB.
Prohibited content is defined by Atlassian's acceptable use policy (in force since 7 October 2025). It names explicitly: creating and sending chain letters and spam; approaching users of the service for commercial purposes without express permission from Atlassian; promoting or advertising someone else's goods and services without proper authorisation. Separately prohibited is material that is false, misleading, deceptive, fraudulent, unlawful, obscene, defamatory, threatening or harmful.
How to grow
Plainly and honestly: Bitbucket provides no tools for growing an audience. There is no feed here, no following an author's profile, no recommendations, no trends and no internal search by interest. A public repository gets found through an external link or through a search engine, not inside the platform.
Bitbucket has no ad manager — none of the official pages we checked describe paid placement. What is more, Atlassian's general policy prohibits approaching users of the services for commercial purposes without the company's express permission. That means mailings to addresses harvested from commits and profiles, as well as advertising your own product in other people's pull requests, are a rule violation, not a promotion technique.
On the help pages we checked we found no built-in public analytics for authors (repository page views, referral sources). The analytics in the product are about engineering effectiveness, not about reach.
What does work: tying the repository to Jira issues, clear documentation in the wiki and the readme, and being present where your target audience actually lives — that is, outside the platform itself.
Path to monetization
Bitbucket does not pay authors for content. No revenue-sharing programme, donations or profile subscriptions are described on the pages we checked.
An indirect way to earn money around the platform is the Atlassian Marketplace: it publishes a storefront of apps for Bitbucket with "Top-selling", "Newest" and "Trending" sections, which means paid apps for Bitbucket exist and are being sold. The page does not give a total number of apps for Bitbucket.
For teams the economics run the other way: the platform does not pay you, you pay it — $3.65 or $7.25 per user per month plus overage on minutes and storage.
Tools and automation
Bitbucket Cloud does have a REST API, and the request limits are published. The help centre lists: anonymous requests — a strict limit of 60 requests per hour; Git operations — 60,000 requests per hour; raw file requests — 5,000 per hour; archives — 1,500 files per hour; repository data — from 1,000 to 10,000 per hour; webhook data — 1,000 per hour; app properties — 2,000 per hour; sending invitations — 100 requests per minute.
The scaled limit is worked out with a formula and does not apply to everyone: the help centre gives the example "1,000 + (500 - 100) * 10 = 5,000" with a ceiling of 10,000 requests per hour and notes that the raised limits are available to workspaces on Standard or Premium with at least 100 paid users. The X-RateLimit-Limit and X-RateLimit-NearLimit response headers help you track consumption.
Builds. Pipelines is limited by more than minutes: up to 100 steps per pipeline; on the Free plan up to 10 parallel steps; a pipeline is skipped if a push touches more than five tags, bookmarks or branches.
Limits and rules
- Users. The Free plan — no more than 5 users.
- Repository. Warning from 2 GB, push blocked from 4 GB, files from 100 MB blocked by default.
- Builds. 50 / 2,500 / 3,500 minutes a month by plan, $10 extra per 1,000 minutes; 100 steps per pipeline, 10 parallel steps on Free.
- API. 60 requests per hour anonymously, up to 10,000 per hour for large paid workspaces.
- Conduct. Spam and chain letters are banned, as are commercial approaches to users without permission from Atlassian and advertising other people's products without authorisation.
- Administration. Workspaces and users are managed in Atlassian Administration, not in Bitbucket itself.
Who it's for
It suits teams that already work in Jira: tying code to issues is the product's main selling point, and it is stated on its page. It suits small teams of up to five people for whom the free plan is enough, with a caveat about the 50 build minutes a month — that is not much for active CI.
It does not suit you as a promotion channel. There is nothing to "grow" here: no feed, no followers, no advertising, no reach statistics. If your goal is to show an open project to a developer audience, Bitbucket will be a mirror, and you will have to make some other platform the shop window.
It does not suit projects that count on monetizing their content: the platform does not pay authors, it charges you for seats.
Verified data
The checked data this deep dive rests on.
About the platform
an Atlassian product; the official page describes it as "Code & CI/CD, powered by AI and the Atlassian platform"
source, checked 2026-07-28
bitbucket.org/product/pricing returns a 302 to atlassian.com/software/bitbucket/pricing — commercial and legal pages live on Atlassian domains
the redirect was recorded during the check
source, checked 2026-07-28
Who's here
Atlassian claims: "15 million developers build on Bitbucket" (15 million developers)
a marketing claim by the company about its own product; no period or date is given for the figure
source, checked 2026-07-28
Getting started
workspaces are no longer created in Bitbucket but in Atlassian Administration, which is also where user management happens
source, checked 2026-07-28
Account and access
the basic unit is a workspace; addresses are built as www.bitbucket.org/<workspace ID>/<repo name>, and changing the identifier changes every link to repositories, snippets and static sites
source, checked 2026-07-28
How the money works here
the platform does not pay authors: no revenue-sharing programmes, donations or subscriptions are described on the pages checked; earning money around the platform is possible by selling apps in the Atlassian Marketplace
the storefront shows Top-selling / Newest / Trending selections; no total number of apps for Bitbucket is given
source, checked 2026-07-28
Pricing
Free — $0 for up to 5 users; Standard — $3.65 per user per month; Premium — $7.25 per user per month
source, checked 2026-07-28
extra resources: 1,000 build minutes or 100 GB for $10 a month; academic and community subscriptions — 5 GB LFS and 500 Pipelines minutes free
source, checked 2026-07-28
included in the plan: Free — 50 build minutes a month and 1 GB of large file storage; Standard — 2,500 minutes and 5 GB; Premium — 3,500 minutes and 10 GB
source, checked 2026-07-28
overage charges: $10 per 1,000 additional build minutes per billing period and $10 per 100 GB of storage
source, checked 2026-07-28
Limits and restrictions
at 2.0 GB a warning appears about being more than halfway to the 4 GB limit; once 4 GB is exceeded a push is not accepted ("Repository is over the size limit (4 GB) and will not accept further additions")
source, checked 2026-07-28
pushing files larger than 100 MB is blocked by default
source, checked 2026-07-28
Pipelines: up to 100 steps per pipeline; up to 10 parallel steps on the Free plan; a pipeline is skipped if a push touches more than five tags, bookmarks or branches
maximum build time, memory and artifact size are not named on the page
source, checked 2026-07-28
Restrictions
Atlassian's acceptable use policy prohibits chain letters and spam, approaching users of the services for commercial purposes without express permission from Atlassian, and promoting or advertising someone else's goods and services without proper authorisation
the policy came into force on 7 October 2025
source, checked 2026-07-28
API access
API limits: anonymous — 60 requests per hour; Git operations — 60,000 per hour; raw files — 5,000 per hour; archives — 1,500 files per hour; repository data — 1,000–10,000 per hour; webhooks — 1,000 per hour; app properties — 2,000 per hour; invitations — 100 requests per minute
source, checked 2026-07-28
scaled limit calculated by a formula, example on the page "1,000 + (500 - 100) * 10 = 5,000", ceiling of 10,000 requests per hour; available to Standard/Premium workspaces with 100+ paid users
consumption is tracked with the X-RateLimit-Limit and X-RateLimit-NearLimit headers
source, checked 2026-07-28
Languages
the interface language of the home page: en
The language is taken from the markup attribute, the versions from hreflang
source, checked 2026-07-28
Catalogue section: all similar See also: catalogue index · region: Australia and Oceania · scheduler comparison · find by situation · platform restrictions