MFE Debugger
Debugs micro frontend architectures by correlating host and remote failures across releases and authentication.
26 linking domains
Emerging
- For
- Teams debugging issues in micro frontend architectures across host and remote applications
- Price
- Price not readpricing page, read 2026-09-19
- Activity
- Activity not read yet
- Company
- founding year not on record
- Correlate runtime failures between host, remotes, and user navigation flows
- Investigate authentication token and contract mismatches causing handshake failures
- Identify which release introduced a regression or caused service degradation
- #25
Weights & Biases
Tracks machine learning experiments, manages models and datasets, and monitors AI applications in production.
21.2kMaintainedFrom $60/mo - #55
OneUptime
Monitors infrastructure and applications, detects incidents in seconds, pages on-call engineers, and opens fix pull requests.
221kActiveFrom $22/mo2020 - #107
True Watch
Monitors applications, infrastructure, and AI workloads with correlated telemetry and AI-assisted diagnostics.
183ActivePay per use - #111
OpenObserve
Ingests and correlates logs, metrics, and traces across infrastructure layers for incident investigation and root cause analysis.
4.6kActiveFrom $0.50 per use2022 - #114
Respan
Routes LLM requests through one gateway to reach multiple models with observability, caching, and evaluations.
1.1kActiveFrom $199/mo2024 - #116
Motadata
Unified observability and IT service management platform combining infrastructure monitoring, application performance, and incident management.
18.5kActive—
What is MFE Debugger?
Debugs micro frontend architectures by correlating host and remote failures across releases and authentication.
Who is MFE Debugger for?
Teams debugging issues in micro frontend architectures across host and remote applications
Do people use MFE Debugger?
Emerging.
What are alternatives to MFE Debugger?
In Developer tools, by use: Weights & Biases, OneUptime, True Watch, OpenObserve, Respan, Motadata.
How we read a tool
No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.
- Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
- Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
- Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
- The line and the use cases are written by us from the homepage, one row at a time, and refused when they repeat the vendor's marketing.
How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.