Product Roadmap

Where ErrorLens is going — and where it has been

This roadmap reflects current thinking. Priorities shift based on customer feedback. If you want to influence what we build next, talk to us →

✓ SHIPPED

✓Code patch suggestions — before/after diffs from stack traces (Python, Java, JS, Go, C#, Ruby, PHP, TypeScript)
✓Team history and collaboration — shared workspace history with filters, search, tags, and analyst tracking
✓Enterprise SSO and SAML 2.0 — Okta, Azure AD, Google Workspace with JIT provisioning and SCIM sync
✓REST API access — full v1 API with bearer token auth for all paid plans
✓Occurrence counting and severity ranking — exact per-error counts, sorted Critical to Low
✓Expanded plan lineup — Starter, Pro, Team, Enterprise with annual billing and $0.06/analysis overage
✓Structured JSON log parser — Winston, Pino, structlog, Zap, Logrus, CloudWatch, ECS, GCP Logging
✓Slack alert webhooks — no-code setup, per-channel routing, severity threshold controls
✓VS Code Extension — right-click analysis on .log files, inline results panel
✓GitHub Actions — official action for CI/CD pipelines, PR comments, merge blocking on critical errors
✓Connectors and SDKs — Node.js, Python, Docker sidecar, New Relic, Sentry, Datadog, PagerDuty packages
✓Image and screenshot analysis — PNG, JPEG, WebP error screenshots via AI vision

✓ RECENTLY SHIPPED

Error Trend Dashboards

Visual dashboards showing error frequency over time, severity distribution by environment, and top error types — now live.

What's included

→Daily error frequency bar chart (last 14 days)
→Severity distribution breakdown
→Environment breakdown (prod/staging/dev)
→Top error types ranked by occurrences

Jira and Linear Integration

One-click issue creation from any error analysis, pre-populated with error type, severity, root cause, and environment.

What's included

→Auto-populates title, description, environment
→Supports both Jira Cloud and Linear
→Configurable project key and team defaults
→Credentials stored locally

Custom Severity Rules

Define workspace-level severity overrides — e.g., any OutOfMemoryError is always Critical. Applied before AI classification.

What's included

→Rule builder UI in Settings
→Match on error type pattern
→Override severity to critical / high / medium / low
→Instant add/remove with preview

Multi-Environment Support

Label analyses by environment — production, staging, development. Filter history and see distribution in Trends.

What's included

→Environment selector on every analysis
→Colored badge in History
→Filter by environment
→Environment breakdown chart in Trends

◈ PLANNED

◈

Datadog / PagerDuty bi-directional integration

Trigger ErrorLens analysis from Datadog monitor alerts and PagerDuty incidents; analysis results post back to the incident timeline.

◈

Bulk history export

Export full analysis history as CSV or JSON — error types, severity, counts, timestamps. Useful for compliance and audit.

◈

SCIM user provisioning (Enterprise)

Full SCIM 2.0 support for automatic user provisioning and deprovisioning through your identity provider.

◈

Per-environment usage quotas

Separate monthly analysis quotas per environment on Team and Enterprise plans.

◌ EXPLORING

◌

Real-time log streaming

Stream live log output to ErrorLens and receive analysis results as new errors appear — sub-second latency via Kafka, Kinesis, Pub/Sub.

◌

Automated PR comments (GitHub App)

A single GitHub App install watches all repositories and comments on PRs when errors are detected in CI runs — no workflow config needed.

◌

Mobile app (iOS & Android)

View analysis history, receive push notifications for critical findings, and approve suggested code fixes from your phone.

◌

Self-hosted / air-gapped deployment

Run ErrorLens entirely within your own infrastructure via Docker + Helm. No log content ever leaves your network. Enterprise-only.

◌

Browser DevTools extension

Detect console errors on any page and analyze them with one click directly from the DevTools console.