IPFS.NINJA is the IPFS pinning service for developers who want a clean REST API, dedicated gateways, and signed upload tokens — without the complexity of running a node themselves.
IPFS.NINJA pins files to the InterPlanetary File System (IPFS) and serves them through dedicated gateways. The API is intentionally minimal: one POST endpoint to upload, one DELETE endpoint to unpin, one GET endpoint to list. No SDK is required — you can hit it with curl, Python's requests, fetch, or whatever HTTP client you already use.
We also generate signed upload tokens for safe client-side uploads from browsers and mobile apps, give every paid account a dedicated gateway with predictable performance, and surface per-CID analytics so you can see what's actually being fetched.
IPFS itself is brilliant but operationally painful. Running a node means managing storage, peering, garbage collection, gateway TLS, and a thicket of CLI tools. Most teams just want a CID back in <500ms after they upload bytes. IPFS.NINJA exists to be that — the boring, predictable, mid-priced pinning service that does one thing well.
Our pricing reflects this: $5/month for the Bodhi tier (10 GB, 200 files, dedicated gateway) was deliberately set as the lowest paid entry point in the market — most competitors start at $20/month for comparable storage.
IPFS.NINJA is built and operated by the team at Blockchain Web Services (BWS), with Nacho Coll as principal. The team has been working on infrastructure for blockchain and decentralized-storage products since 2019, and launched IPFS.NINJA in April 2024 — because every pinning service we evaluated for prior client projects charged a 4× markup for what was, fundamentally, the same underlying setup.
The blog you're reading is part technical documentation, part operator's notebook. Some articles are drafted by an AI assistant (using the content-generation workflow described below) and reviewed by the team before publication; others are written end-to-end by hand. Every code example is verified against the live API before it ships.
Some blog posts on this site are drafted by Claude (Anthropic's AI assistant) using a prompt that ranks topics by underserved-search-intent, drafts the article body with required code-first structure, and emits FAQPage JSON-LD. The BWS team then reviews the draft, verifies every code example against the live API, fixes any factual errors, and approves publication. Articles that pass this review carry the byline "Nacho Coll" and include a disclosure paragraph (this article? no — this one is written by hand).
This is disclosed per Google's helpful-content guidance , which asks that "appropriate use of automation/AI-generation is self-evident to visitors through disclosures". We agree.
We don't accept paid placements, sponsored posts, or affiliate links. Comparison articles (e.g., "IPFS.NINJA vs Pinata") are written with explicit prices and feature counts from the competitor's public documentation, and we link to their site so readers can verify the facts themselves. If you spot an inaccuracy in any post, please open an issue at our GitHub or email hello@ipfs.ninja — we'll correct it and add an editorial note.
Page last updated 2026-06-23.