CloudPipe
cloudpipe.app · Debrid · 1 record · JSON
CloudPipe Debrid
fails: quotaemailno cardphoneDper-object-cap
| Free tier | 'Free $0/month ... 5 jobs / day ... 3GB max file size ... Standard download speed ... 6hr server storage (no storage cap) ... 1 download at a time'. Home page adds 'No credit card required for free plan'. unit requests; metered on request-count; The job counter is the only byte-bearing free counter that is also a daily one. The 450 GB in the ladder is 5 jobs x 3 GB x 30 days, which requires every job to be a distinct 3 GB file. |
|---|---|
| Price | USD 0 |
| Per-object cap | '3GB max file size' on the free plan, '10GB max file size' on Basic and 'Unlimited file size' on Pro. (3000000000 bytes) |
| Retention | '6hr server storage (no storage cap)' on free; 'We delete our copy immediately' once the file lands in the client's cloud drive |
| Egress | not metered by bytes at any tier; 'No Storage Limits - We use your cloud storage. Download as much as your storage can handle without extra fees.' free_allowance: 5 jobs/day, 3 GB each |
| Identity | email 'No credit card required for free plan'; the destination is a Google Drive account connected by OAuth after signup. A Google account is itself the identity gate, and Google may ask for a phone number at creation. |
| Limits |
The binding constraint on the 450 GB is not CloudPipe at all: it is whether a 15 GB free Google Drive can be emptied 30 times in a month without the OAuth app's read-only-write permission getting in the way. |
| Binding | per-object-cap 3 GB per file is 7.2x too small for a 20 GiB object, so the object fails before the daily count is reached. |
| Interface | rest, cli web dashboard that authorises against the client's Google Drive; no documented public API on the free plan |
| Tooling | browser dashboard plus a Drive OAuth grant; the Drive side is then reachable by rclone |
| Composes with | The largest step in the ladder and the only one that stages through a free Google Drive of 15 GB, so the 450 GB is a monthly flow rather than a monthly store. |
| Reliability | files are on CloudPipe's servers for 6 hours on free and then gone; one download at a time; the Drive permission is read-only for existing files, so the client must delete through Drive, not through CloudPipe. |
| Notes | Every number in the ladder's CloudPipe row is confirmed. Two caveats the arithmetic hides: '3GB max file' is a file cap that the ladder converts into a per-job cap, and the 450 GB needs the Drive emptied between jobs because free Drive holds 15 GB. If the cap is per file inside a multi-file torrent, 450 GB is an undercount; if it is per job, it stands. The page does not say which. The cheapest paid price, but the free 3 GB cap and the 6-hour server window mean it cannot host the 20 GiB case even on the paid plan unless the paid cap is larger, which the vendor does not state. |
| Evidence rung | documented Both the pricing and home pages were read today. No job was run, so the Drive churn is arithmetic, not measurement. |
| Checked | 2026-10-24 (live); stale on 2026-11-23 |
| Parsed numbers |
|
Evidence (4)
| date | source | what it proved |
|---|---|---|
| 2026-10-23 | cloudpipe.app/pricing | 'Free $0/month', '5 jobs / day', '3GB max file size', '6hr server storage (no storage cap)', '1 download at a time' |
| 2026-10-23 | cloudpipe.app/ | 'No credit card required for free plan', 'No Storage Limits - We use your cloud storage', 'We delete our copy immediately', and the FAQ sentence 'You connect your Drive after signing up' |
| 2026-10-23 | cloudpipe.app/ | 'Free $0 - 5 jobs/day, 3GB max file, 6hr server storage, 1 download at a time, No credit card required'; paid '$2.99 /mo'; 'We delete our copy immediately' |
| 2026-10-23 | cloudpipe.app/features/torrent-to-mega | a torrent-to-cloud destination page exists, so the target cloud is interchangeable |
More fields (4)
{
"job_to_file_assumption": "unstated by the vendor",
"ladder_gb_month": 450,
"drive_free_gb": 15,
"destination": "user's own cloud drive"
}