ten_cubed
ten_cubed caps your network at 10 close connections across 3 degrees of reach — a hard ceiling that mirrors how human trust actually works. No feeds tuned for virality. No followers. No influencers.
Last verified:
What is ten_cubed?
ten_cubed is a bounded social graph implementation that caps user networks at 10 direct connections across 3 degrees of reach (maximum 1,110 total reachable nodes). It's designed for developers building social applications that prioritize meaningful connections and meaningful interactions over viral growth and scaled engagement.
ten_cubed pricing
Pricing model: Freemium
ten_cubed pros
- Hard network cap prevents virality and coordinated manipulation from scaling
- User-controlled depth settings (10 to 1,110) provide privacy-first flexibility
- Eliminates influencer economy—no follower accumulation or audience monetization
- Simple PostgreSQL implementation: single recursive CTE query with no specialized infrastructure required
ten_cubed cons
- Not suitable for broadcast or one-to-many platforms—audience permanently capped at 1,110
- Graph volatility: dropping a first-degree connection orphans their entire downstream branch
- Requires careful application-level handling of orphaned content and pending transactions
Frequently asked questions about ten_cubed
What's the maximum network size?
1,110 total reachable connections: 10 direct connections (degree 1) + 100 friends-of-friends (degree 2) + 1,000 at degree 3.
Is this suitable for large broadcast platforms?
No. By design, audience reach caps at 1,110. One-to-many platforms cannot map to ten_cubed.
How is the graph implemented?
Single PostgreSQL recursive CTE query (PG 14+) that respects each user's max_degree setting and walks outward three degrees maximum.
Can users control their own privacy settings?
Yes. Each user sets their own max_depth: privacy-first users can limit to just their 10 direct connections; others can open to all 1,110.