Managing dedicated gateways
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.
Third-party CDN policy
Filebase's IPFS gateway service includes its own CDN. Proxying Filebase IPFS gateway traffic through another CDN, including Cloudflare's proxy/CDN, Amazon CloudFront, Fastly, or Bunny CDN, is not permitted. Access your gateway directly or configure a custom domain that points directly to Filebase.
Plan limits
| Plan | Dedicated gateways |
|---|---|
| Free | 1 |
| Starter | 1 |
| Pro | 5 |
| Unlimited | 10 |
Create a gateway
Via the console
- Gateways → Create New Gateway in the console.
- Pick a name (3–63 characters, lowercase letters/numbers/dashes, globally unique).
- Choose Public (serves any IPFS CID) or Private (serves only CIDs pinned to your account).
- 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
Troubleshooting CDN proxy errors
If a gateway returns 403 Forbidden with the message CDN proxying is not allowed, remove the third-party CDN from the request path. Point your custom domain directly to the Filebase CNAME target shown in the console. If you use Cloudflare DNS, set the gateway record to DNS only, with proxying disabled, then retry after DNS propagation.
Other 403 responses can have different causes, including bandwidth limits or access restrictions. Check the response message before changing your DNS configuration.