Skip to content

Unofficial parody. The software is real. Unofficial parody of infloww.com. Not affiliated with Infloww. The software is real; the jokes are ours.

Inflowwww
Menu

Enterprise

Enterprise plan: $0

Includes the same software as the free plan, because there is only one.

Infloww's enterprise page cites "$2.61 billion USD in revenue generated in 2024 by Infloww users" (infloww.com/onlyfans-crm-enterprise, page stamped Oct 10, 2026). We don't publish a revenue figure for our users, and their 24/7 support and dedicated account managers have no equivalent here.

Who this is for

The README describes the project as an independent reverse-engineering of OnlyFans' public web API for personal / educational use. Nothing here is sold, and there is no enterprise contract. An agency can run it, but tell your creators before you connect theirs.

Using it on a live OnlyFans account may violate OnlyFans' Terms of Service; the risk sits with the creator's account. Read the disclaimer first.

Self-hosting

Inflowwww runs with Docker Compose on a server you control: a Python relay (FastAPI) that holds the captured sessions, a Next.js dashboard, and an autoheal container. The install is the Quick start from the README. The relay and the app bind to 127.0.0.1 on the host, and the app also joins the external n8n_default network with Traefik labels; if you run Traefik on that network it will be published. Otherwise making it reachable is a step you choose: a reverse proxy in front of the app, or the optional Cloudflare quick tunnel profile. Put local edits in a docker-compose.override.yml (the repository ignores it), not in the tracked file.

Your backups

Everything that matters is on the host: service/chatterly.db (SQLite), service/sessions/, service/proxies.json, service/secrets/ and .env, plus the vault image folders (service/vault_thumbs/, vault_posters/, vault_images/), which can't be downloaded again once OnlyFans' signed URLs expire. The service/ ones are bind-mounted into the relay; Compose reads .env. Back them up on your schedule, to your storage, and keep the copies as private as passwords: chatterly.db and proxies.json hold passwords in plain text. Help > Backups has the backup commands and a restore test.

Your proxies

You choose the proxy provider and assign one per creator in Creators > Custom proxy (/creators/proxy). The registry is service/proxies.json on your server.

No vendor lock-in

  • The data is one SQLite file you can open with any SQLite client.
  • The code is one MIT-licensed repository (the project's source folder). Fork it, change it, and keep running your fork.
  • There is no account with us, no licence key and no contract to end.

The license, in full

This is the text of LICENSE in the repository.

The project was renamed; the copyright line below is the original and is reproduced as it stands in the file.

MIT License

Copyright (c) 2026 Chatterly contributors

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.