Hub · Product overview
One core. Many communities, each its own world.
Hub gives every tenant a branded fan and community site built from switchable modules and run from one shared admin console. This page explains what the platform is, what each module does, and how the modules work together.
- 33
- feature modules
- 7
- feature families
- 3
- tenant experiences
- 1
- shared console
Why it exists
Built for what community owners actually struggle with.
“Building our own site would take months.”
Everything is already built. Choose features, add a brand and launch.
“Fans visit once and never come back.”
Daily challenges, streaks, points, levels and leagues give a reason to return every day.
“Our content is scattered everywhere.”
News, podcasts, discussions, games, surveys and competitions sit together in one place.
“We don't know what's working.”
The dashboard shows activity across every feature, compared with the previous period.
“We need control over what gets published.”
Writers, reviewers and creators get the right access, and content is approved before it goes live.
“Our fans speak different languages.”
Content is published in several languages, each with its own web address.
01 · The platform
Custom on the outside,
shared underneath.
Every tenant gets its own member-facing experience. Some need a completely different UI and UX, so we build it for them. All of them run on the same core and are managed from the same admin console.
Member experiences
A football-first fan world with its own UI and UX, built on a selected set of modules.
hub-tenant-befootball
A bespoke community site designed around its own brand and journeys.
hub-tenant-rov
The complete reference site: every module, from sign-in to Web3, ready to switch on.
hub_tenant-frontend
Tenant Admin
One back office for every tenant
Each tenant signs in to its own space: content, members, rewards, competitions and reports. The menu only shows the modules switched on for that tenant.
hub_tenant-admin-frontend
Platform team
Sets the stage
Creates tenants, switches modules, approves branding, sets languages and schedules maintenance.
Hub core
One engine behind every community
Each tenant’s data lives in its own separate space.
Web3 service, connected where the Web3 add-on is on
Custom where it matters
Each community's look and journeys can be designed from scratch. We don't force a template on them.
Shared where it counts
One console, one set of modules and one approval flow, so every improvement reaches every tenant.
Switch, don't rebuild
A new capability is a module to switch on, not a new project. Custom builds pick only the modules they need.
02 · Modules
Everything a community needs,
as building blocks.
Seven feature families, including the optional Web3 add-on, plus the member essentials and the foundations every tenant gets. Each module can be switched on or off per tenant. Open any module to see what it provides and what it connects to.
Publish4
Stories, shows and fan content: the reasons people visit.
Engage4
Get members talking and taking part.
Reward5
Recognise and reward loyal members: the reasons people come back.
Compete4
Friendly competition all season long.
Grow3
Turn members into promoters and keep in touch.
Earn1
Create value for sponsors, and measure it.
Web37
An optional add-on: reward members with the community's own token. Our team switches it on and sets it up.
Members & access5
How people arrive, sign in, find things and stay in the loop.
Foundations7
What every tenant gets: brand, access, languages and a safe way to run live.
03 · Connections
Modules are better together.
Modules are independent, but they link up where it helps: a survey inside an article, a mission powered by a survey, news in the welcome email, and points flowing in from everywhere. Pick a module to see what it connects to.
Publish
Engage
Reward
Compete
Grow
Earn
Web3
Members & access
Foundations
Hover a module to see how they connect.
04 · The rewards loop
Why members come back.
Engagement modules aren't separate add-ons. They share one points economy, so activity anywhere on the site feeds progress and standing everywhere else.
- 01
Members take part
They complete quests and daily challenges, predict matches, answer surveys, refer friends, redeem codes and take on Web3 quests.
- 02
Points land in one balance
Every activity pays into the same points balance, whichever module it came from.
- 03
Progress becomes visible
Members move up levels, unlock achievements and earn badges, all shown on their profile.
- 04
Standing starts to count
Points place members on the leaderboard and in weekly or monthly leagues. Where Web3 is on, reward cycles turn those points into token rewards.
05 · Tenant Admin
Run everything from one place.
Every tenant, whether it runs a custom experience or the full Hub, manages its community from the same console. Several admins can share it, so a tenant can bring in their whole team.
- Dashboard
- News
- Podcasts
- Quests
- Leaderboards
- Settings
New members
+18%
Quest activity
+32%
Sign-ups
+9%
Activity · this period vs last
Dashboard
Activity for each feature, against the previous period.
Members
Add, edit, verify, suspend or remove, one at a time or in bulk.
Roles
Admins, authors, publishers, creators, podcast creators, influencers.
Approvals
Articles, podcasts, game suggestions, reviews and quest proof.
Moderation
Keep the forum and creator feed safe.
Branding
Request changes to logo, colours, fonts and headline text.
Rewards
Quests, levels, achievements, badges and redeem codes.
Reports
Ads, referrals, survey answers and form responses.
Web3
Admin wallet, reward cycles, staking and farming pools, and Web3 quests.
06 · Who does what
The right access for every person.
Roles decide who can write, review, submit or track what. Visitors can look around freely. To post, vote or collect rewards, they create a free account in seconds.
Visitor
Browses news, podcasts, the forum, leaderboards and competitions, and answers public surveys.
Member
Joins in fully: posts, votes, takes on quests, earns rewards, predicts and joins teams.
Creator
Shares photos and videos and builds a following.
Author
Writes articles that are reviewed before going live, with a personal dashboard.
Publisher
Reviews and approves articles.
Podcast Creator
Submits and manages episodes, reviewed before going live.
Influencer
Promotes the community with a custom referral code and sees the results.
Tenant admin
Runs the console: content, members, rewards, competitions, Web3 and reports.
Platform team
Sets up tenants, switches modules, approves branding, manages languages and maintenance.
07 · How a tenant comes to life
From idea to live in five steps.
Choose the features
The tenant picks the modules that fit their community. More can be added later.
We set up the tenant
The platform team creates the tenant, its data space and the first admin account.
Make it theirs
Logo, colours and text are submitted, checked by our team and applied.
Shape the experience
A custom build like befootball or ROV, or the full Hub experience, connects to the same core.
Go live
The site launches with its settings locked. We look after maintenance and updates.
Adding Web3? We also set up the community token and reward pools, and register the tenant's own wallet as the administrator.
08 · Foundations & trust
Safe, dependable, and theirs.
Some things aren't modules. Every tenant gets them, whatever plan they're on.
Branding
Nothing goes live by accident
Tenants request changes to their logo, colours, fonts and headline text. Our team reviews each one, and the current look stays live until it’s approved.
Feature switches
Only what they’ve chosen
Our team switches each module on or off. When a module is off, it disappears from the site, the console menu and every place it could be embedded.
- Community forum
- Match predictor
- Fan awards
- Wallet connection
Languages
One list, used everywhere
Each tenant’s supported languages appear in every module at once. Add a language at the tenant level and it’s available everywhere.
Their data stays theirs
Each community's data is kept separate from every other community.
Nothing goes live by accident
Content and branding go through approval, and live settings are protected.
Planned maintenance, clearly communicated
Members see a friendly “back soon” message while the team keeps working.
Ready for many languages
Content is translated into each language the tenant offers.
Tenants control their rewards
Their own wallet is the administrator, and each reward cycle is funded and published from it.
09 · Good to know
Clear about what’s included today.
Being upfront about limits builds trust. When you talk about Hub, use these notes as they are.
Works today, with these notes
- Branding changes are checked by our team before they go live. The current look stays until then.
- Our team switches features on and off and sets each tenant's languages.
- Podcast episodes are added as YouTube links.
- Newsletter sign-ups can be collected and downloaded. Sending newsletters from the console isn't available yet.
- Tournament entry fees are for display only, and no payments are taken.
- Badges are earned automatically for forum activity. Manual awarding isn't available yet.
- Web3 features are optional. Our team switches them on and sets up the token and reward pools.
- Web3 features currently run on a test network.
- Members need their own wallet for Web3 features, and pay a small network fee for actions like staking, claiming and swapping.
- Reward cycles are paid in the tenant's token and funded from its own wallet. Members need a linked wallet to be paid.
- Swap prices are estimates. Swaps happen on a supported exchange, not on the site.
Not live yet
These aren’t available yet.
- Scheduled publishing and automatic article expiry
- Tournament results and standings from the console
- Google sign-in
- Connecting social accounts (X, Discord, Twitch, Telegram)
- Live streaming
- A member feedback inbox
- Sending newsletters or email campaigns
- Awarding badges by hand
10 · Questions
The questions people ask.
No. Our team sets up the site, and the tenant manages everything from the admin console.
Every community, its own home.
Need to explain Hub to a new tenant? Start with the modules they care about and follow the connections from there.
Back to the modules