Bifrost

Systems & Integrations

What is connected, enabled, missing, or failing — and how to fix it.

API Connectivity

Frontend ↔ backend wiring — the first thing to check when data is missing.
checking…
frontend environmentproduction
api base urlhttps://bifrost-asgard-api.fly.dev/api/v1
frontend origin
round-trip latency
last successful api callnone recorded
last failed api callnone recorded
backend environment
backend version / commitnot exposed
backend uptime
db latency (server-side)
cors origins
auth enforcement / rate limit

Database

Supabase / Postgres connection, schema revision, and table-by-table row counts.
unknown

Loading…

Feature Flags

Platform doctrine: everything defaults OFF; sending always requires human approval.

Loading…

Connectors

Key presence and reachability only — secrets never leave the backend.

Loading…

Opportunity sources

Per-source market ingestion: status, last sync, ingested / rejected / qualified.

Loading…

Runtime

Intelligence cycle, approvals, and spend posture.

Loading…

Automation & Make.com

Gmail/calendar intake + digest scenarios — estimated credit spend, junk rejections, caps. Secrets never shown.

Loading…

Diagnostics

All actions are safe: read-only probes; the cycle runs dry — no sends, no paid API calls.