Belonging Intelligence · Infrastructure layer

Turn belonging into retention, renewals and revenue.

Hytribe is the belonging infrastructure enterprises, universities and communities use to reduce attrition, protect renewals and lift lifetime value — by matching members into small trusted tribes inside the platforms you already run, and proving the impact with privacy-safe cohort analytics.

Tribes of
3–5
Cohort floor
n ≥ 5
Pilot
30–90d
REST APISDKsTLS in transitGDPR & PDPA alignedDPA availableAggregate-only · n ≥ 5Signed DPATenant isolationHard-delete on requestREST APISDKsTLS in transitGDPR & PDPA alignedDPA availableAggregate-only · n ≥ 5Signed DPATenant isolationHard-delete on request
Tribe size
3–5
Small enough to trust. Large enough to be a group.
Cohort floor
n ≥ 5
Enforced at the data layer for every metric.
Pilot window
30–90d
Treatment-vs-control readout, one quarter.
Match latency
<200ms
Typical response for a mid-sized cohort.
Start where you buy

Jump to the answer your team needs to greenlight the pilot.

Why customers deploy Hytribe

One platform. Three levers on retention.

Automatic matching

Interests, goals, availability and conversational signal — no manual curation.

Drops into what you run

OAuth into Slack or Discord, a Telegram bot, or REST into your own product. Members never leave the platform they already use.

Stays alive on its own

Anton, the AI facilitator, introduces each tribe, nudges quiet ones, and flags groups that need attention.

The product

One connection layer. Three APIs that move the number on your board.

Match API

Forms stable tribes of 3–5 using compatibility signals.

Read reference

Ritual API

Schedules recurring check-ins and rituals that keep relationships alive.

Read reference

Insights API

Measures community health as aggregate, cohort-level analytics only.

Read reference
Insights, written exactly this way

Show only aggregate, cohort-level metrics gated by an n ≥ 5 floor:

  • Community participation
  • Recurring-interaction rate
  • Connection depth
  • Tribe activation
  • Cohort engagement trend

Do NOT display individual belonging scores, individual isolation/loneliness risk, or any per-person wellbeing number.

Community health · Q3
Cohort of 128 · n ≥ 5 applied
Synthetic sample data
Participation
72%
Recurring rate
58%
Tribe activation
84%
Cohort engagement trend
See the ROI engine run

From roster to retention lift, in five steps.

1
Import members
2
AI matching
3
Tribes of 3–5 created
4
Weekly rituals
5
Aggregate insights
Interactive demo

Run a match

Illustrative · synthetic data
Tribes formed
0
Avg compatibility
Processing time
How matching works

From vectors to trusted tribes, in four steps.

Step 1
Profile

Each member embedded into an interests / goals vector.

Step 2
Pair

Nearest-neighbour search plus a stable-roommates algorithm — pairings no two people would both want to swap out of.

Step 3
Cluster

Stable pairs grow into tribes of 3–5, gated by a compatibility floor.

Step 4
Place or queue

Outliers are queued and prioritised next round — never dropped.

Community platforms

Manage content. Bill you monthly.

  • Posts
  • Forums
  • Events
  • Messaging
Hytribe

Manages relationships. Moves retention.

  • AI matching
  • Micro-tribes
  • Recurring rituals
  • Aggregate community-health analytics (n ≥ 5)
Privacy by architecture · the moat

Belonging measured at the group. Never at the person.

No individual emotion inference.

Analytics are aggregate-only, enforced at the data layer by an n ≥ 5 cohort floor.

Wellbeing instruments disabled for enterprise tenants.

UCLA-3, WHO-5 and psychological profiling are off. No special-category or health data is processed on the customer's behalf.

Customer is controller. Hytribe is processor.

We act on the customer's instructions. A DPA is available. Hytribe does not sell customer data.

No pixels, no background collection.

Members flow in only from the fields the customer chooses to send.

Security · honest and dated

What's true today. What's on the roadmap.

We never imply a certification we don't yet hold.

