Skip to main content

Managing dedicated gateways

Legacy: This page documents Filebase's IPFS tier. For new deployments, use the S3-compatible object storage tier with the s3.filebase.io endpoint.

A dedicated IPFS gateway is a private gateway you provision under your account. Compared to the public gateway at ipfs.filebase.io, dedicated gateways offer:

  • No rate limit.
  • Higher performance (direct peering with Filebase's IPFS nodes).
  • Configurable access controls.
  • Custom domain support.

Plan limits​

PlanDedicated gateways
Free1
Starter1
Pro5
Unlimited10

Create a gateway​

Via the console​

  1. Gateways → Create New Gateway in the console.
  2. Pick a name (3–63 characters, lowercase letters/numbers/dashes, globally unique).
  3. Choose Public (serves any IPFS CID) or Private (serves only CIDs pinned to your account).
  4. Click Create.

Your gateway is now reachable at https://<gateway-name>.myfilebase.com/ipfs/{CID}.

Via the Platform API​

curl -X POST \
  -H "Authorization: Bearer $(echo -n "$KEY:$SECRET" | base64)" \
  -H "Content-Type: application/json" \
  -d '{ "name": "my-gateway", "private": false, "enabled": true }' \
  https://api.filebase.io/v1/gateways

List gateways​

curl -H "Authorization: Bearer $(echo -n "$KEY:$SECRET" | base64)" \
  https://api.filebase.io/v1/gateways

Enable / disable​

A gateway can be temporarily disabled — kept under the same name, but returning errors to requests:

curl -X PUT \
  -H "Authorization: Bearer $(echo -n "$KEY:$SECRET" | base64)" \
  -H "Content-Type: application/json" \
  -d '{ "enabled": false }' \
  https://api.filebase.io/v1/gateways/my-gateway

Delete​

curl -X DELETE \
  -H "Authorization: Bearer $(echo -n "$KEY:$SECRET" | base64)" \
  https://api.filebase.io/v1/gateways/my-gateway

What's next​