Upgrade to the most self‑hosted CRM on the market

Inflowwww is an independent reverse-engineering of OnlyFans' public web API. Running it against a live account may violate OnlyFans' Terms of Service. Use it at your own risk. The project is not affiliated with or endorsed by OnlyFans. Read the disclaimer first.

You need a server with Docker Engine 25+ and Compose 2.20+. The healthchecks use start_interval, which older versions don't support. On Ubuntu 24.04, install it with Docker's own Ubuntu instructions; the distro's docker.io package may be older; check docker version.

1. Clone the repository

Cloning downloads the repository (the project's source folder) to the server.

git clone https://github.com/BlackPhoenixSlo/Opensoursed_infloww.git openinflowwww
cd openinflowwww

2. Create the network, the state files and .env

The app joins an external network called n8n_default, so it has to exist. (The network name comes from the maintainer's own Traefik setup; you don't need n8n.) The state files are bind-mounted, so they have to exist as files, not directories.

docker network create n8n_default
echo '{"proxies": []}' > service/proxies.json
touch service/chatterly.db
mkdir -p service/sessions

cat > .env <<ENV
SHARE_TOKEN=$(openssl rand -hex 24)
SESSION_SECRET=$(openssl rand -hex 32)
CHATTER_SESSION_SECRET=$(openssl rand -hex 32)
ENV

Without SHARE_TOKEN the share-link gate is off (sign-in is the only gate), and without the session secrets every rebuild signs everyone out. ADMIN_PASSWORD is optional. It is the only check on the admin actions (view as another user, transfer or delete a user), so anyone signed in who knows it can use them on any account; if you set it, make it long and random. Without it those actions are refused.

3. Start the stack

docker compose up -d --build

This starts openinflowwww-relay (127.0.0.1:8787), openinflowwww-app (127.0.0.1:3001) and openinflowwww-autoheal. A server usually has no browser, so from your own computer forward the port with ssh -L 3001:127.0.0.1:3001 user@server and open http://127.0.0.1:3001/?t=<SHARE_TOKEN> there (grep SHARE_TOKEN .env on the server prints the token; it is remembered after the first visit). Register the owner account on the Sign in / Register screen at /login first. Ignore the installer link on the login screen; it points at an older setup.

127.0.0.1 only works on the server itself, or through your ssh -L tunnel. Your laptop, your phone and your chatters reach the dashboard at the server's URL. 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. One way is a domain behind a reverse proxy on the server: point Caddy or nginx at 127.0.0.1:3001, or use the Traefik labels in docker-compose.yml, which expect your own Traefik on the n8n_default network with a websecure entrypoint and a cert resolver named mytlschallenge. Put your host (in place of your-host.example.com) and those names in a docker-compose.override.yml, which the repository already ignores, so git pull stays clean; don't edit the tracked file. The other is the tunnel profile: docker compose --profile tunnel up -d starts a Cloudflare quick tunnel, docker compose logs openinflowwww-tunnel shows its trycloudflare.com URL, and the URL changes on every restart. Both make the dashboard public, so before either, read the security notes; use the quick tunnel only to try it, not for a live team.

4. Capture each creator's session

Capturing a session means signing in to the creator's OnlyFans once, so the dashboard can use that login. The creator cannot paste it themselves: the Creators page is owner-only. They need Chrome on a computer, not a phone. They install the extension (open chrome://extensions, turn on Developer mode, click Load unpacked and pick the loginExtensionMulti folder the owner sends them), log in on onlyfans.com, open Messages, click Copy curl, and send the copied text to the owner over a channel they would trust with their password. The owner pastes it on the Creators page. No password is shared. The copied text is a live login to their account, so treat it like one.

In chrome://extensions it is listed as "Inflowwww Login Capture (OF + Fansly)"; the Creators page card calls it "Chatterly Login Capture". Both are old names of the same extension. On the Creators page, from a computer (the card is hidden on phones), ignore the Install Chrome Extension button, paste the copied text into the Paste cURL card and click Bootstrap from cURL.

The folder is loginExtensionMulti/ at the top of the repository. Its manifest asks Chrome for access to onlyfans.com and fansly.com only, and for permission to read those sites' cookies, see the open tabs, run its scripts on those sites, keep its own settings and write to the clipboard. Remove the extension after the capture.

The creator's account will be seen from the server's IP (or the proxy you assign) from then on; assign a proxy before pasting if that matters (step 5 shows where).

The desktop app's own capture button does not work against this relay today; use the Chrome extension. The accounts appear in Creators > Manage creators (/creators). If a session stops working, capture it again the same way.

Fansly is partly built: the Docker image (a packaged copy of the app) ships the Fansly client, and 4 of the Fansly Manager's 16 pages are built, behind a setting.

5. Add your proxies

Assign a proxy to each creator in Creators > Custom proxy (/creators/proxy). The list is kept in service/proxies.json, the proxy registry on the host. You supply the proxies; none are built in.

6. Invite your chatters

Invite each chatter from Employees > Manage employees > Chatters (/employees): under "Invite a new chatter", the "Mint invite URL" button makes a one-time /chatter-login?token=... link that expires after 24 hours, and they pick a username and password there. Logins are a share token for the dashboard, then per-user logins: the owner at /login, each chatter at /chatter-login. Chatters sign in with their own login; the share token is for the owner (it does not stop anyone from registering; see Security notes). Owner pages such as Creators, Vault Pro and Tracking links are hidden from chatters.

Infloww's switch page describes its private Telegram support as "Real human support, no AI" (infloww.com/switch-crm, page stamped Oct 10, 2026).

Ours: real human support, no AI. The human is you.

In practice that means the README, the code, and the issue tracker on GitHub. The LLM keys (DEEPSEEK_API_KEY, DEEPINFRA_API_KEY, ZAI_API_KEY) are optional, billed by their providers, and the dashboard works without any of them.