Filebase (@Filebase) header
Filebase (@Filebase) profile picture

Filebase

@Filebase

Fast S3-Compatible Object Storage with Free Egress ⚡ Reliable, scalable storage for developers and businesses. 5 GB free ↓

 Boston, MA
filebase.com
Joined May 2019
  • Tweets4.5K
  • Following142
  • Followers4.3K
563Media
Photo by Filebase (@Filebase)Photo by Filebase (@Filebase)Photo by Filebase (@Filebase)Photo by Filebase (@Filebase)Photo by Filebase (@Filebase)Photo by Filebase (@Filebase)Photo by Filebase (@Filebase)Photo by Filebase (@Filebase)Photo by Filebase (@Filebase)Photo by Filebase (@Filebase)
Today we’re launching Filebase Object Storage. High-performance S3-compatible storage with: • zero egress fees • fast uploads/downloads • predictable pricing • deterministic object verification Built for modern file-heavy workloads. filebase.com/blog/introducin…
Introducing Filebase Object Storage with Free Egress

Introducing Filebase Object Storage with Free Egress

Introducing Filebase Object Storage: S3-compatible, $15/TB per month, free egress, built-in CDN, and up to 18x faster than Cloudflare R2.

filebase.com
6
2
14
914
A wallet signature can support an application's identity check. It is not a Filebase S3 access key or RPC Bearer token. Let the backend authorize storage actions separately, and keep storage credentials out of client-side code. #Web3
Filebase graphic: IDENTITY != STORAGE AUTHORIZATION. Wallet verification and storage credentials serve different roles. WALLET IDENTITY CHECK; APP AUTHORIZATION POLICY; BACKEND STORAGE REQUEST; FILEBASE. Wallet signatures are not S3 keys or RPC Bearer tokens.

ALT Filebase graphic: IDENTITY != STORAGE AUTHORIZATION. Wallet verification and storage credentials serve different roles. WALLET IDENTITY CHECK; APP AUTHORIZATION POLICY; BACKEND STORAGE REQUEST; FILEBASE. Wallet signatures are not S3 keys or RPC Bearer tokens.

94
Filebase RPC files/rm does not support recursive=true or force=true; those flags return 400. Build a reviewed list of explicit paths instead of assuming Kubo's full deletion behavior is available. Check the supported route: filebase.com/docs/ipfs/rpc-a…
Filebase graphic: EXPLICIT PATHS. EXPLICIT DELETIONS.. Do not assume recursive removal is available. POST /api/v0/files/rm; arg=/approved-path.txt; recursive=true -> 400; force=true -> 400. Review the path list. Stop on unsupported behavior.

ALT Filebase graphic: EXPLICIT PATHS. EXPLICIT DELETIONS.. Do not assume recursive removal is available. POST /api/v0/files/rm; arg=/approved-path.txt; recursive=true -> 400; force=true -> 400. Review the path list. Stop on unsupported behavior.

99
A 503 SlowDown is not a signal to retry faster. Filebase recommends the AWS SDK's exponential backoff with jitter. Keep retries bounded and worker concurrency controlled; synchronized immediate retries can prolong a burst. Rate-limit guidance: filebase.com/docs/s3-api/rat…
Filebase graphic: SLOWDOWN MEANS BACK OFF. Use bounded retries, jitter, and controlled concurrency. REQUEST; 503 SlowDown; BACKOFF + JITTER; BOUNDED RETRY. Prefer the SDK retryer over synchronized immediate retries.

ALT Filebase graphic: SLOWDOWN MEANS BACK OFF. Use bounded retries, jitter, and controlled concurrency. REQUEST; 503 SlowDown; BACKOFF + JITTER; BOUNDED RETRY. Prefer the SDK retryer over synchronized immediate retries.

1
101
One IPFS bandwidth total can contain several delivery paths. Filebase separates S3, Gateway, Public GW, Bitswap, Trustless, RPC and Sites usage. Sum the categories once; don't add the account total again. Inspect the breakdown: filebase.com/docs/ipfs/bandw…
Filebase graphic: SUM THE CATEGORIES ONCE. The account total is not an extra delivery path. 60 GB; ILLUSTRATIVE CATEGORY A; 30 + 10 GB; OTHER TWO CATEGORIES; 100 GB; TOTAL, NOT AN EXTRA LINE. Illustrative three-category subtotal. Include all applicable categories.

