Subprocessors 12 Relied on by 0
+ − ⟲
Not listed by any tracked vendor.
Subprocessors 12 third parties. CSVof Runbear's subprocessors · Atom
Name Purpose Location Listed since Anthropic AI AI provider; Runbear processes user messages through OpenAI to generate AI responses. US Sep 30, 2026 Cloudflare Runbear uses Cloudflare to route and protect web traffic Cloud monitoring Sep 30, 2026 GitHub Runbear uses Github to host our code Version control Sep 30, 2026 Google Cloud Platform Cloud provider; Runbear's primary compute hosting US East Sep 30, 2026 OpenAI AI AI provider; Runbear processes user messages through Anthropic to generate AI responses. US Sep 30, 2026 Pipedream Pipedream enables Runbear agents to connect with third-party applications through managed tool integrations and workflows. It may process integration requests, responses, credentials, OAuth tokens, and related metadata.; Tool integration us-east-1 Sep 30, 2026 PostHog Runbear uses PostHog for product, event analysis Analytics Sep 30, 2026 Sentry Monitor application errors Cloud monitoring Sep 30, 2026 Slack Communication with Authorized Users in connection with the provision of the Services and support Collaboration Sep 30, 2026 Stripe Handles plan subscription and payment Finance and payments Sep 30, 2026 Supabase Cloud provider; Runbear uses Supabase as primarily store user data US East Sep 30, 2026 Vercel Engineering; Runbear is supported using resources provided by Vercel hosting. US East Sep 30, 2026
Compliance Certified Says it complies with Certifications as Runbear's trust center lists them; reports are usually shared on request (evidence )
Service status Jul 4: before our history of this status page Jul 5: before our history of this status page Jul 6: before our history of this status page Jul 7: before our history of this status page Jul 8: before our history of this status page Jul 9: before our history of this status page Jul 10: before our history of this status page Jul 11: before our history of this status page Jul 12: before our history of this status page Jul 13: before our history of this status page Jul 14: before our history of this status page Jul 15: before our history of this status page Jul 16: before our history of this status page Jul 17: before our history of this status page Jul 18: before our history of this status page Jul 19: before our history of this status page Jul 20: before our history of this status page Jul 21: before our history of this status page Jul 22: before our history of this status page Jul 23: before our history of this status page Jul 24: before our history of this status page Jul 25: before our history of this status page Jul 26: before our history of this status page Jul 27: before our history of this status page Jul 28: before our history of this status page Jul 29: before our history of this status page Jul 30: before our history of this status page Jul 31: before our history of this status page Aug 1: before our history of this status page Aug 2: before our history of this status page Aug 3: before our history of this status page Aug 4: before our history of this status page Aug 5: before our history of this status page Aug 6: before our history of this status page Aug 7: before our history of this status page Aug 8: before our history of this status page Aug 9: before our history of this status page Aug 10: before our history of this status page Aug 11: before our history of this status page Aug 12: before our history of this status page Aug 13: before our history of this status page Aug 14: before our history of this status page Aug 15: before our history of this status page Aug 16: before our history of this status page Aug 17: before our history of this status page Aug 18: before our history of this status page Aug 19: before our history of this status page Aug 20: before our history of this status page Aug 21: before our history of this status page Aug 22: before our history of this status page Aug 23: before our history of this status page Aug 24: before our history of this status page Aug 25: before our history of this status page Aug 26: 1 incident (1 major) Aug 27: no incident reported Aug 28: no incident reported Aug 29: no incident reported Aug 30: no incident reported Aug 31: no incident reported Sep 1: no incident reported Sep 2: no incident reported Sep 3: no incident reported Sep 4: no incident reported Sep 5: no incident reported Sep 6: no incident reported Sep 7: no incident reported Sep 8: no incident reported Sep 9: no incident reported Sep 10: no incident reported Sep 11: no incident reported Sep 12: no incident reported Sep 13: no incident reported Sep 14: no incident reported Sep 15: no incident reported Sep 16: no incident reported Sep 17: no incident reported Sep 18: no incident reported Sep 19: no incident reported Sep 20: no incident reported Sep 21: no incident reported Sep 22: no incident reported Sep 23: no incident reported Sep 24: no incident reported Sep 25: no incident reported Sep 26: no incident reported Sep 27: no incident reported Sep 28: no incident reported Sep 29: no incident reported Sep 30: no incident reported Oct 1: no incident reported 90 days ago today
1 incident in 36 days1 major or critical4 h 24 min typical time to resolve4 h 24 min longest majorIncidents per month 0 2 4 Aug 2026: 1 incident (1 major) · partial: our history begins Aug 26 · typical time to resolve 4 h 24 min Sep 2026: 0 incidents Oct 2026: 0 incidents Aug 2026 Sep Oct critical major minor no impact stated before or partly before our history
Components affected Component Incidents Bar Runbear API Server 1 Runbear Chat Engine 1 Runbear Main Website 1
As Runbear's status page reports its own incidents (scheduled maintenance left out), read every few hours since Aug 26, 2026 (evidence )
Changes None since tracking began.
Runbear