Your own database, storage, logins and address
Not a tenant column in a shared table. Every agency gets a Postgres instance, a private media bucket, its own login system and its own subdomain, created for it at signup.
sentryq is the CRM we built to run our own creators on Fanvue, from one screen: chatting, earnings, shifts and payroll, coaching, mass messages, welcome sequences and fan lists. On your own subdomain with your own database, live minutes after your first model subscribes.
Since 2025-09, on our own agency.
One agency, three shifts a day.
Chatter, team lead, QA, trainer, admin.
Fanvue webhook to inbox.
The tour
These are the screens your team will live in, drawn from the real product with invented fans and figures, because a screenshot of a real workspace is a screenshot of somebody's money.
Chatting
The CRM stores conversations itself and keeps them fresh from Fanvue in realtime, so a thread opens instantly instead of waiting on the platform. Creator tabs across the top, Online Fans and Notifications one click away, unread and not-answered filters with live counts, and every fan's lifetime spend beside their name.
Earnings
Subscriptions, messages, tips and referrals, gross and net, cut in your agency's own timezone. The dashboard total matches what Fanvue shows you; every receipt is listed with its fan, and every chatter's share is attributed from the conversation that earned it.
Chatting Shifts
Plan the week on the PH or European clock, auto-assign chatters across models, and mark attendance. Chatters clock in and out with break and away rules enforced, and Pay & Fines produces the period from what actually happened, with bonuses and fines on the same page.
Coaching
Team leads record what was taught, for how long, with the Loom that proves it, and tick the problems they saw in live chats. The review queue and the overall view turn that into a trend per chatter, so a monthly review is a look at a chart rather than an argument about memory.
Mass Messages
Choose the smart lists (subscribers, auto-renewing, spent more than $50, expired) or a custom list, exclude the fans a chatter is handling one-to-one, attach vault media with a PPV price, schedule it, and watch sent, reach, views, purchases and revenue as it runs.
Welcome Sequence
Every new subscriber gets the welcome in the model's voice, then timed follow-ups that stop the moment the fan replies or a chatter gets there first. Promo Auto-Renewal watches expiring discounts and re-creates them before they lapse, so a campaign never quietly stops on a Sunday night.
Vault and Fan Lists
The vault mirrors each model's Fanvue folders next to your own uploads, searchable by caption, with photo, GIF, video and audio filters. Dynamic lists describe a segment once (whales, expired subs, fans who replied today) and the CRM refills it every six hours, ready to blast.
Agency Tracking
Every tracking link with its source, clicks, subscribers acquired, conversion and gross, rolled up per model and across the agency. A Server Postback receiver feeds your ad platform, and the fan journey survives the move from anonymous click to paying subscriber.
Team
Rank chatters by revenue, messages or reply time for any period. Shift goals with bonuses appear in the chat while they work; Pay & Fines, Bonuses, Warnings and Feedback live on one page, and Chatter Salaries carries the self-reported view beside the attributed one.
And the rest
Everything on this page is the software we run our own creators on. You get the same build, on your own infrastructure, updated when we update ours.
Not a tenant column in a shared table. Every agency gets a Postgres instance, a private media bucket, its own login system and its own subdomain, created for it at signup.
New releases roll out to every workspace inside a maintenance window you choose, with a health check before and after. A failed update rolls itself back.
Every model's Fanvue connection, sessions and passwords in one place, with the token health the integrations page shows.
Post to the feed from the CRM and run shout-for-shout swaps between your own models.
A payouts queue per model, and chargebacks surfaced before they become a dispute you did not know about.
Tips, new subscribers, unlocks and renewals as they happen, in the app and on your phone's browser.
Chatter, team lead, QA, trainer and admin, each adjustable per permission, with an audit of who did what.
A built-in language checker underlines typos before a fan sees them, tuned to chat slang, never blocking Send.
Spot chatters gaming attribution, and see webhook health, error events and integration status on one admin page.
Chatters work in the desktop app: the clock, focus windows, screen recording and live view for team leads. Everything else runs in the browser.
Conversations, fans, earnings and shifts as files you keep. Servers in Germany, nightly encrypted backups.
sentryq Cloud runs in any modern browser on desktop and tablet, and ships a desktop app for Windows and macOS. Chatters and team leads work in the desktop app: it carries the clock, focus windows, screen recording and live view. Owners and managers can use either.
Isolation
Every agency gets its own database, its own storage and its own address. That is a deployment decision, not a policy — the separation is structural, so nothing we could get wrong in code exposes one agency to another.
A Postgres instance created for you, with its own credentials.
There is no shared table with a tenant column, so there is no forgotten WHERE clause that could return another agency's rows.
A private bucket holding your vault and your message attachments.
Keys are scoped to your prefix, so a bug in one workspace cannot list, read or overwrite another's files.
Your chatters' accounts exist in your workspace and nowhere else.
There is no global user table and no cross-workspace session, so an account cannot be pointed at a different agency.
Your tokens are sealed with AES-256-GCM before they touch a disk.
They are decrypted only inside your own container, for your own requests, and never appear in a log or an API response.
A subdomain of your own with its own certificate.
Your chatters' bookmarks, and the cookies behind them, belong to a host nobody else uses.
How it works
Creating a workspace is free and asks for no card. Nothing is provisioned, and nothing is charged, until one of your models subscribes through Fanvue.
Pick a subdomain and a timezone. This takes a minute and costs nothing: there is no card field anywhere in this flow.
One consent screen on Fanvue. We read your roster so we know which models exist, and we ask for the scopes the CRM needs to run their inboxes.
Open the sentryq listing in the Fanvue App Store from the Fanvue account of the model you want covered, and subscribe. $100 per month, billed by Fanvue to that account. Repeat for each model.
The hub asks Fanvue which of your models now hold a licence. As soon as one does, provisioning starts.
Fourteen steps, live on screen. At the end you get the address of your own CRM and the owner login for it.
Pricing
You pay for the models you want covered. Chatters, managers and QA reviewers are unlimited and free.
Per model
$100per month
Billed through the Fanvue App Store. Each model's own Fanvue account subscribes to the sentryq app, and Fanvue charges that account. No card details ever reach us.
Creating a workspace is free. Nothing is charged until a model subscribes.
One model's inbox, media, earnings and fans inside your workspace, for as many chatters as you want to put on it. Licence a model and they appear; let the licence lapse and their data stays, but their inbox stops syncing.
Your database, your media storage, your subdomain and certificate, every update we ship to our own install, and nightly backups with restore drills. There is no infrastructure line on top of the $100.
FAQ
If yours is not here, write to us before you pay for anything.
Through Fanvue, not through us. Each model's own Fanvue account subscribes to the sentryq app in the Fanvue App Store at $100 per month. Fanvue bills that account and pays us; no card details ever reach sentryq. If you manage five models, five subscriptions are started from those five accounts, and each can be cancelled independently.
Yes, the same build. sentryq Cloud is the software our own Fanvue agency has run on for a year, with twenty creator accounts and three chatting shifts a day. Every workspace gets the same release we run ourselves, on its own infrastructure.
Yes. Every agency gets its own Postgres database, its own media bucket, its own login system and its own subdomain. There is no shared table with a tenant column in it, so there is no query anyone could write that reads across agencies. The hub you sign up on stores only your account, your subdomain and which models are licensed.
Minutes, not days. Once at least one model has subscribed and you have connected your Fanvue agency account, provisioning runs fourteen steps and you watch them happen. You get a link to your own CRM at the end of it.
You connect the Fanvue account that manages your models, and grant read and write scopes for chat, media, posts, creators, insights and tracking links. That is what lets the CRM read conversations and send on your behalf. You can revoke it from Fanvue at any time; the CRM keeps working for everything already stored and stops syncing.
No. Fanvue serves the CRM's reads from the same accounts your chatters work in, so the CRM is built to read as little as possible: conversations are stored and kept fresh by webhooks, heavy views are cached and refreshed in the background, and outbound requests run under a per-agency rate budget.
Yes, for Windows and macOS. Chatters and team leads work in it: it carries the clock, the focus windows, screen recording and live view. Owners and managers can use the browser or the desktop app; both open the same workspace.
Any time, per model, from that model's Fanvue account. The licence runs to the end of the period already paid for. When the last licence lapses, the workspace is suspended rather than deleted, and your data is kept for 30 days so an accidental cancellation is recoverable.
Yes. Your workspace has an export that produces your conversations, fans, earnings and shift records as files you keep. It is yours; we do not hold it hostage to a subscription.
On dedicated servers in Germany, operated by Hetzner. Nothing is hosted outside the EU except the services listed on our subprocessors page, each of which is named there with what it does.
No. You pay per model, not per person. Add as many chatters, team leads, QA reviewers and trainers to your workspace as you need; the price does not move.
Signing up costs nothing and asks for no card. You will see your own subdomain, your roster read straight from Fanvue, and exactly what each model would cost — before anybody subscribes to anything.
Replies monday to friday, 09:00-18:00 cet.
Already know you want it?
Subscriptions are started from each model's own Fanvue account, in the App Store. You can do that before or after creating your workspace — the hub picks the licence up either way.
Available on the Fanvue App Store