This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
Hubbee
Push design, content and updates to every WordPress site
Run WordPress sites for clients? Hubbee pushes design to them, not just updates. Real React + Three.js backgrounds, elements and text effects land on a client's page with no build step, via Elementor. Content the same way: set a headline or phone number once, push it to every site at once. Every pending plugin, theme and core update in one list. Uptime probed server-side every 2 minutes, on every plan. Free for 3 sites.
Hi everyone — Timur here. I lead development on Hubbee at 2BrandsMedia, where it started as our own internal tool.
Every client site had its own login. Changing one phone number or one campaign headline meant a morning of wp-admin tabs and password-manager round trips. We tried WordPress multisite, ManageWP and MainWP (updates and backups done well, content not at all — neither will push a changed phone number to twenty sites), and our own REST scripts (fine until one site's REST route changed). So we built what we actually wanted, ran our own client sites on it, and we are opening it up now.
Content push. Define a token once — a headline, a phone number, opening hours — and push it to one site or to a whole client's sites in one action. Every push is HMAC-SHA256 signed with a per-site secret, versioned, logged, and only the changed values go over the wire. Every previous value is kept for 90 days, so you can always see what a token used to say before you changed it.
Updates and uptime. Plugin, theme and core updates are inventoried per site and rolled up across the workspace, so what is pending everywhere sits in one list. Uptime is a server-side probe every two minutes on every plan, Free included, and a site is flagged offline after eight minutes of silence. That is separate from the health snapshot each site reports about itself — on Free that refreshes when you open the dashboard, on Pro every five minutes.
Design assets. Backgrounds, animated elements and text effects live in a library and are assigned per site, so a site only downloads what you give it. They embed through Elementor today; native WordPress embedding is on the roadmap, not shipped. Content push, updates and uptime work on any WordPress site.
Honest limits: Hubbee also means one plugin install per connected site. The production stack runs on a Hetzner box in Germany, with nightly backups pulled to a second machine we control; billing goes through Paddle and transactional email through Resend (US, under standard contractual clauses). And if Hubbee is down your sites are not — every token we push is written into your own WordPress database, so the content stays put either way.
What I would like your read on:
Ceilings. Free is 3 sites, no card. Pro is 25 sites at $30/mo, Agency 100 sites at $90/mo (billed yearly that works out to $25 and $75). Too tight, too generous?
Going from a handful of client sites to thirty — what breaks first for you? For us it was content, not updates; updates were the part everyone already had a tool for.
Content sources. Only Google Sheets and Airtable ship today. Which one would you actually connect next?
I am in the thread all day.
About Hubbee on Product Hunt
“Push design, content and updates to every WordPress site”
Hubbee was submitted on Product Hunt and earned 2 upvotes and 1 comments, placing #160 on the daily leaderboard. Run WordPress sites for clients? Hubbee pushes design to them, not just updates. Real React + Three.js backgrounds, elements and text effects land on a client's page with no build step, via Elementor. Content the same way: set a headline or phone number once, push it to every site at once. Every pending plugin, theme and core update in one list. Uptime probed server-side every 2 minutes, on every plan. Free for 3 sites.
On the analytics side, Hubbee competes within Design Tools, SaaS and WordPress — topics that collectively have 329.1k followers on Product Hunt. The dashboard above tracks how Hubbee performed against the three products that launched closest to it on the same day.
Who hunted Hubbee?
Hubbee was hunted by Timur Bilgin. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of Hubbee including community comment highlights and product details, visit the product overview.
Timur Bilgin
Hi everyone — Timur here. I lead development on Hubbee at 2BrandsMedia, where it started as our own internal tool.
Every client site had its own login. Changing one phone number or one campaign headline meant a morning of wp-admin tabs and password-manager round trips. We tried WordPress multisite, ManageWP and MainWP (updates and backups done well, content not at all — neither will push a changed phone number to twenty sites), and our own REST scripts (fine until one site's REST route changed). So we built what we actually wanted, ran our own client sites on it, and we are opening it up now.
If you would rather watch than read: the design side at https://youtu.be/b3V3FJqC9VA, the site-management side at https://youtu.be/17dpJ5632Wk.
Three things it actually does:
Content push. Define a token once — a headline, a phone number, opening hours — and push it to one site or to a whole client's sites in one action. Every push is HMAC-SHA256 signed with a per-site secret, versioned, logged, and only the changed values go over the wire. Every previous value is kept for 90 days, so you can always see what a token used to say before you changed it.
Updates and uptime. Plugin, theme and core updates are inventoried per site and rolled up across the workspace, so what is pending everywhere sits in one list. Uptime is a server-side probe every two minutes on every plan, Free included, and a site is flagged offline after eight minutes of silence. That is separate from the health snapshot each site reports about itself — on Free that refreshes when you open the dashboard, on Pro every five minutes.
Design assets. Backgrounds, animated elements and text effects live in a library and are assigned per site, so a site only downloads what you give it. They embed through Elementor today; native WordPress embedding is on the roadmap, not shipped. Content push, updates and uptime work on any WordPress site.
Honest limits: Hubbee also means one plugin install per connected site. The production stack runs on a Hetzner box in Germany, with nightly backups pulled to a second machine we control; billing goes through Paddle and transactional email through Resend (US, under standard contractual clauses). And if Hubbee is down your sites are not — every token we push is written into your own WordPress database, so the content stays put either way.
What I would like your read on:
Ceilings. Free is 3 sites, no card. Pro is 25 sites at $30/mo, Agency 100 sites at $90/mo (billed yearly that works out to $25 and $75). Too tight, too generous?
Going from a handful of client sites to thirty — what breaks first for you? For us it was content, not updates; updates were the part everyone already had a tool for.
Content sources. Only Google Sheets and Airtable ship today. Which one would you actually connect next?
I am in the thread all day.