What is done, what is next, what is only an idea.
No dates. A dated roadmap from a one-person company is a promise broken in public.
In progress
- in progressbilling
Plans and usage in the dashboard
Your plan and usage in the dashboard, and upgrades without an email.
- in progressbusiness-live
Review and QA for Business
PR review, dependency and secret scanning and QA flows are built, and go live with the first Business customers.
Shipped
Ingest for the open-source SDKs
resolvedEnvelope and store endpoints, verified end to end with the PHP and Node SDKs.
Grouping and regressions
resolvedFingerprints, in-app frames, type and message. A resolved issue that fires again is a regression.
Tracing and logs
resolvedTransactions, spans and structured logs, linked to the errors they belong to.
Uptime and cron monitoring
resolvedHTTP checks and cron check-ins. A failure opens an issue; recovery resolves it.
Issue and metric alerts
resolvedIssue rules plus thresholds and anomalies on error count, failure rate and p95.
Source maps and releases
resolvedDebug-ID bundles over the sentry-cli protocol, resolved before grouping.
The Parsemend CLI
resolvedBrowser sign-in, and your issues in the terminal.
MCP server for your coding agent
resolvedYour issues for Claude Code, Codex, Cursor or any MCP client, with no repository access.
Self-serve sign-up
resolvedRegister, create a project, copy its DSN.
Exploring
Not commitments.
Session replay
unresolvedA lot of work for something an agent rarely needs.
Profiling
unresolvedUseful, expensive, and not on the path to a fix.
Performance aggregates
unresolvedGrouping by any tag over any window. Waits on the query layer.
Analytics query layer
unresolvedArbitrary queries over event attributes, which needs a column store.
If one of these is why you cannot use Parsemend, say so at hello@parsemend.com.