@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
552Media
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: S3-compatible, $15/TB per month, free egress, built-in CDN, and up to 18x faster than Cloudflare R2.

filebase.com
6
2
14
879
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.

36
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
132
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
133
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.

71
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
132
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
108
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
Before parsing an IPFS bucket path, inspect it. Filebase RPC files/stat returns stat information without making a file-read request. Build the processing branch from the actual response, not from a filename guess. Route details: filebase.com/docs/ipfs/rpc-a…
Filebase graphic: INSPECT BEFORE PROCESSING. A path is an input. Its stat response is evidence. BUCKET PATH; files/stat; INSPECT RESPONSE; CHOOSE NEXT STEP. Handle missing paths separately from empty files.

ALT Filebase graphic: INSPECT BEFORE PROCESSING. A path is an input. Its stat response is evidence. BUCKET PATH; files/stat; INSPECT RESPONSE; CHOOSE NEXT STEP. Handle missing paths separately from empty files.

2
159
Keep the object key machine-friendly and the download name human-friendly. Content-Disposition can suggest a filename without renaming the stored key. Set it in your S3 upload metadata and check the browser's result. Filebase operations: filebase.com/docs/s3-api/sup…
Filebase graphic: KEY != DOWNLOAD NAME. Keep storage identity separate from presentation. reports/7f2a.pdf; STORED OBJECT KEY; quarterly-report.pdf; SUGGESTED DOWNLOAD NAME. Content-Disposition: attachment; filename="quarterly-report.pdf"

ALT Filebase graphic: KEY != DOWNLOAD NAME. Keep storage identity separate from presentation. reports/7f2a.pdf; STORED OBJECT KEY; quarterly-report.pdf; SUGGESTED DOWNLOAD NAME. Content-Disposition: attachment; filename="quarterly-report.pdf"

79
Infrastructure spend needs a product denominator. An illustrative $40 monthly workload supporting 2,000 active customers costs $0.02/customer. Keep activity definitions consistent and allocate shared costs explicitly. Check current Filebase pricing: filebase.com/pricing/?utm_so…
Filebase graphic: THE BILL PER CUSTOMER. Give infrastructure spend a product denominator. $40; ILLUSTRATIVE MONTHLY SPEND; 2,000; ACTIVE CUSTOMERS; $0.02; PER ACTIVE CUSTOMER. Illustrative arithmetic. Define the customer cohort consistently.

ALT Filebase graphic: THE BILL PER CUSTOMER. Give infrastructure spend a product denominator. $40; ILLUSTRATIVE MONTHLY SPEND; 2,000; ACTIVE CUSTOMERS; $0.02; PER ACTIVE CUSTOMER. Illustrative arithmetic. Define the customer cohort consistently.

1
87
Previewing a file header should not require a full-file read. Filebase RPC files/read accepts offset and count. Request a small byte window, then handle binary data as bytes rather than assuming text. Check the parameters: filebase.com/docs/ipfs/rpc-a…
Filebase graphic: READ THE HEADER WINDOW. A format preview does not need the full payload. FILE BYTES; 0; 64; HEADER PREVIEW; REMAINING PAYLOAD. Illustrative offset=0, count=64. Sample is not full validation.

ALT Filebase graphic: READ THE HEADER WINDOW. A format preview does not need the full payload. FILE BYTES; 0; 64; HEADER PREVIEW; REMAINING PAYLOAD. Illustrative offset=0, count=64. Sample is not full validation.

86
A .json filename is not your Content-Type configuration. Set application/json when uploading JSON to Filebase, then inspect the returned header. The object key names the asset; the media type tells clients how to interpret it. Details: filebase.com/docs/concepts/c…
Filebase graphic: A SUFFIX IS NOT A HEADER. Configure the media type when you upload. Key: data/report.json; ContentType: application/json; GET response; Content-Type: application/json. Object name and response metadata are separate.

ALT Filebase graphic: A SUFFIX IS NOT A HEADER. Configure the media type when you upload. Key: data/report.json; ContentType: application/json; GET response; Content-Type: application/json. Object name and response metadata are separate.

