eroq store
Storage that won't drop you.
Adult products die twice: once when the model refuses, once when the bucket terminates. The Store is NSFW-friendly object storage on a global CDN — governed by the same written policy as our models, priced once at upload, built to hold what the API generates.
2 credits / 10 MB uploaded · one-time · fair-use serving included
The Store is one pillar of eroq — the same key drives our uncensored roleplay API, image and video generation, and voice. Generate with one call, host with the same one.
Why it exists
Mainstream infrastructure has an adult-content clause. You are it.
The termination pattern
Big-cloud buckets and image CDNs exclude adult media in their acceptable-use terms. Enforcement is not a warning — it is an account closure with days of notice, and every avatar, gallery and clip your product serves goes down with it.
A written policy instead
The Store runs under the same four-paragraph policy as the models: mature content of adult, fictional characters is the supported use case. The hard walls — minors, real people, illegal content — are explicit, enforced, and yours to rely on contractually.
How it works
Three steps, no ceremony.
- 01
Upload
One multipart POST with your key — a generated image, a clip, an avatar, anything up to 100 MB.
- 02
Get the URL
The response carries the public CDN URL immediately. No buckets, no ACLs, no signed-URL ceremony.
- 03
Serve forever
Global edge delivery, storage included for the life of your account, fair-use bandwidth built into the one-time price.
curl https://eroq.ai/v1/storage/objects \
-H "Authorization: Bearer $EROQ_API_KEY" \
-F name=poster.webp \
-F [email protected]Pricing
Pay once, at upload.
| What you store | Size | One-time cost |
|---|---|---|
| Avatar or gallery image | ≤ 10 MB | 2 credits |
| Voice line or short clip | ≤ 20 MB | 4 credits |
| Generated video | ≤ 60 MB | 12 credits |
≈ 2¢ per 10 MB at pack rates. Storage for the life of the account; serving included within fair use.
The honest comparison
Managed for adult products, or assembled from parts.
You can absolutely build this yourself on a generic CDN — we respect that stack. The Store exists for products that would rather spend those weeks on their product, and would rather hold a written adult-content policy than an open policy question.
| eroq Store | DIY — generic CDN + bucket | Mainstream media platforms | |
|---|---|---|---|
| Setup | One multipart POST | Buckets, pull zones, keys, TLS, cache rules | Account, SDK, content review |
| Adult content | Supported in writing — same AUP as the models | Policy homework is yours: AUPs are general-purpose and the account risk is yours to carry | Commonly excluded outright |
| Pricing | 2 credits / 10 MB, once — serving included in fair use | Monthly storage per GB + metered egress, forever | Monthly tiers, transformation quotas |
| Pairs with generation | store: true on the same API call | Glue code you write and operate | Glue code you write and operate |
| Ops surface | None — it is an API response with a URL | Yours: monitoring, purges, key rotation | Some: quotas, invalidations |
Positioning as of August 2026 — verify current terms on each provider's site. The ranked breakdown of NSFW-friendly storage options lives on the blog.
FAQ
The storage questions.
Is adult content allowed on the Store? +
Yes — that is why it exists. The Store is governed by the same acceptable-use policy as the models: mature content of adult, fictional characters is supported; minors, real-person content without consent, and anything illegal are banned absolutely.
How is the Store different from Bunny, S3 or Cloudinary? +
Those are excellent generic infrastructure — and generic is the point of difference. They price storage monthly per GB plus egress, their acceptable-use policies are written for the whole internet (researching where lawful adult content stands, and carrying the account risk, is on you), and wiring them to a generation pipeline is glue code you operate. The Store is one API call with a one-time price, an AUP written for adult products, and store: true integration with image and video generation. Managed versus assembled — that is the whole comparison.
What does serving cost? +
Nothing beyond the upload. You pay 2 credits per started 10 MB once; storage lasts as long as your account and serving is included within fair use. Sustained multi-terabyte egress on a single object moves to metered pricing, with notice — a clause for hotlinked viral files, not for normal products.
Why not just use a mainstream bucket and CDN? +
Because their terms exclude adult content, and enforcement arrives as an account termination with days of notice — taking every file your product depends on with it. Purpose-built infrastructure with a written policy is the difference between a product and a gamble.
What formats and sizes are supported? +
Any content type, up to 100 MB per upload — images, video, audio, archives. Larger media pipelines (multi-GB video) are on the roadmap; talk to us.
Can I delete files? +
Yes — DELETE /v1/storage/objects/{id} removes the file from the origin immediately, and edge caches drain within minutes. Upload credits are not refunded since the storage was consumed.
Generate. Store. Ship.
One key covers the models and the Store — the 50 free credits are enough to generate an image and host it.