# Pomf.lain.la

> lain.la | Debrid; 1 record: free tier, limits, identity cost and evidence.

HTML https://fshy.ajam.dev/p/lain/ | JSON https://fshy.ajam.dev/api/v1/entity/lain.json | how to read a record: https://fshy.ajam.dev/llms-full.txt

## Pomf.lain.la

- `debrid/pomf-lain-la` | qualifies-with-caveat | evidence measured | binding per-object-cap | category anonymous pomf clone (1 GiB per file) | tier free
- needs card no, phone no, ID no, institution no | verified 2026-10-23T02:30:47.000Z (live) | stale on 2026-11-23
- url https://pomf.lain.la/
- price USD 0
- free tier: Max upload size is 1 GiB, wow! | unit: GiB | metered on: none | read on: 2026-10-23 | source: [1] | note: No account, no email, no cap on the number of files stated.
- per-object cap: Max upload size is 1 GiB | bytes: 1073741824 | source: [1] | note: 1 GiB is the largest anonymous per-file cap met that is both stated and on a host that answers.
- retention: unverified: the homepage publishes no expiry and the FAQ was not readable as text (served gzip without a decoded body to the reader) | source: [1] | note: The Terms & Privacy page is the place to settle it; it was not read.
- egress: Downloads are served from pomf2.lain.la; no byte allowance and no download counter are published. | metered: no | free allowance: none published | source: [1]
- identity: anonymous | detail: Multipart POST with no account, no email and no cookie; a link came back.
- interface: rest, cli
- limits:
  - per-object-cap (binding): 1 GiB per file [1]
- binding note: At 1 TiB a month this is 1 024 objects of 1 GiB; the cap is what forces splitting, and no rate or byte counter was observed to bind first.
- interface detail: POST https://pomf.lain.la/upload.php multipart field 'files[]'. JSON reply with success, files[0].url, .hash (SHA-1), .size. The stored object is served from the pomf2 host.
- endpoint: part of interface detail
- tooling: curl -F 'files[]=@file' https://pomf.lain.la/upload.php; an optional 'speedkey' field exists for a queue priority the site calls Speedkeys
- composes with: 1 GiB per object with no account is the right shape for a single large media file or a dataset shard: two files cover a 2 GiB upload that most relays refuse, and the JSON reply carries SHA-1 so the store can be verified without a second download.
- reliability: Uploads were switched off during a PHP CVE and switched back on, per a comment left in the homepage HTML; treat availability as hobby-grade.
- notes: The caveat is retention, which nobody states: a 1 GiB cap is worth nothing if the file is gone in a week, and that is the one number still missing.
- evidence note: Upload, read-back and SHA-256 match, at 1 MiB. The 1 GiB claim is the vendor's and was not pushed to.
- probe:
  - upload_bytes: 1048576
  - download_bytes: 1048576
  - match: yes
  - status: 200
- extras:
  - cap_stated_bytes: 1073741824
  - sha1_echoed: c96b568c8726029947ffc0e752a2bb7463030153
- evidence:
  - probe:https://pomf.lain.la/upload.php 2026-10-23: POST of 1 048 576 bytes -> HTTP 200, {'success':true,'files':[{'url':'https://pomf2.lain.la/f/nck8aluy.bin','size':1048576,'hash':'c96b568c...'}]}
  - probe:https://pomf2.lain.la/f/nck8aluy.bin 2026-10-23: read-back 1 048 576 bytes, sha256 da0099c231f1182a5d411c8ac5149dfb7a2e3578a3970928490cb78ba92aecc9, full-body hash matched
  - [1] 2026-10-23: 'Max upload size is 1 GiB, wow!' and the comment that uploads had been disabled for a PHP CVE and are back
- sources:
  - [1] https://pomf.lain.la/