103
An hourly inventory job has its own request budget. At 30 listing pages per scan, 24 scans/day for 30 days means 21,600 list calls. That's an illustrative Class A workload before other operations. Check Filebase allowances: filebase.com/pricing/?utm_so…
Filebase graphic: PRICE THE SCAN CADENCE. An hourly job is a recurring request workload. 30; PAGES PER SCAN; 720; SCANS IN 30 DAYS; 21,600; LIST CALLS. Illustrative: 30 x 24 x 30. Excludes retries.

ALT Filebase graphic: PRICE THE SCAN CADENCE. An hourly job is a recurring request workload. 30; PAGES PER SCAN; 720; SCANS IN 30 DAYS; 21,600; LIST CALLS. Illustrative: 30 x 24 x 30. Excludes retries.

1
121
Bitswap can ask two different questions: HAVE asks whether a connected peer has a block; BLOCK asks for the block itself. Availability information and payload transfer are different messages, not different storage products. #IPFS
Filebase graphic: DO YOU HAVE IT?. Availability and payload transfer are different questions. HAVE; ASK ABOUT A BLOCK; BLOCK; ASK FOR THE PAYLOAD. Bitswap 1.2 protocol concept. Not a storage guarantee.

ALT Filebase graphic: DO YOU HAVE IT?. Availability and payload transfer are different questions. HAVE; ASK ABOUT A BLOCK; BLOCK; ASK FOR THE PAYLOAD. Bitswap 1.2 protocol concept. Not a storage guarantee.

2
151
One JSON document and NDJSON need different parsers. Filebase RPC pin/ls can stream results with stream=true. Buffer incomplete lines, parse complete records, and handle the final line at EOF. Check the route: filebase.com/docs/ipfs/rpc-a…
Filebase graphic: CHUNKS ARE NOT RECORDS. Parse the NDJSON boundary, not the network chunk. RESPONSE CHUNKS; BUFFER PARTIAL LINE; PARSE COMPLETE RECORD; HANDLE EOF. pin/ls with stream=true

ALT Filebase graphic: CHUNKS ARE NOT RECORDS. Parse the NDJSON boundary, not the network chunk. RESPONSE CHUNKS; BUFFER PARTIAL LINE; PARSE COMPLETE RECORD; HANDLE EOF. pin/ls with stream=true

1
120
Need an object's size or Content-Type, not its bytes? Use HeadObject before GetObject. Filebase supports HEAD metadata reads. A metadata check is still an operation, not a free download shortcut. See the supported calls: filebase.com/docs/s3-api/sup…
Filebase graphic: METADATA. NO FILE BODY.. Choose the response your application needs. HeadObject; METADATA ONLY; GetObject; METADATA + FILE BYTES. A HEAD call still counts as an operation.

ALT Filebase graphic: METADATA. NO FILE BODY.. Choose the response your application needs. HeadObject; METADATA ONLY; GetObject; METADATA + FILE BYTES. A HEAD call still counts as an operation.

2
122
A storage rate is not a delivery metric. Divide monthly workload spend by GB actually delivered: $30 / 1,000 GB = $0.03/GB in this illustrative example. Filebase object egress is free; the full workload still has costs. Start here: filebase.com/pricing/?utm_so…
Filebase graphic: WHAT DID DELIVERY COST?. A workload metric, not a storage unit rate. $30; ILLUSTRATIVE MONTHLY SPEND; 1,000 GB; DELIVERED TO USERS; $0.03 / GB; SPEND DIVIDED BY DELIVERY. Illustrative arithmetic. Not a Filebase quote.

ALT Filebase graphic: WHAT DID DELIVERY COST?. A workload metric, not a storage unit rate. $30; ILLUSTRATIVE MONTHLY SPEND; 1,000 GB; DELIVERED TO USERS; $0.03 / GB; SPEND DIVIDED BY DELIVERY. Illustrative arithmetic. Not a Filebase quote.

5
159
Replying to @araseb_
Pin It.
24
Load more