Push Notifications: How Delivery Actually Works

The delivery chain Every push goes through the same path, and a fault at any link looks identical to the member (nothing arrives). Know the chain before you debug: Device registers. The installed a...

Scheduled Jobs & Background Processing

How scheduled work runs Recurring platform work is driven by pg_cron jobs in the database. A job does not contain a URL or a key: it calls public.invoke_edge_function(fn, body), which reads the tar...

Storage Buckets & Nightly Backups

Where files live Uploaded files — gym media, contract assets, member progress photos, maintenance photos and videos, SAR packages and the rest — are held in storage buckets rather than in the datab...

Environments & the Deployment Pipeline

Two environments Development and production are separate databases, separate storage and separate edge functions. Never assume a change you can see is live for customers, and never test a destructi...

Mobile App Releases (iOS & Android)

What the mobile apps are The member and staff apps are the same web application wrapped with Capacitor and shipped as native builds. The app identifier is app.bliply.gym. Most product changes reach...

AI Usage, Prompts & Monitoring

How AI is wired AI features call Google Gemini directly using our own API key. We deliberately do not route model traffic through third-party gateways, so behaviour and cost stay predictable and th...