Track who's winning in your niche. Decode the patterns that work. Riff on them, in your own voice.
Self-hosted. Your server. Your session. Your edge.
we never see your data · hand-deployed, not SaaS · 2026 cohort
Watch it work
One operator post. Three moves. End-to-end, on your infrastructure.
Sample data. Your deployment runs on your server, your X session, your operators.
Three moves
Monitor the operators that matter in your niche. On your server, with your X session, on your account. Threading, replies, engagement context. All preserved.
AI pipelines extract the hooks, tones, formats, and CTAs that drive engagement. Patterns surface in a dashboard built around how you actually think.
Generate content drafts grounded in what's working. Riffed in your voice, not flattened to AI-slop.
What you actually get
"{N} lessons from {time} building {topic}. #1 will surprise you"
"Most people {action}. The truth is {opposite}. Here's why"
"How I {achievement} in {timeframe} with {method}"
copy-paste · niche-blind · sounds like everyone
{
"tweet_id": "1773829...",
"user": "@growth_dr",
"text": "7 pricing mistakes...",
"metrics": {
"likes": 1843,
"replies": 92,
"retweets": 38
},
"media": [],
"lang": "en"
} structured · technical · zero insight
"4 onboarding mistakes I made in my first cohort. #2 still stings two quarters later"
specific · niche-aware · publish-ready
Dashboard
Tracked operators, decoded patterns, drafts queued. All in one view, refreshed in real time.
Sample dashboard. Yours fills with your operators after the first scrape.
How it works
We map your niche, your operators, your voice. You leave knowing whether this fits — even if the answer is no.
The engine lands on your server, authenticated as you on X. We log out and the system runs on its own — without us. No SaaS middleman, no shared database, no vendor lock.
Track who's winning. Decode what works. Riff drafts in your voice. We're around for updates and tuning when you need us.
Founder note
@crewtives
I built Whet because I needed it. I was decoding what works on X manually. Reading threads at midnight, reverse-engineering hooks, retrofitting drafts into my voice. Eating up my whole week.
Whet is the system I wished existed. Track. Decode. Riff. End-to-end, on your VPS, in your voice.
If you want it deployed in your infrastructure, let's talk.
Common questions
You operate the scraper. On your VPS, with your X session, on your account. We sell deployment and maintenance. You own the data and the operation. We're consultants and integrators, not data vendors. Your legal team will appreciate that distinction.
One-time setup fee depending on scope. Optional monthly retainer if you want updates and tuning. We talk numbers on the call once we know what you actually need. Generic pricing for a hand-deployed product is usually wrong for somebody.
On your VPS. Always. No SaaS database, no third-party storage, no vendor lock. If we go separate ways tomorrow, the system stays running on your infrastructure and the data stays yours. That's not a feature. That's the whole product.
You need a VPS and willingness to keep root access. We deploy and document; you operate. If you've ever SSH'd into a server, you're more than fine. If not, we can recommend a managed VPS provider that gets you 80% of the way there.
That's part of why this is a managed deployment, not raw open-source code thrown at you. We track changes, ship updates, keep your scraper in sync with what your account can actually do. The retainer covers it. If you don't take the retainer, you get the source and the docs to handle it yourself.
If you post 3-7 times a week on X, monetize an audience, and you're tired of decoding what works in your niche by hand, yes. If you want a templates app or a content calendar, no. The 15-minute call sorts this out fast.