ALT Filebase graphic: SUM THE CATEGORIES ONCE. The account total is not an extra delivery path. 60 GB; ILLUSTRATIVE CATEGORY A; 30 + 10 GB; OTHER TWO CATEGORIES; 100 GB; TOTAL, NOT AN EXTRA LINE. Illustrative three-category subtotal. Include all applicable categories.

1
99
A CID helps identify content. It does not tell you who endorsed that content. For a signed manifest stored on IPFS, verify both the referenced content and the signature against an identity your application trusts. Hash matching is not authorship. #Web3
Filebase graphic: MATCHED BYTES != TRUSTED AUTHOR. Content verification and signature verification answer different questions. CONTENT CHECK; EXPECTED DATA REFERENCE; SIGNATURE CHECK; EXPECTED SIGNING IDENTITY. The application must define which identity it trusts.

ALT Filebase graphic: MATCHED BYTES != TRUSTED AUTHOR. Content verification and signature verification answer different questions. CONTENT CHECK; EXPECTED DATA REFERENCE; SIGNATURE CHECK; EXPECTED SIGNING IDENTITY. The application must define which identity it trusts.

1
99
An IPNS key alias and its cryptographic identity are different things. Filebase RPC key/rename renames an existing key; it is not a key-generation step. Compare key IDs before and after a rename in a test workflow. RPC reference: filebase.com/docs/ipfs/rpc-a…
Filebase graphic: RENAME IS NOT ROTATION. A key alias is not its cryptographic identity. ALIAS: old-key; BEFORE RENAME; ALIAS: new-key; AFTER RENAME. Compare the key identifiers; do not infer identity from the alias.

ALT Filebase graphic: RENAME IS NOT ROTATION. A key alias is not its cryptographic identity. ALIAS: old-key; BEFORE RENAME; ALIAS: new-key; AFTER RENAME. Compare the key identifiers; do not infer identity from the alias.

1
127
HTTP success is not proof every requested object was deleted. With S3 DeleteObjects, inspect the per-key results and error entries. Filebase supports batches of up to 1,000 keys. Review the candidate list first; then reconcile the response: filebase.com/docs/s3-api/com…
Filebase graphic: 200 IS NOT THE WHOLE RESULT. Read the per-key outcome before declaring success. KEY; RESULT; old-a.json; DELETED; old-b.json; ERROR: INSPECT; old-c.json; DELETED. Illustrative response. Review deletion candidates before sending.

ALT Filebase graphic: 200 IS NOT THE WHOLE RESULT. Read the per-key outcome before declaring success. KEY; RESULT; old-a.json; DELETED; old-b.json; ERROR: INSPECT; old-c.json; DELETED. Illustrative response. Review deletion candidates before sending.

109
A cache hit is not automatically free bandwidth. Reuse in a browser can avoid a gateway fetch; bytes served by a Filebase dedicated IPFS gateway count toward Gateway bandwidth. Measure where the response was served. Billing categories: filebase.com/docs/ipfs/bandw…
Filebase graphic: WHICH CACHE SERVED THE BYTES?. The response path matters more than a hit-rate headline. BROWSER REUSE; NO NEW GATEWAY FETCH; GATEWAY RESPONSE; OUTBOUND BYTES COUNT. Dedicated IPFS gateway response size contributes to Gateway bandwidth.

ALT Filebase graphic: WHICH CACHE SERVED THE BYTES?. The response path matters more than a hit-rate headline. BROWSER REUSE; NO NEW GATEWAY FETCH; GATEWAY RESPONSE; OUTBOUND BYTES COUNT. Dedicated IPFS gateway response size contributes to Gateway bandwidth.

73
A peer being online does not guarantee a direct connection. libp2p can use relays and attempt direct connection upgrades across NATs. A relay forwards a connection; it is not a promise to persist your IPFS content. #libp2p
Filebase graphic: REACHABLE != RETAINED. A relay carries a connection. Storage retains content. PEER A; RELAY PATH; PEER B; DIRECT PATH WHEN POSSIBLE. Network reachability is separate from data persistence.

ALT Filebase graphic: REACHABLE != RETAINED. A relay carries a connection. Storage retains content. PEER A; RELAY PATH; PEER B; DIRECT PATH WHEN POSSIBLE. Network reachability is separate from data persistence.

