LogoLogo
HomePlatform IntegrationsDownloadsLogin
  • Welcome
  • šŸ“ŒIntroduction
    • Getting Started
      • Signing Up
      • Creating a Database
      • Platform Integrations
        • šŸ’»Desktop
          • BugSplat Crash Reporting Library for Windows (Native C++)
            • Full Memory Dumps
            • Windows (Native C++) Dependencies
          • Windows (.NET Framework)
          • macOS
          • Linux
        • šŸ”€Cross-Platform
          • .NET Standard
          • Breakpad (Deprecated)
          • Crashpad
            • How to Build Google Crashpad
          • Deno
          • Electron
          • Java
          • Node.js
          • Python
          • Qt
        • šŸŽ®Game Development
          • CRYENGINE
          • Nintendo Switch
          • PlayStation
          • Unreal Engine
            • Unreal Engine Plugin
          • Unity
          • Xbox
        • šŸ“±Mobile
          • Android
          • Ionic
          • iOS
          • React Native
        • šŸ•øļøWeb
          • Angular
          • JavaScript
          • React
          • Vue
        • āŒ›Downloads
      • Platform Samples
        • BugSplatTester (iOS)
        • BugSplatTester (macOS)
        • myConsoleCrasher (C++)
          • Address Sanitizer Reports
        • my-android-crasher
        • my-angular-crasher
        • my-electron-crasher
        • my-java-crasher
        • my-node-crasher
        • my-qt-crasher
        • my-react-crasher
        • my-unity-crasher
        • my-unreal-crasher
      • Inviting Team Members
      • Importing Crashes
      • Troubleshooting
      • Quickly Submitting Your First Crash in Under 5 Minutes
    • Development
      • Using the App
      • Symbol Files
        • Common Symbols
        • How to Manually Upload Symbols
        • Source Maps
        • Symbol Servers
        • Working with Symbol Files in Windows Environments
      • Searching
        • Table Filtering
        • Table Grouping
      • Grouping Crashes
      • Commenting
      • Integrations and Third Party Tools
        • Configurable Alerts
          • Slack
          • Microsoft Teams
          • Discord
          • Email
          • Webhook
        • Issue Trackers
          • Azure DevOps
          • Favro
          • Jira
          • GitHub Issues
          • GitLab
          • Monday.com
          • YouTrack
          • Auto-Creating Defects from BugSplat Databases in Attached Third-Party Issue Trackers
      • API
        • Web Application Endpoints
          • Charting
          • Company
          • Crash
          • Crashes
          • Crash Groups
          • Databases
          • Defect
          • Events
          • Import/Migrate
          • Support Response
          • User (GDPR)
          • Users
          • Versions
        • Crash Post Endpoints
        • OAuth2
        • Defect Tracker Options
        • Paging, Filtering, and Grouping
        • Platform Specific API's
          • C++ Native API
          • .NET API
    • Production
      • Versions
      • šŸ†•Regression Alerts
      • Security and Compliance
        • Security Program
        • BugSplat Security Program Inquirys
        • SOC 2
        • GDPR & UK GDPR Compliance
        • Avoid Collecting Personally Identifiable Information (PII)
        • Crash Expiry
        • Terms
        • Privacy Policy
      • Support Responses
      • BugSplat Status
  • šŸŽEducation
    • BugSplat Terminology
    • How-Tos
      • Creating Defects
      • Contacting End-Users
      • Crash Dialog Branding
      • Reprocess Crashes
      • Batch Reprocess Crashes
      • Using the Crash Attribute Feature
      • Send Feedback
      • Remove Crashes
    • Videos
      • BugSplat Product Walkthrough
    • FAQs
      • How Do I Upload Crashes with Python?
      • How Do I Remove Symbol Files?
      • Crash details 'Active Thread'
      • How long does it take to process a crash?
      • How BugSplat handles large crash volumes
      • How Does Crash Rate Limiting Work?
      • Add Custom Branding to Support Response
      • Finding Missing Reports
      • Using Dark Mode
      • What If My App or Game Grows Quickly?
      • Does BugSplat have an effect on application performance?
      • Manually Upload Crash Reports to BugSplat
      • How to configure proxy settings in BugSplat
      • Using BugSplat's public database
      • How to Upload Symbol Files with Symbol-Upload
      • Using SendPdbs to Automatically Upload Symbol Files
      • Managing Symbol Space
      • Why Group Crashes?
      • Uploading third-party DLLs without PDB files
      • Localized Support Responses for Windows C++, .NET, and macOS
      • BugSplat application uptime data
        • What are the upload size considerations with BugSplat accounts.
      • Is an application's source code safe when using BugSplat?
      • How to get correct callstacks with BugSplat in Steam
      • What is a crash reporter?
      • Common End-User Questions
        • Missing BugSplat.dll
        • What should I do if I get a BugSplat?
        • What is BsSndRpt.exe?
        • My software just crashed. Should I contact BugSplat for help?
  • šŸ¢Administration
    • Billing
      • Free Trial Overview
      • Plans and Billing Overview
      • How to Sign Up for a BugSplat Plan
      • Viewing Account Usage
      • Upgrading, Changing, or Canceling Your Plan
        • Upgrading or Downgrading Your Plan
        • Adding Additional Crashes and Storage Space
        • Updating Credit Card and Billing Information and Viewing Billing History
        • Updating Tax and VAT Information
        • Canceling Your Plan
      • Free and Discounted Plans
        • Free Plan Overview
        • Free Crash Reporting for Indie Game Development
        • Education
        • Open-Source
        • Good Causes
      • Plans, Upgrades, and Payments FAQ
        • Fair-Refund Policy
        • Update to Our Legacy Plans Guide
        • Updates to BugSplat Pricing Plans - March 2024
        • Using Coupons and Promotions at BugSplat
        • What is 'High Volume Fractional Crash Processing'?
    • Account
      • Migrating Databases
      • Deleting Databases
      • Deleting a Company Account
      • Changing Company Name
    • User Management
      • User Permissions
      • Deleting a User
      • Requesting Access
      • Login Page and Options
      • Password Settings and Reset Options
        • Required Password Reset - August 4th, 2023
      • Single Sign-On (SSO)
      • Multi-Factor Authentication (MFA)
      • Enforce MFA
      • Adding New Users in Companies with Multiple Databases
    • Contact us
  • šŸ›About
    • What is BugSplat?
    • Why BugSplat?
    • Who is BugSplat?
      • Our Values
      • Charitable Giving
      • Brand Guidelines
    • Partnerships
    • Misc
      • Promotions
        • March 2024 - Game Developer Free Months of Service
      • Giveaways
        • April 8 - April 22, 2025
        • Feb 18 - March 17, 2025
        • Jan 15 - Feb 13, 2025
        • December 19-29, 2024
        • November 21–28, 2024
        • October 17-24th, 2024
        • September 19-26th, 2024
        • July 18 - July 23, 2024
        • April 18 - May 12, 2024
        • March 18 - April 03, 2024
        • November 15-30, 2023
        • October 9-23, 2023
  • šŸ”€Changelog
    • Changelog
