Content at
the edge.
Your community API isn't served from WordPress on every app open. It's cached across 12 global edge nodes — Redis-backed, instantly invalidated. Members in Lagos, London, and LA all load in milliseconds.
12
Edge regions
<50ms
Avg latency
99.99%
Uptime SLA
Redis
Cache layer
Request flow
How a cached
request works.
App opens
Your member taps the app. API requests fire for feed content, theme tokens, and navigation config.
Edge node intercepts
The request hits the nearest of 12 global edge nodes — not your WordPress server. Cache is checked in Redis.
Cache hit — instant serve
Cached content returns in <50ms. No PHP execution. No database query. No waiting.
Cache miss — revalidation
On a miss, the edge fetches from your WordPress origin, stores in Redis, and responds. Future requests are served from cache.
Magic Containers + Redis — not WordPress transients
The edge layer runs on Magic Containers — edge compute that executes cache logic at each PoP. Redis stores cached API responses with TTLs tuned per content type. Your WordPress site only receives traffic for writes and cache misses — typically an 80–95% reduction in origin load.
Coverage
Everything your
app needs, cached.
Every high-frequency API call your app makes on open is served from the edge — not round-tripped through your WordPress host.
Member feed
Activity feeds, group posts, and forum threads cached at the edge — served fresh without hitting your WordPress database on every open.
Theme tokens
Colors, typography, spacing, border radii, and component-level design tokens. Every user gets your brand in milliseconds.
Navigation config
Tab structure, menu items, and feature flags. App nav loads instantly — no round-trip to your server required.
Course content
LearnDash lesson lists, module trees, and course metadata. Students see their curriculum the moment the app opens.
Notifications
Notification centre content and unread counts served from the nearest PoP — no latency spikes on app launch.
Marketplace data
Product listings, pricing, and availability cached globally. Shop screens load without waiting for WooCommerce queries.
Performance
The numbers.
The difference between an app that feels fast and one that feels slow is usually the first 300ms. The edge closes that gap.
Compatibility
Built for your
community stack.
BuddyBoss Platform
- Member profiles & activity
- Groups & group feeds
- Social learning + LearnDash
- Forums (bbPress)
- Media gallery
Fluent Community
- Spaces & space feeds
- Member directories
- Post & comment feeds
- Notification centre
- User badges
BuddyPress
- Activity streams
- Member profiles
- Friend connections
- Groups
- Private messaging
FAQ
Questions.
API responses from your community plugin (BuddyBoss, Fluent Community, BuddyPress) — member feeds, group content, courses, notifications. Plus all app configuration: theme tokens, navigation structure, and feature flags. Static assets (images, fonts) are handled separately by the CDN.
The Blockli companion plugin sends a webhook to the edge layer whenever content is published, updated, or deleted on your WordPress site. The relevant cache keys are invalidated and the next request pulls fresh data from origin. Most content is re-cached within seconds of a change.
Yes — for cache misses and for write operations (likes, comments, enrollments, purchases). Reads are served from cache. The result is typically an 80–95% reduction in origin request volume.
Magic Containers is the edge compute layer that runs the Blockli cache proxy. It executes request routing logic, Redis lookups, and cache invalidation webhooks at each PoP — without any server you need to manage.
The base Blockli platform includes a standard CDN for static assets. The Global Edge API — Redis-backed dynamic content caching across all 12 regions — is a one-time $99 add-on, set up once during onboarding.
BuddyBoss Platform, Fluent Community, and BuddyPress are fully supported. The edge layer understands the REST API shape of each plugin and caches intelligently by endpoint, user scope, and group membership.
$99 — set up once.
The Global Edge API is a one-time add-on. We configure the edge layer, Redis cache, and webhook invalidation for your site during onboarding. No ongoing fees beyond your plan.