Filebase
filebase.com · 3 records in Storage · JSON
Records 3
- fails: quotaFilebase (IPFS tier)
Storagefree tieridentity emailno cardlimit volume-quotaevidence reportedstale on 2026-11-05
- deadinfura ipfs
Storageidentity email?card?evidence reportedchecked 2026-10-21
- deadsia / skynet
Storageidentity email?card?evidence reportedchecked 2026-10-21
Filebase (IPFS tier)
Storage- Free allowance
- Free: 5 GB of pooled Object Storage and IPFS storage, 500 pinned files, 10 GB a month of IPFS egress and free object egress; Pro $7.50 a month raises storage to 500 GB
- Verdict
- fails: quotathe free allowance is too small to matter
- Cost
- free tier
- Identity
- emailno card, no phone
- Binding limit
- volume-quota5 GB of pooled storage on the Free plan
- Evidence
- reported25 sources; a third party said so
- Freshness
- stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05
| Free tier | Free: 5 GB of pooled Object Storage and IPFS storage, 500 pinned files, 10 GB a month of IPFS egress and free object egress; Pro $7.50 a month raises storage to 500 GB unit GB; metered on stored-bytes; the pricing page was read on 2026-11-01; the binding constraint is the 5 GB volume, which limits[] carries |
|---|---|
| Price | none stated |
| Limits |
Single PUT 5 GB; multipart total 5 TB (1 TB recommended); 500 req/s S3 API; 1 bucket on Free; 500 pinned files. |
| Binding | volume-quota the free plan's 5 GB of pooled storage is a volume quota and is the constraint that fails first; object egress is free |
| Identity | email the sign-up form asks for a first name, a last name, an email address and a password, with a Google sign-up option; no card, phone or ID field appears on the form |
| Egress | Split, and the split is the trap. 'For S3-compatible object storage buckets on the non-IPFS tier at s3.filebase.io, egress is free on every paid plan.' But 'IPFS bandwidth is not free... On the free tier, there is a 5 GB / month egress cap' — and the pricing page states 10 GB IPFS Egress. Either way it is single-digit-to-10 GB/month. free allowance: 10 GB per month of IPFS egress on Free |
| Per-object cap | the pricing page states no per-object cap; the limits it does state are a bucket count and a pinned-file count |
| Retention | Pinned content stays on the Filebase node indefinitely and files uploaded to an IPFS bucket stay pinned for as long as they are kept in the bucket; the pricing page states no period, its footnote calling pinned files objects maintained for persistence on the IPFS network |
| Interface | s3-compatible, rclone, cli part of the text of Limits, above |
| Tooling | S3 API at s3.filebase.io, region 'auto', SigV4; rclone s3 backend works; IPFS Pinning Service API; dedicated gateways; docs list rclone/boto3/aws-cli explicitly. |
| Composes with | 1 bucket on Free, no limit on object count within it. 5 GB per account is not repeatable to 500 GB in any practical way, and each account needs its own S3 keys. |
| Reliability | S3 API held up live: the public gateway served the test CID at 200 (414,201 bytes, Server: Filebase) but throttled during a rapid burst (2 of 8 answered before the burst ran long). The 'no egress fees' headline applies to the S3 tier, not the IPFS tier — a genuinely confusing pricing page and the single most common misread in this niche. |
| Notes | Free: 5 GB pooled storage across Object Storage and IPFS, 500 pinned files, 10 GB/month IPFS bandwidth, object egress free. Pro $7.50/mo: 500 GB pooled. |
| Evidence note | reported the pricing page, the bandwidth docs and the sign-up form were read on 2026-11-01; the identity, interface, retention and per-object fields were re-read, the live probe of the gateway was not repeated |
| Parsed numbers |
|
Evidence 25
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | filebase.com/pricing/ | Free: 'Storage 5 GB', 'Shared across Object Storage and IPFS', 'Pinned Files 500', 'IPFS Egress 10 GB', 'Object Egress Free' |
| 2026-10-21 | filebase.com/docs/concepts/bandwidth | 'IPFS bandwidth is not free. IPFS buckets, gateways, Bitswap, trustless gateway responses, RPC responses, and Filebase Sites have separate IPFS bandwidth accounting.' |
| 2026-10-21 | ipfs.filebase.io/ipfs/bafybei...5u4 | probe: GET -> 200, 414201 bytes, Server: Filebase |
| 2026-11-01 | filebase.com/pricing/ | object egress is free on both plans, so the read path is not the constraint |
| 2026-11-01 | filebase.com/pricing/ | the Free plan stores 5 GB against 500 GB on Pro |
| 2026-11-01 | filebase.com/pricing/ | 500 GB is what the paid plan stores, so it is the retry threshold for a quota failure |
| 2026-11-01 | filebase.com/pricing/ | Free holds 5 GB of pooled storage and Pro 500 GB |
| 2026-11-01 | filebase.com/pricing/ | IPFS bandwidth beyond the allowance is priced at $0.015/GB |
| 2026-11-01 | filebase.com/pricing/ | the Free plan includes 10 GB of IPFS egress |
| 2026-11-01 | console.filebase.com/signup | the sign-up form carries an email field and no card, phone or ID field |
| 2026-11-01 | console.filebase.com/signup | a Google sign-up option sits beside the email form |
| 2026-11-01 | filebase.com/pricing/ | the Free plan's storage is a volume allowance of 5 GB |
| 2026-11-01 | filebase.com/pricing/ | 5 GB of free storage is the volume that binds |
| 2026-11-01 | filebase.com/pricing/ | 5 GB is the Free plan's pooled storage allowance |
| 2026-11-01 | filebase.com/pricing/ | the Free and Pro storage allowances are unchanged at 5 GB and 500 GB |
| 2026-11-01 | filebase.com/pricing/ | the pricing page states the Free and Pro storage allowances |
| 2026-11-01 | filebase.com/pricing/ | the Free plan states a bucket count of 1 and no per-object size cap |
| 2026-11-01 | filebase.com/pricing/ | pinning is described as persistence with no retention period |
| 2026-11-01 | filebase.com/docs/concepts/bandwidth | the bandwidth docs were read and state that IPFS bandwidth is metered |
| 2026-11-01 | filebase.com/pricing/ | pinning is described as persistence with no retention period stated |
| 2026-11-02 | filebase.com/docs/ipfs/concepts/what-is-ipfs-pinning | the docs state an indefinite retention period for pinned content, so 'no period stated' contradicts the docs |
| 2026-11-02 | filebase.com/docs/ipfs/concepts/what-is-ipfs-pinning | retention lasts while the object stays in the bucket, so deletion is what ends it |
| 2026-11-02 | filebase.com/docs/ipfs/pinning/deleting-files | deletion is the event that ends retention, and Filebase then no longer guarantees availability |
| 2026-11-02 | filebase.com/pricing/ | the pricing page footnote describes pinning as persistence and states no period, and the row is the pricing page's own text, not the docs' |
| 2026-11-02 | filebase.com/docs/ipfs/concepts/what-is-ipfs-pinning | not published |
More fields 1
| dead end | {"failure_class": "quota","why": "The free plan holds 5 GB of pooled storage against the 500 GB per unit this topic requires; object egress is free on both plans, so the byte allowance binds and the read path does not","retry_when": "if the free allowance rises to 500 GB of pooled storage on the $0 plan","first_recorded": "2026-10-21"} |
|---|
Unknown values 1
- per object cap notes: the field may be stated in a source that was not read
infura ipfs
Storage- Free allowance
- Discontinued. New uploads and pinning stopped 2026-08-03; the IPFS API and dedicated gateway ended 2026-08-15, after which unmigrated content is no longer available.
- Verdict
- deadthe offer or the service no longer exists
- Cost
- no price stated
- Identity
- email?placeholder, not evidence; card unknown, phone unknown
- Binding limit
- noneno named constraint binds
- Evidence
- reported1 source; a third party said so
- Freshness
- checked 2026-10-21checked 2026-10-21 (inherited)
| Free tier | Discontinued. New uploads and pinning stopped 2026-08-03; the IPFS API and dedicated gateway ended 2026-08-15, after which unmigrated content is no longer available. Infura's own docs URL… unit none; metered on none |
|---|---|
| Price | none stated |
| Identity | email (placeholder) not published |
| Egress | not recorded |
| Interface | unknown |
| Tooling | not recorded |
| Parsed numbers |
|
Evidence 1
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | filebase.com/blog/infura-ipfs-is-shutting-down-how-to-migrat | the text of Free tier, above |
More fields 1
| dead end | {"failure_class": "dead-service","why": "Discontinued. New uploads and pinning stopped 2026-08-03; the IPFS API and dedicated gateway ended 2026-08-15, after which unmigrated content is no longer available. Infura's own docs URL…","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
sia / skynet
Storage- Free allowance
- Skynet Labs shut down its websites and services in 2023 and Filebase ran a migration for Skynet customers; siasky.net free portal storage is gone.
- Verdict
- deadthe offer or the service no longer exists
- Cost
- no price stated
- Identity
- email?placeholder, not evidence; card unknown, phone unknown
- Binding limit
- noneno named constraint binds
- Evidence
- reported3 sources; a third party said so
- Freshness
- checked 2026-10-21checked 2026-10-21 (inherited)
| Free tier | Skynet Labs shut down its websites and services in 2023 and Filebase ran a migration for Skynet customers; siasky.net free portal storage is gone. Sia itself survives as a protocol where… unit none; metered on none |
|---|---|
| Price | none stated |
| Identity | email (placeholder) not published |
| Egress | not recorded |
| Interface | unknown |
| Tooling | not recorded |
| Parsed numbers |
|
Evidence 3
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | filebase.com/blog/announcing-automatic-bucket-migration-for- | the text of Free tier, above |
| 2026-10-21 | www.coindesk.com/business/2022/08/12/blockchain-firm-skynet- | cited as the basis of the rejection: Skynet Labs shut down its websites and services in 2023 and Filebase ran a migration for Skynet customers; siasky.net free portal storage is gone. Sia itself survives as a protocol where you |
| 2026-10-21 | docs.sia.tech/ | cited as the basis of the rejection: Skynet Labs shut down its websites and services in 2023 and Filebase ran a migration for Skynet customers; siasky.net free portal storage is gone. Sia itself survives as a protocol where you |
More fields 1
| dead end | {"failure_class": "dead-service","why": "Skynet Labs shut down its websites and services in 2023 and Filebase ran a migration for Skynet customers; siasky.net free portal storage is gone. Sia itself survives as a protocol where…","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