Status & reliability
Because TribeBlend runs on the desktop, hosted-service outages have a smaller blast radius. Here is how each piece behaves and how we handle incidents.
Reliability model
This page explains how each dependency behaves and how we handle incidents. It is not a live monitor; during an incident we update this page and email organization admins directly.Desktop-first by design
TribeBlend keeps the app shell, local settings, business context, and in-progress review state on the analyst's device. Live Databricks queries, sign-in, licensing checks, and governed write-back use their respective upstream services and resume automatically once connectivity returns.
Components
Desktop application
Runs on the analyst's device. Local UI, business context, and in-progress review state stay on the machine; live warehouse work depends on the user's Databricks connectivity.
Local device
Website & dashboard
Marketing site, account dashboard, and admin controls.
Cloudflare Workers
Authentication & SSO
Login, MFA, SAML/OIDC SSO, and SCIM provisioning.
Cloudflare Workers, Turso
Licensing
License activation and heartbeat validation.
Keygen.sh
Sales & scheduling
Contact form, demo booking, and lead routing.
HubSpot, Cal.com
During an incident
We notify organization admins by email and update this page with scope, impact, and resolution. For urgent issues, reach us through the contact page. Security vulnerabilities have a dedicated channel in security.txt.