From the first error to a verified fix
Buglapse looks at every occurrence of an error at once: the steps they share, a representative example and the cause — then takes it to a pull request and, after the release, checks that the fix worked.
Free plan: up to 2 projects and 5,000 errors a month. No card required.
src/checkout/useCart.ts:48
Coupon not found: coupon is undefined and reading coupon.id throws.
Setup
Drop in a script tag or install the SDK. Events are batched to your project endpoint and authorized by the key in the project DSN — no secret keys in your code.
Sign up for free and create a project — its DSN is ready right away in Settings → SDK.
Paste the script tag or call init() with the project DSN. Only the integrations you enable are loaded.
Errors are grouped into issues with a readable stack trace, breadcrumbs, release and user.
index.html
<script
src="https://app.buglapse.com/cdn/YOUR_PROJECT_TOKEN/buglapse.min.js"
async
></script>The project key is already in the URL. Toggle integrations in Settings → SDK — no redeploy needed.
All in one
Errors, logs, traces, sessions, replays, releases and uptime share one context — no separate products to stitch together.
An error that happened 10,000 times is one row with a counter. Custom fingerprints, short keys like WEB-42, assign, resolve and merge, search with filters. A resolved issue reopens by itself if the error comes back.
Learn more: Exceptions & IssuesCrash-free sessions and users for every release: see at once whether a deploy made things worse, how many visits an issue touched, and get alerted when the share drops.
Learn more: Release HealthBuglapse checks your URLs and gRPC services from its own servers, down to once a minute — no SDK needed. A few failed checks in a row open an incident, and the team is alerted right away.
Learn more: Uptime monitoringSee which deploy brought new issues: new issues per release, counters and the commit ref.
Learn more: ReleasesMinified stack traces turn back into your source files and lines. Upload from CI or with the bundler plugin, bound to a release.
Learn more: Source mapslog.info, warn and error right next to errors and traces. Console capture, search and trace links.
Learn more: LogsA waterfall of spans: pageload and navigation automatically, fetch and HTTP spans, distributed across browser and Node.
Learn more: TracingSee what the user saw before the error. Full session or on-error mode, inputs masked by default.
Learn more: Session ReplayEvery event is tied to a real user: how many people an error hit and each user's history.
Learn more: UsersOverview
Every project opens on a page of widgets: events, issues that need attention, releases, sessions, uptime, replays, alerts and Autofix runs. Keep what your team looks at every day and drop the rest.
A list, a top three, a counter or a chart — full width or half of it. Pick the one that fits the space.
Move widgets around and add new ones right where you need them. Every change is saved at once.
The whole team sees the same overview, and the default set is one click away.
A text widget for runbook links, agreements and the context numbers do not carry.
Widgets are on every plan; which ones you can add follows the signals your plan includes.
Widgets · click to add or remove
Events
Needs attention
Sessions
Releases
Uptime
Issues
Buglapse groups events, resolves the stack and shows what led to the error — you know where to look before you open the editor.
Identical errors collapse into one issue with Events, Users, First and Last seen. Tune the fingerprint when the default is not enough.
Source maps turn minified frames back into your code, down to the line and column.
Clicks, navigation, fetch requests and console output before the error — and the steps the issue’s events share on the way to it.
Release, environment, browser, OS, device and the affected user on every event.
Autofix · AI agent
The agent reads your GitHub or GitLab repository, finds the root cause, plans the fix and opens a draft pull request — or stops at the diagnosis when that is all you need.
Step 1
Reads the stack trace, breadcrumbs and the code around the failing line.
Step 2
Explains what to change and why before touching anything.
Step 3
Writes the patch — the full diff is visible in Buglapse.
Step 4
Opens a draft pull request on a new branch of your repository.
Runs on your own AI provider key
You pay the provider directly. Buglapse doesn't charge for tokens.
Reads code, never runs it
The agent only reads the repository — it doesn't execute anything.
Always a draft PR on a new branch
It never pushes to existing branches. If CI fails, it repairs its own change.
Full step log and diff
Every step the agent took and every changed line stay in Buglapse.
Available on Pro and Team — with a connected repository and your own AI provider key.
coupons.find() returns undefined for an unknown code, and applyCoupon reads coupon.id without a check.
Guard the missing coupon, throw CouponNotFoundError and show the message in CheckoutForm.
1 file changed in src/checkout.
Draft pull request #128 opened on a new branch.
fix(checkout): guard missing coupon in applyCoupon
Buglapse-autofix wants to merge 1 commit into main from buglapse/autofix-web-42
MCP server
Ask Claude Code or Cursor about production right in the IDE — the assistant reads issues, traces and logs through the Buglapse MCP server.
claude mcp add --transport http buglapse https://app.buglapse.com/mcp \
--header "Authorization: Bearer YOUR_PERSONAL_TOKEN"What's the most frequent error in production this week?
buglapse.list_issues(environment: "production", period: "7d", sort: "events")
found 5 unresolved issues
buglapse.get_issue(key: "WEB-42")
stack trace and 1,284 events loaded
The most frequent one is WEB-42 — TypeError — with 1,284 events from 312 users since release web@2.14.0.
It's thrown at src/checkout/useCart.ts:48: coupons.find() returns undefined for an unknown coupon code, and coupon.id is read without a check. Want me to add a guard and a test?
Integrations & SDK
Organization-level integrations power Autofix; modular SDKs keep your bundle small — every integration has its own docs.
GitHub App: repository access and pull requests for Autofix.
GitLab.com or self-managed: repository access and merge requests for Autofix.
Anthropic: Autofix runs on your Claude API key.
Or run Autofix on your OpenAI API key.
Any Chat Completions server: OpenRouter, DeepSeek, Groq, Ollama, vLLM.
Uploads source maps during the build: Vite, webpack, Rollup, Rspack, esbuild.
@buglapse/bundler-plugin
Browser SDK for any framework.
@buglapse/browser
SDK for your Node.js server.
@buglapse/node
Five event types, one endpoint, sent in batches.
Enable the Sentry integration and point the official SDK's DSN at Buglapse — errors, transactions, logs and replays arrive without changing your code.
Need something specific? Write your own integration
Teams
Organizations, projects and plain roles — with volume and budget under control at the organization level.
An organization holds all your projects; the plan and quotas live at the organization level.
Flat roles: an owner and members. No permission matrix to maintain.
Hand an issue to a teammate — or to the AI agent.
Monthly quotas per event type, shared by the whole organization. Under a spike, sampling keeps the first events of every issue instead of cutting off.
How long errors, logs, traces, replays and sessions are kept depends on the plan.
Accept events only from your own domains and drop the rest.
New and regressed issues, spikes, quotas and downtime — batched into one message every few minutes; a monitor going down is sent at once.
teams.items.privacy.text
Projects
Members
Monthly quotas
ProAllowed origins
Security
Monitoring that doesn't depend on foreign services: servers, contract and billing are all in Russia.
Servers and databases are in Moscow, with no cross-border transfer. We process your users' data on your behalf under Russia's Federal Law 152-FZ.
Passwords, tokens, card numbers and keys are replaced on the server before the event is even queued, so they're never stored. Add your own fields and hash IP addresses; in replays the SDK masks input.
{ "authorization": "[Filtered]", "card_number": "[Filtered]", "api_token": "[Filtered]", "user.ip": "h:9f2c41…" }
Data travels over TLS only; passwords and access tokens are stored as hashes.
Ingestion is separate from the dashboard and runs through a queue. Under overload, traces and replays are dropped first while errors keep coming in.
We keep backups. Deleted data disappears from them too, within 30 days at most.
Autofix uses the provider key you connected yourself. Nothing connected — nothing leaves.
The SDKs are MIT-licensed: the code that runs inside your app is open to review.
Companies pay by bank transfer; closing documents are signed through electronic document exchange.
Self-hosted
When data can’t leave your infrastructure at all, Buglapse runs inside it. The same features, with install and upgrades in a single command.
curl -fsSL https://app.buglapse.com/api/self-hosted/install.sh | sudo bashPricing
Quotas are monthly and shared across the organization. Plan changes are on request — there's no online payment yet.
For side projects and trying Buglapse out.
₽0/ month
per organization
Get startedFree plan upgrade on request, anytime
For products in production: 5–10× the volume, per-minute uptime checks, assignees and API access.
₽1,990/ month
per organization
Choose ProPlan change on request
For growing teams: 5–10× the volume again, unlimited Autofix and longer retention.
₽5,990/ month
per organization
Choose TeamPlan change on request
Need more? Custom plans
Individual quotas, retention and member limits for your organization.
AI tokens are billed by your provider on your own API key — Buglapse doesn't charge for them.
| Free | Pro | Team | |
|---|---|---|---|
| Plan | |||
| Price / month | ₽0 | ₽1,990 | ₽5,990 |
| Projects | 2 | 10 | Unlimited |
| Members | 1 | 5 | 25 |
| Monthly quotas | |||
| Errors / month | 5,000 | 25,000 | 150,000 |
| Spans / month | 100,000 | 1,000,000 | 10,000,000 |
| Logs / month | 50,000 | 500,000 | 5,000,000 |
| Replays / month | 10 | 100 | 1,000 |
| Retention | |||
| Errors & issues | 14 days | 30 days | 90 days |
| Sessions (release health) | 7 days | 14 days | 90 days |
| Traces | 7 days | 14 days | 30 days |
| Logs | 7 days | 14 days | 30 days |
| Replays | 7 days | 14 days | 30 days |
| Alert history | 14 days | 30 days | 90 days |
| Uptime monitoring | |||
| Monitors | 1 | 10 | 50 |
| Shortest check interval | 10 minutes | 1 minute | 1 minute |
| Check history retention | 7 days | 14 days | 30 days |
| gRPC checks | Not included | Included | Included |
| Autofix | |||
| AI agents (Autofix) | Not included | Included | Included |
| Autofix runs / month | Not included | 30 | Unlimited |
| CI-fix attempts per run | Not included | 3 | 5 |
| Investigate (diagnosis without a pull request) | Included | Included | Included |
| Investigations / month | 10 | 100 | Unlimited |
| Features | |||
| Source maps | Included | Included | Included |
| Largest source map | 10 MB | 30 MB | 50 MB |
| Stack frames linked to your repository | Included | Included | Included |
| MCP server | Included | Included | Included |
| DSN for Sentry SDKs | Included | Included | Included |
| Custom grouping and issue merging | Not included | Included | Included |
| Custom event filters | Not included | Included | Included |
| Custom data scrubbing rules, IP hashing | Not included | Included | Included |
| Issue assignees | Not included | Included | Included |
| Export to Markdown / JSON | Included | Included | Included |
| API access with a personal token | Not included | Included | Included |
Create a project on the free plan and send your first event in a couple of minutes.
Still have questions? Email hello@buglapse.com