Jira Cloud Free
atlassian.com · 8 records in Compute, Storage · JSON
Records 8
- caveatBitbucket Pipelines
Computefree tieridentity emailcard?limit write-gatedevidence documentedstale on 2026-12-05
- caveatAtlassian Confluence Cloud Free
Storagefree tieridentity email?card?limit per-object-capevidence reportedstale on 2026-11-05
- caveatAtlassian Confluence Premium via Social Impact (nonprofit) License — unlimited file storage
Storagefree tieridentity card?card?limit per-object-capevidence reportedstale on 2026-11-05
- fails: quotabitbucket cloud free
Storageidentity email?card?evidence reportedstale on 2026-11-05
- fails: quotaBitbucket Cloud Git LFS
Storagefree tieridentity card?card?limit per-object-capevidence reportedstale on 2026-11-05
- fails: quotaConfluence Cloud Free
Storagefree tieridentity institution?card?limit per-object-capevidence reportedstale on 2026-11-05
- fails: quotaconfluence standard/premium as a free route
Storageidentity email?card?evidence reportedstale on 2026-11-05
- fails: quotaJira Cloud Free
Storagefree tieridentity email?card?evidence reportedstale on 2026-11-05
Bitbucket Pipelines
Compute- Free allowance
- 50 build minutes a month on the Free plan, at $0 for up to 5 users, with 1 GB of Git LFS storage in total, up to 100 steps per pipeline and up to 10 concurrent steps; no overage protection on Free
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- emailcard unknown, no phone
- Binding limit
- write-gatedpast 5 users the workspace must move to Standard at $3.65 a user a month
- Evidence
- documented21 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-12-05checked 2026-11-04 (live); stale on 2026-12-05
| Free tier | 50 build minutes a month on the Free plan, at $0 for up to 5 users, with 1 GB of Git LFS storage in total, up to 100 steps per pipeline and up to 10 concurrent steps; no overage protection on Free unit minutes; metered on wall-clock |
|---|---|
| Price | none stated |
| Limits |
a step times out after 120 minutes by default, and max-time accepts 1 to 720 minutes; sizes 4x and up are limited to Standard and Premium |
| Identity | email an Atlassian account; the Free plan covers up to 5 users, and the billing documentation charges a credit card on file only for monthly Standard or Premium plans after a 30-day evaluation; whether the Free sign-up form asks for a card is unverified: the form renders client-side |
| Egress | not published: https://www.atlassian.com/software/bitbucket/pricing and https://support.atlassian.com/bitbucket-cloud/docs/limitations-of-bitbucket-pipelines/ state no data-transfer allowance or overage price |
| Per-object cap | not stated |
| Retention | not stated |
| Interface | rest, git Bitbucket REST API (OpenAPI spec published) and Git |
| Tooling | not stated |
| Reliability | no reliability event recorded |
| Notes | free plans cannot buy extra build minutes or LFS storage beyond the plan allowances; on paid plans extra minutes are $10 per 1,000 |
| Evidence note | documented documented from the Pipelines limitations page, the pricing page and the step-options page; the 1x size table and the prose of the step-options page disagree on the CPU count (2 against 4) |
| Parsed numbers |
|
Evidence 21
| date | source | what it proved |
|---|---|---|
| 2026-10-02 | www.atlassian.com/software/bitbucket/pricing | not published |
| 2026-10-22 | www.atlassian.com/software/bitbucket/pricing | 'Free forever for up to 5 users' at $0, with Standard $3.65 and Premium $8 per user a month, quoted; the page's build-minute definition is in a collapsed section it does not render |
| 2026-10-30 | support.atlassian.com/bitbucket-cloud/docs/limitations-of-bi | the Free plan includes 50 build minutes a month for up to 5 users |
| 2026-10-30 | support.atlassian.com/bitbucket-cloud/docs/limitations-of-bi | the Free allowance is a number of build minutes |
| 2026-10-30 | www.atlassian.com/licensing/bitbucket | build minutes are pipeline execution time |
| 2026-10-30 | www.atlassian.com/software/bitbucket/pricing | the Free plan includes 50 build minutes |
| 2026-10-30 | support.atlassian.com/bitbucket-cloud/docs/step-options/ | a 1x step has 2 CPU, 4 GB memory and a 64 GB volume |
| 2026-10-30 | support.atlassian.com/bitbucket-cloud/docs/step-options/ | a step times out after 120 minutes unless max-time is set |
| 2026-10-30 | support.atlassian.com/bitbucket-cloud/docs/step-options/ | max-time can be raised to at most 720 minutes per step |
| 2026-10-30 | support.atlassian.com/bitbucket-cloud/docs/step-options/ | the default step timeout is 120 minutes |
| 2026-10-30 | www.atlassian.com/licensing/bitbucket | the Free plan allowance cannot be extended by purchase |
| 2026-10-30 | support.atlassian.com/bitbucket-cloud/docs/manage-your-plan- | a card on file is tied to the paid Standard and Premium plans |
| 2026-10-30 | support.atlassian.com/bitbucket-cloud/docs/step-options/ | the size table gives 2 CPU for 1x |
| 2026-10-30 | www.atlassian.com/software/bitbucket/features/pipelines | the Pipelines feature page also states 50 minutes a month on Free |
| 2026-10-30 | support.atlassian.com/bitbucket-cloud/docs/step-options/ | the prose gives a default step 4 GB memory, 4 shared CPUs and 64 GB of disk |
| 2026-10-30 | support.atlassian.com/bitbucket-cloud/docs/step-options/ | the Free plan is limited to 1x and 2x steps |
| 2026-10-30 | www.atlassian.com/software/bitbucket/pricing | the Free plan is still offered for up to 5 users |
| 2026-10-30 | www.atlassian.com/software/bitbucket/pricing | Standard is still $3.65 a user a month |
| 2026-10-31 | support.atlassian.com/bitbucket-cloud/docs/limitations-of-bi | the Free row gives $0 for up to 5 users, 50 build minutes a month, 1 GB LFS in total, up to 100 steps per pipeline, up to 10 concurrent steps, and overage protection not included |
| 2026-11-03 | developer.atlassian.com/cloud/bitbucket/rest/intro/ | Bitbucket exposes a REST API and Git access |
| 2026-11-03 | www.atlassian.com/software/bitbucket/pricing | the pricing page lists seats and prices and no data-transfer allowance or price |
More fields 7
| keep rate | 1.0 |
|---|---|
| billing model | unclassified |
| shape | {"vcpu": 2,"ram": 4,"disk": 64,"gpu_class": null,"gpu_count": null,"note": "a default 1x step: 2 CPU, 4 GB memory and a 64 GB volume in the size table, while the prose of the same page says 4 CPUs that might be shared; 2x gives 4 CPU and 8 GB; 4x and larger sizes need a paid plan"} |
| session cap | {"wall_clock_min": 720,"idle_reap_s": null,"restart_required": false,"note": "a step runs for at most 120 minutes by default and at most 720 minutes with max-time"} |
| free tier kind | allowance |
| granularity | {"min_billed_s": 60,"rounding_s": null} |
| burst x | 1.0 |
Unknown values 7
- chaining: a source was read and is silent on this field
- egress metered: egress metering was not published
- per object cap stated: a source was read and is silent on this field
- reliability note: nothing of this kind was observed
- retention notes: the field may be stated in a source that was not read
- retention stated: a source was read and is silent on this field
- tooling: a source was read and is silent on this field
- Free allowance
- 2 GB file storage on the Free plan (10 users, unlimited spaces and pages).
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- email?placeholder, not evidence; card unknown, phone unknown
- Binding limit
- per-object-capper-object-cap: attachment default 100 MB
- Evidence
- reported4 sources; a third party said so
- Freshness
- stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05
| Free tier | 2 GB file storage on the Free plan (10 users, unlimited spaces and pages). Crucially: 'Free, Standard, and Premium plans entitle you to one app instance. You can have as many of these plans as you need. You'll subscribe to each one separately.' Each instance 'will have its own storage'. unit GB; metered on stored-bytes |
|---|---|
| Price | none stated |
| Limits |
per-object-cap: attachment default 100 MB, admin-configurable upward ('Enter your preferred maximum size (in bytes)'). Quota is per-site, not per-org. request-rate: Atlassian Cloud REST rate limits apply. Retention: Free sites are DEACTIVATED after a period of inactivity (logging in and viewing a page counts as activity) — this is the real hazard, not eviction. Over-quota does not delete data, it restricts editing/creating. |
| Identity | email (placeholder) not published |
| Egress | No egress meter anywhere in Atlassian Cloud pricing. Attachments are served from the site domain, not a billed CDN bucket. |
| Per-object cap | per-object-cap: attachment default 100 MB (100000000 bytes) |
| Retention | not stated |
| Interface | rest, rclone part of the text of Limits, above |
| Tooling | Confluence Cloud REST API v2/v1 (/wiki/rest/api/content/{id}/child/attachment), Basic auth with email + API token, or OAuth 2.0. No rclone backend; the API is the client. |
| Composes with | 2 GB x N free Confluence sites, and N is self-service and explicitly unbounded ('as many of these plans as you need'). Ten free sites = 20 GB; a scripted site-creation loop is the multiplier. Community reports confirm multiple free sites per account are allowed and the one-instance limit is a paid-plan construct. |
| Reliability | Nothing is deleted at quota — writes are blocked until you upgrade or free space. But a Free site that goes untouched is deactivated, so a storage-only site needs a periodic login to stay alive. |
| Parsed numbers |
|
Evidence 4
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | support.atlassian.com/confluence-cloud/docs/manage-your-stor | 'Confluence Free- 2 GB / Standard- 250 GB / Premium- Unlimited storage' |
| 2026-10-21 | support.atlassian.com/organization-administration/docs/how-m | 'You can have as many of these plans as you need' |
| 2026-10-21 | support.atlassian.com/organization-administration/docs/track | 'if you have two Confluence instances from two sites, each will have its own storage' + Free-plan inactivity deactivation |
| 2026-10-21 | support.atlassian.com/confluence-cloud/docs/configure-attach | 'The default is 100 megabytes, expressed as 104857600 bytes', admin-adjustable |
Unknown values 3
- per object cap notes: the field may be stated in a source that was not read
- retention notes: the field may be stated in a source that was not read
- retention stated: the field may be stated in a source that was not read
bitbucket cloud free
Storage- Free allowance
- Free workspaces were cut to 1 GB of total repository storage (all repos combined) effective 2025-04-28, delayed to 2025-05-29.
- Verdict
- fails: quotathe free allowance is too small to matter
- Cost
- not stated
- Identity
- email?placeholder, not evidence; card unknown, phone unknown
- Binding limit
- noneno named constraint binds
- Evidence
- reported2 sources; a third party said so
- Freshness
- stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05
| Free tier | Free workspaces were cut to 1 GB of total repository storage (all repos combined) effective 2025-04-28, delayed to 2025-05-29. Free plan also lost the Downloads feature entirely and lost… unit none; metered on none |
|---|---|
| Price | none stated |
| Identity | email (placeholder) not published |
| Egress | not recorded |
| Interface | unknown |
| Tooling | not recorded |
Evidence 2
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | www.atlassian.com/blog/bitbucket/important-changes-coming-to | the text of Free tier, above |
| 2026-10-21 | confluence.atlassian.com/bbkb/what-are-the-repository-and-fi | cited as the basis of the rejection: Free workspaces were cut to 1 GB of total repository storage (all repos combined) effective 2025-04-28, delayed to 2025-05-29. Free plan also lost the Downloads feature entirely and lost sni |
More fields 1
| dead end | {"failure_class": "quota","why": "Free workspaces were cut to 1 GB of total repository storage (all repos combined) effective 2025-04-28, delayed to 2025-05-29. Free plan also lost the Downloads feature entirely and lost…","retry_when": null,"first_recorded": "2026-10-21"} |
|---|
Unknown values 7
- chaining: no value was recorded for this field
- egress terms: no value was recorded for this field
- interface: the access interface was not established
- per object cap notes: no value was recorded for this field
- per object cap stated: no value was recorded for this field
- retention stated: no value was recorded for this field
- tooling: no value was recorded for this field
Bitbucket Cloud Git LFS
Storage- Free allowance
- Free (up to 5 users): 1 GB LFS storage.
- Verdict
- fails: quotathe free allowance is too small to matter
- Cost
- free tier
- Identity
- card?placeholder, not evidence; card unknown, phone unknown
- Binding limit
- per-object-capno per-file cap at all
- Evidence
- reported2 sources; a third party said so
- Freshness
- stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05
| Free tier | Free (up to 5 users): 1 GB LFS storage. Academic 5 GB, Standard 5 GB, Premium 10 GB. Extra storage sold in 100 GB units at $10/month. Notable counter-property: no per-file cap at all. unit GB; metered on stored-bytes |
|---|---|
| Price | none stated |
| Limits |
'there's no limit on the LFS file size you can push to Bitbucket Cloud' — genuinely no per-file cap. Forks do not copy LFS objects (fork points at parent's store, and the fork lacks permission) — so fork-based sharding fails. Repo archives do not include LFS files. |
| Identity | card (inferred, not read) not published |
| Egress | Not metered — Atlassian publishes no LFS bandwidth quota, only storage in 100 GB units. This is the one LFS host where the storage number is small but the transfer side is genuinely unstated/unbilled. |
| Per-object cap | no per-file cap at all |
| Retention | not stated |
| Interface | ssh, git git |
| Tooling | git-lfs. Note: SSH not usable for LFS repos? (not stated) — the documented limitation is that repository transfer and forking both break LFS links; the alternative route is git lfs fetch --all + git lfs push --all. |
| Composes with | 1 GB per free workspace, unlimited free workspaces (each needs an email). 500 workspaces = 500 GB of very awkward storage. Weak: no route to manage many workspaces at once, and the workspace is tied to users. |
| Reliability | Fork/transfer/archive are all documented as broken for LFS repos, which makes recovery awkward. Storage overage is auto-billed in 100 GB increments rather than blocked. |
| Parsed numbers |
|
Evidence 2
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | support.atlassian.com/bitbucket-cloud/docs/storage-policy-fo | 'Free (up to 5 users) | 1 GB'; '100 GB of file storage | Your monthly bill goes up $10' |
| 2026-10-21 | support.atlassian.com/bitbucket-cloud/docs/current-limitatio | 'there's no limit on the LFS file size you can push'; 'the transfer of repositories with Git LFS files is disabled' |
More fields 1
| dead end | {"failure_class": "quota","why": "Free (up to 5 users): 1 GB LFS storage. Academic 5 GB, Standard 5 GB, Premium 10 GB. Extra storage sold in 100 GB units at $10/month. Notable counter-property: no per-file cap at all.","retry_when": null,"first_recorded": "2026-10-21"} |
|---|
Unknown values 3
- per object cap notes: the field may be stated in a source that was not read
- retention notes: the field may be stated in a source that was not read
- retention stated: the field may be stated in a source that was not read
Confluence Cloud Free
Storage- Free allowance
- 2 GB per site on Free (250 GB Standard, unlimited Premium); 100 MB default per attachment, admin-configurable
- Verdict
- fails: quotathe free allowance is too small to matter
- Cost
- free tier
- Identity
- institution?placeholder, not evidence; card unknown, phone unknown
- Binding limit
- per-object-cap100 MB/file
- Evidence
- reported3 sources; a third party said so
- Freshness
- stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05
| Free tier | 2 GB per site on Free (250 GB Standard, unlimited Premium); 100 MB default per attachment, admin-configurable unit GB; metered on unstated |
|---|---|
| Price | none stated |
| Limits |
2 GB hard cap per site — exceeding it freezes page/space creation until you delete content; archived pages still count ('Archiving content that contain attachments will not free up any storage'); 100 MB/file default |
| Identity | institution (inferred, not read) not published |
| Egress | free direct attachment download links, Atlassian media CDN, no egress billing |
| Per-object cap | 100 MB/file (100000000 bytes) |
| Retention | 2 GB per site on Free (250 GB Standard, unlimited Premium); 100 MB default per attachment, admin-configurable | 2 GB hard cap per site — exceeding it freezes page/space creation until you delete content; archived pages still count ('Archiving content that contain attachments will not free up any storage'); 100 MB/file default |
| Interface | rest rest |
| Tooling | Confluence Cloud REST v2 /wiki/api/v2/attachments (documented, OAuth or API token); atlassian-python-api wraps it |
| Composes with | 2 GB x unlimited free sites (10 users each, unlimited free orgs on the same email domain). 500 GB = 250 sites; 20 TiB = 10,000 sites — the site-creation step is the bottleneck, not the API |
| Reliability | the cleanest API of the Atlassian trio and the highest per-file ceiling (100 MB configurable), but the 2 GB bucket is small; multi-site chaining is the only route to scale |
| Parsed numbers |
|
Evidence 3
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | support.atlassian.com/confluence-cloud/docs/manage-your-stor | 'Confluence Free- 2 GB / Standard- 250 GB / Premium- Unlimited storage' |
| 2026-10-21 | support.atlassian.com/confluence-cloud/docs/configure-attach | 'The default is 100 megabytes' |
| 2026-10-21 | support.atlassian.com/confluence-cloud/docs/learn-about-conf | '2 GB of file storage' on Free, 10-user cap |
More fields 1
| dead end | {"failure_class": "quota","why": "2 GB per site on Free (250 GB Standard, unlimited Premium); 100 MB default per attachment, admin-configurable","retry_when": null,"first_recorded": "2026-10-21"} |
|---|
Unknown values 2
- per object cap notes: the field may be stated in a source that was not read
- retention notes: the field may be stated in a source that was not read
Jira Cloud Free
Storage- Free allowance
- 2 GB storage on Free, 250 GB Standard, unlimited Premium
- Verdict
- fails: quotathe free allowance is too small to matter
- Cost
- free tier
- Identity
- email?placeholder, not evidence; card unknown, phone unknown
- Binding limit
- noneno named constraint binds
- Evidence
- reported1 source; a third party said so
- Freshness
- stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05
| Free tier | 2 GB storage on Free, 250 GB Standard, unlimited Premium unit GB; metered on stored-bytes |
|---|---|
| Price | none stated |
| Identity | email (placeholder) not published |
| Egress | free attachment links, Atlassian CDN |
| Per-object cap | not stated |
| Retention | not stated |
| Interface | rest rest |
| Tooling | Jira Cloud REST API v3 issue attachments (multipart POST /rest/api/3/issue/{key}/attachments); jira-python wraps it |
| Composes with | 2 GB x unlimited free sites; same math as Confluence but with the same 2 GB ceiling and a smaller default file cap |
| Reliability | identical bucket economics to Confluence Free — only worth it if you are already farming Atlassian sites; issue-per-attachment bookkeeping is worse than Confluence pages |
| Parsed numbers |
|
Evidence 1
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | www.atlassian.com/software/jira/pricing | '2 GB of storage' (Free), '250 GB of storage' (Standard), 'Unlimited storage' (Premium) |
More fields 1
| dead end | {"failure_class": "quota","why": "2 GB storage on Free, 250 GB Standard, unlimited Premium","retry_when": null,"first_recorded": "2026-10-21"} |
|---|
Unknown values 4
- per object cap notes: the field may be stated in a source that was not read
- per object cap stated: the field may be stated in a source that was not read
- retention notes: the field may be stated in a source that was not read
- retention stated: the field may be stated in a source that was not read