Powered by GitBook
On this page
  • Our Story
  • Back in 2004, if you wanted a crash reporter, you had to build it.
  • Over the years, BugSplat has grown significantly.

Was this helpful?

  1. About

Who is BugSplat?

Our Story

BugSplat started in 2004 as an informal side project by David Plunkett and a couple of friends.

Dave and the gang had built and maintained crash reporting tools at much larger software companies in their previous roles. This was an experience that led them to three big takeaways:

  1. Crash reporting was a nearly magical tool for finding and fixing crash defects. \

  2. Software is better and more stable with crash reporting—so everyone should use it.\

  3. Building and supporting a crash reporter was a lot of work.\

Back in 2004, if you wanted a crash reporter, you had to build it.

Back in the day, there wasn't a self-service crash reporting tool available on the open market. If you or your team wanted to buy a crash reporter your only option was a tool from Microsoft that - instead of collecting crash data and giving your team access to that valuable knowledge - sent the crash data directly to Microsoft.

To us that kind of missed the point, we need access to crash data in order to fix crashes and improve application stability. What good is a third-party getting that data?

This meant if you wanted access to application crash data you had to build and maintain a crash reporter in-house.

For larger companies, this wasn't an issue. The company that Dave worked for could afford to throw a team of six developers full-time at building and maintaining a crash reporter.

What if you weren't a billion-dollar company? How could you dedicate six or eight people to doing this?

Even if you could afford to build a crash reporter, why spend the time, energy, and resources scaling up a new tool for the first time? Wouldn’t it be better to use a market-tested tool supported by experts?

Sensing market and developer need—the team started building and expanding on the BugSplat project in 2003.

Nights and weekends were dedicated to development as the team fell quickly into the heady experience of building something new, fun, and exciting.

In 2004, BugSplat was launched with our friends at Sketchup being the first customer.

Over the years, BugSplat has grown significantly.

Since we launched our business in 2004 we have seen the industry grow and change.

Many companies have entered the market in that time - some were free options from tech giants, and others were VC-backed startups raising millions to try and do the same things as BugSplat.

Through it all we’ve maintained a laser focus on providing our users with the best possible data on application crashes, keeping our application easy to use, building the features important to our users, and providing excellent customer support.

Despite the industry changes we’re still 100% self-funded and have never accepted outside investment. That means we only answer to you, our customer. We're lean, profitable, growing, and supporting ourselves and our families through this business.

Today BugSplat helps developers track and fix over 500 million crashes on around 350 million computers, tablets, consoles, and phones every year.

We know that we have an amazing gig with BugSplat. It’s a lot of work, sure, but we work every day on interesting problems with great partners. We’re a fully remote company that emphasizes flexibility, self-responsibility, and personal and professional exploration.

All of this is to say...

Cheers,

PreviousWhy BugSplat?NextOur Values

Last updated 1 year ago

Was this helpful?

If you're a BugSplat user, thank you for making this happen. If you're not a user yet, please consider .

šŸ›
signing up