1
79
Renaming a bucket file is a path operation. Filebase RPC files/mv takes the source and destination as two arg values. Test argument ordering and destination behavior in a disposable fixture before adapting a script. RPC reference: filebase.com/docs/ipfs/rpc-a…
Filebase graphic: TWO PATHS. ONE MOVE.. Repeated arg parameters have distinct roles. POST /api/v0/files/mv; arg=/old.txt; arg=/new.txt; FIRST = SOURCE | SECOND = DESTINATION. Use a query builder that preserves repeated parameter names.

ALT Filebase graphic: TWO PATHS. ONE MOVE.. Repeated arg parameters have distinct roles. POST /api/v0/files/mv; arg=/old.txt; arg=/new.txt; FIRST = SOURCE | SECOND = DESTINATION. Use a query builder that preserves repeated parameter names.

79
A key containing spaces, + or # is not ready to paste into a URL. Give the SDK the actual key and let it build the request. Don't double-encode a pre-signed URL after signing. Key naming and URL encoding are different steps. Filebase S3: filebase.com/docs/s3-api/sup…
Filebase graphic: KEY != ENCODED URL. Let one layer own request construction. Stored key: reports/Q1 + Q2.pdf; SDK input: actual object key; Request URL: encoded by SDK; Pre-signed URL: preserve as returned. Avoid double encoding or edits after signing.

ALT Filebase graphic: KEY != ENCODED URL. Let one layer own request construction. Stored key: reports/Q1 + Q2.pdf; SDK input: actual object key; Request URL: encoded by SDK; Pre-signed URL: preserve as returned. Avoid double encoding or edits after signing.

1
131
Three identical exports under three keys can be avoidable application work. Check content before creating another object and map consumers to the retained export. Don't assume Filebase provides an automatic deduplication discount. Current pricing: filebase.com/pricing/?utm_so…
Filebase graphic: ONE EXPORT. MANY REFERENCES.. Avoid redundant payloads in the application workflow. IDENTICAL EXPORT INPUT; ONE RETAINED OBJECT; CONSUMER A; CONSUMER B. Application-level reuse. No automatic deduplication discount assumed.

ALT Filebase graphic: ONE EXPORT. MANY REFERENCES.. Avoid redundant payloads in the application workflow. IDENTICAL EXPORT INPUT; ONE RETAINED OBJECT; CONSUMER A; CONSUMER B. Application-level reuse. No automatic deduplication discount assumed.

1
81
For browser apps, gateway URL shape is an isolation decision. Path-style URLs can share an origin; CID subdomains give content separate origins on a correctly configured gateway. An IPFS content address alone does not set browser boundaries. #IPFS
Filebase graphic: URL SHAPE SETS THE ORIGIN. Content addressing and browser isolation are different layers. gateway/ipfs/CID; SHARED HOST ORIGIN; CID.ipfs.gateway; CID-SPECIFIC ORIGIN. Requires a correctly configured subdomain gateway.

ALT Filebase graphic: URL SHAPE SETS THE ORIGIN. Content addressing and browser isolation are different layers. gateway/ipfs/CID; SHARED HOST ORIGIN; CID.ipfs.gateway; CID-SPECIFIC ORIGIN. Requires a correctly configured subdomain gateway.

3
143
Need a filename beneath an IPFS root? Filebase RPC add supports wrap-with-directory=true. The returned CID identifies the wrapper directory, so retrieval uses that CID plus the file path, not the directory as file bytes. Route details: filebase.com/docs/ipfs/rpc-a…
Filebase graphic: THE WRAPPER IS THE ROOT. A wrapped upload needs its file path at retrieval. invoice.pdf; add + directory wrapping; DIRECTORY CID; /invoice.pdf. Not a Bucket CID or an incremental release workflow.

ALT Filebase graphic: THE WRAPPER IS THE ROOT. A wrapped upload needs its file path at retrieval. invoice.pdf; add + directory wrapping; DIRECTORY CID; /invoice.pdf. Not a Bucket CID or an incremental release workflow.

1
146
A failed download need not restart at byte zero. Filebase supports Range GETs. Resume from the saved byte offset, check Content-Range, and confirm the object hasn't changed before appending. Supported operations: filebase.com/docs/s3-api/com…
Filebase graphic: RESUME THE DOWNLOAD. Append only when the object and range still match. SAVED BYTES; 0; OFFSET; REQUEST REMAINING RANGE; VERIFY BEFORE APPENDING. A changed object requires a different recovery path.