Today
  • HTTPS / TLS in transit
  • Per-community API keys (ht_test_ / ht_live_)
  • Tenant isolation by community_id
  • RBAC and audit logging
  • Signed DPA
  • Retention & hard-delete path
Roadmap
  • SOC 2 readiness
  • ISO 27001
  • Penetration testing
  • Formal SLA

Labelled as roadmap. No certification is implied.

Sub-processors
  • Railway (hosting)
  • Neon (Postgres)
  • OpenAI (embeddings)
  • Anthropic (Anton)
  • Resend (email)

Plus delivery channels. 30-day notice on new sub-processors.

Solutions by segment

Where Hytribe pays for itself.

Each segment maps to a specific line item — attrition, dropout, occupancy, renewals, cohort ROI — that belonging directly moves.

Enterprise

Cut attrition costs and lift productivity by reducing employee isolation.

Universities

Protect tuition revenue by reducing dropout-driving loneliness and disengagement.

Residential & smart cities

Raise occupancy and property value through stronger resident retention.

Coworking spaces

Increase membership renewals by reducing churn-driving isolation.

Professional associations

Grow renewal revenue by strengthening member engagement and belonging.

Accelerators

Improve cohort completion and portfolio ROI by preventing founder burnout.

Integrations

Install via OAuth in minutes. Or wire the REST API once and it runs itself.

Live
SlackDiscordTelegram
Roadmap
Microsoft TeamsREST into your appBambooHRRippling
Developers

Real endpoints. Real request shape. Copy-paste ready.

Talk to Engineering
# 1 · Register a community — returns your API key
curl -X POST https://api.hytribe.xyz/communities \
  -H "Content-Type: application/json" \
  -d '{ "name": "Indie Hackers NYC", "platform": "custom" }'

# 2 · Sync a member (fire from your signup / profile-update)
curl -X POST https://api.hytribe.xyz/members \
  -H "X-API-Key: ht_live_9f2c…" \
  -d '{ "platform_user_id": "U012AB",
        "profile_text": "founder, climbing, AI" }'

# 3 · Run matching — returns tribes
curl -X POST https://api.hytribe.xyz/match \
  -H "X-API-Key: ht_live_9f2c…"
Example response
{
  "tribes": [
    { "id": "trb_01", "members": ["U012AB","U023CD","U087QR","U118TT"] },
    { "id": "trb_02", "members": ["U033EF","U041GH","U059IJ"] }
  ],
  "compatibility_score": 0.94,
  "queued": [],
  "processing_time": "132ms"
}
Pricing · built for procurement

Pay for measurable outcomes. Scale when the pilot pays back.

Pilot
$5,000–$10,000
flat · 30–90 days

50–200 seats · treatment-vs-control readout.

Start a Pilot
Enterprise
from $15
per seat / month · annual

Indicative band $12–$18. Volume and multi-year discounts. Premium HR analytics tier available.

Talk to Sales
University
$65
per student / year

≈ $5–$6 / student / month. Annual student-belonging plan or cohort package.

Talk to Sales
Developer / API
Free
sandbox · usage-based in production

White-label / API licensing custom.

Get API keys
Proof & design partners

We ship pilots, not logos.

We won't invent customer logos, named case studies or metrics. Everything on this site labelled as a scenario is synthetic and clearly marked. Real outcomes publish as pilots complete — with permission, with numbers, with named buyers.

Enterprise pilot · in progress
University pilot · in progress
Smart-city pilot · in progress
Accelerator pilot · in progress
FAQ · what procurement actually asks

Answers before you have to ask.

About

We all belong.

Our mission is to build the belonging infrastructure for humanity. Our vision is that every person has trusted communities wherever they live, work or study — warm and human, without asking anyone to opt into a worldview.

Delaware C-Corp. Singapore HQ (coming).

Hytribe
PLEC
Passion · Loyalty · Excellence · Consistency
Book a 30–90 day pilot

Run one quarter. Show finance the retention lift. Scale from there.

Treatment-vs-control readout on your people, in your platform. Aggregate-only metrics. Signed DPA. Your data stays yours.