ALT Filebase graphic: RESUME THE DOWNLOAD. Append only when the object and range still match. SAVED BYTES; 0; OFFSET; REQUEST REMAINING RANGE; VERIFY BEFORE APPENDING. A changed object requires a different recovery path.

72
An illustrative 4 GB text export compressed to 1 GB uses 3 GB fewer stored bytes. Filebase does not automatically transcode gzip/Brotli delivery; set Content-Encoding when serving compressed content. Check the header guidance: filebase.com/docs/concepts/c…
Filebase graphic: STORE THE SMALLER REPRESENTATION. Measure compression. Configure delivery headers. 4 GB; ILLUSTRATIVE ORIGINAL; 1 GB; COMPRESSED PAYLOAD; 75%; FEWER STORED BYTES. Illustrative 4:1 compression. Not a benchmark or bill-savings claim.

ALT Filebase graphic: STORE THE SMALLER REPRESENTATION. Measure compression. Configure delivery headers. 4 GB; ILLUSTRATIVE ORIGINAL; 1 GB; COMPRESSED PAYLOAD; 75%; FEWER STORED BYTES. Illustrative 4:1 compression. Not a benchmark or bill-savings claim.

2
134
Raw block bytes are not necessarily file bytes. Filebase RPC block/get retrieves a block; cat returns a file's contents. For a UnixFS file with a structured root, pick the route that matches the bytes your parser expects. RPC reference: filebase.com/docs/ipfs/rpc-a…
Filebase graphic: BLOCK BYTES != FILE BYTES. Pick the representation your parser expects. block/get; RAW BLOCK REPRESENTATION; cat; FILE CONTENT. Structured UnixFS roots require reconstruction; raw blocks can coincide.

ALT Filebase graphic: BLOCK BYTES != FILE BYTES. Pick the representation your parser expects. block/get; RAW BLOCK REPRESENTATION; cat; FILE CONTENT. Structured UnixFS roots require reconstruction; raw blocks can coincide.

92
Hashed JS and changing HTML need different cache policies. Filebase respects Cache-Control: use long-lived immutable caching for content-hashed assets and a shorter policy for changing entry pages. Configure each upload deliberately: filebase.com/docs/concepts/c…
Filebase graphic: TWO ASSETS. TWO CACHE POLICIES.. Match freshness requirements to the object. app.a3f9.js; LONG LIFETIME + IMMUTABLE; index.html; SHORTER FRESHNESS WINDOW. Content-hashed filenames and changing entry pages have different contracts.

ALT Filebase graphic: TWO ASSETS. TWO CACHE POLICIES.. Match freshness requirements to the object. app.a3f9.js; LONG LIFETIME + IMMUTABLE; index.html; SHORTER FRESHNESS WINDOW. Content-hashed filenames and changing entry pages have different contracts.

1
109
Old builds can outlive their usefulness. Keep needed rollback versions, inventory the rest, and approve cleanup before deletion. Filebase does not support S3 lifecycle write configuration; use an explicit retention job. Check compatibility: filebase.com/docs/s3-api/com…
Filebase graphic: BUILDS NEED A RETENTION POLICY. Keep rollback capacity. Review obsolete outputs. CURRENT BUILD; KEEP; ROLLBACK BUILDS; KEEP; OBSOLETE BUILDS; REVIEW FIRST. No S3 lifecycle write configuration. Cleanup requires a separate workflow.

ALT Filebase graphic: BUILDS NEED A RETENTION POLICY. Keep rollback capacity. Review obsolete outputs. CURRENT BUILD; KEEP; ROLLBACK BUILDS; KEEP; OBSOLETE BUILDS; REVIEW FIRST. No S3 lifecycle write configuration. Cleanup requires a separate workflow.

91
One peer connection can carry multiple protocol streams. libp2p stream multiplexing separates those conversations without requiring a new connection for every exchange. Stream count and connection count are different operational metrics. #libp2p
Filebase graphic: ONE CONNECTION. MANY STREAMS.. Count the transport and the conversations separately. PEER CONNECTION; PROTOCOL STREAM A; PROTOCOL STREAM B; PROTOCOL STREAM C. Some transports multiplex streams natively.

ALT Filebase graphic: ONE CONNECTION. MANY STREAMS.. Count the transport and the conversations separately. PEER CONNECTION; PROTOCOL STREAM A; PROTOCOL STREAM B; PROTOCOL STREAM C. Some transports multiplex streams natively.

104
Load more