Sampling RUM data to control costs? 🤔 The wrong sampling method can inadvertently filter out the critical errors and rare events. Most observability tools rely on sampling. At bitdrift, we take a different approach: eliminate sampling. Instead of hoping your sampled data catches critical issues, you get: ✓ Comprehensive data from your entire user population ✓ Flexibility and control over what you collect (no query language, no app re-release) ✓ Targeted deep dives into specific devices or user segments See how bitdrift addresses the risks and limitations of traditional sampling, without surprise overages. 👇 #MobileObservability, #MobileTeams
bitdrift
Technology, Information and Internet
San Francisco, CA 1,356 followers
Welcome to the future of observability
About us
Mobile observability, radically reimagined: bitdrift flips the decades-old mobile observability paradigm on its head: log everything, intelligently choose what to store, and instantly deploy changes to your entire fleet. bitdrift exists to solve a common, frustrating, and costly problem: observability. Developers need visibility in the things that their app runs on – whether it be servers (coming soon), or mobile devices. And though there are many, many, many observability solutions out there – including highly successful public companies – most developers will tell you that observability is still the bane of their existence. Despite (or perhaps because of) it being the single biggest line item on their infrastructure bill, developers still generally don’t have the observability data they need to really understand what’s going on. And because they pay up the nose for everything they store, whether it’s useful or not, the incentive is to be highly stingy on what they log, to the detriment of their visibility and their users. bitdrift is a bit of an unusual startup in that we’ve been at this for a while. The bitdrift team used to work at Lyft, and over several years developed a comprehensive internal solution to the problems outlined above. It supported 50+ million devices at Lyft and saved the company 10s of millions of dollars per year. We spun out as an independent company in 2023 with Lyft as our first marquee customer, and raised $15M from leading investors like Amplify Partners.
- Website
-
https://bitdrift.io
External link for bitdrift
- Industry
- Technology, Information and Internet
- Company size
- 2-10 employees
- Headquarters
- San Francisco, CA
- Type
- Privately Held
- Founded
- 2023
- Specialties
- observability, mobile, and mobile observability
Locations
-
Primary
Get directions
San Francisco, CA, US
-
Get directions
New York, NY, US
-
Get directions
Boise, ID, US
Employees at bitdrift
Updates
-
Our solution architect on why mobile observability requires a completely different approach.
Reason #3 in my “10 reasons not to use bitdrift” series: 🖥️ You like tools that were built for server apps 👇 There’s a better model for mobile observability https://lnkd.in/e78NQtNQ #MobileObservability #DevTools #DeveloperExperience #bitdrift
-
🎙️ New episode alert! Hear Ty Smith, Principal Engineer at Uber, tell the story of how he got into engineering, walk through his epic career (including almost 10 years at Uber so far), and discuss the future of software engineering, including AI-driven development, the coming validation/observability crunch, and how the “software engineer” role itself is evolving. Check it out here, or wherever you get your podcasts! https://lnkd.in/e7YMEGit
-
We loved working with Ranjith Kumar and the Zuper team on this case study! It digs into how they went from relying on crash and analytics tools that were only showing part of the story to full on-device visibility with bitdrift. Now, their team can get a birds-eye view of what's happening across complex mobile workflows, uncover issues before they impact users, and quickly debug problems in production. Link to the full case study in the comments 👇
-
-
What happens when your crash & analytics tools only tell half the story? For the team at Zuper, that was a daily frustration. Their field service app handles millions of work orders in industries like HVAC, security, and construction, capturing photos, videos, and heavy media on every job... But piecing together user issues felt like detective work, jumping between tools & trying to uncover hidden context. At some point, “good enough” observability just wasn’t good enough anymore. Zuper wanted: - Full on-device context, not just stack traces - Proactive visibility into performance issues - One central place to understand what users experienced, without stitching data together manually That’s when the team found bitdrift and things started to click. They uncovered issues like crashes caused by device storage and battery constraints, problems that had existed all along... but were invisible in their previous setup. And now when something breaks? Engineers get real-time Slack alerts with the context they need to debug immediately. If you’re still relying on crash reports, breadcrumbs, and dashboards that leave you guessing, this is worth a read. Read the full case study here: https://lnkd.in/erH8uf6H
-
We're starting off the new year with a brand new feature: dynamic Time To Live (TTL) for workflows! But let's back up for a second. When we talk about "workflows" on a mobile observability platform, what do we mean? On bitdrift, a workflow is the visual language you use to define what sequence of events to look for to kick off certain actions. For example: “Wait for the user to view the check out screen, then if the user leaves the checkout screen or 15s has passed without a checkout, increment a counter and dump a full session with session replay.” Workflows let you encode detailed conditions to match on and unlock extremely pointed debugging - all without sending heaps of useless data to the backend. Where most vendors are happy to charge you for data you don't use, we think that model creates misalignment between the user and the tool. Instead, our interests are aligned with the customer: ingest only the data that is needed and nothing more. TTLs provide the foundation to do just that. Read more about our support for workflow TTLs here 👇 https://lnkd.in/e7mw45bh
-
Looking for something exciting to kick off the new year? Come work at bitdrift!
👋 Happy new year all! We are excited to start expanding the engineering team at bitdrift. This is an opportunity to work with our small but mighty team on truly novel technology in the observability space. We are already working with some of the largest companies in the world and are super excited about what 2026 will bring. We are looking for: - Systems engineers: This is a nearly 100% Rust 🦀 focused role where you will be building the infrastructure/systems that power our real-time observability solution. You will also have the opportunity to work on the core Rust code that powers our SDK. - Mobile SDK engineers: We are looking for iOS/Android engineers that want to work on making our our SDKs truly best in class in the mobile observability and issue reporting space. This spans both the native SDKs as well as React Native, Flutter, Unity, and more. The dynamic nature of our SDKs make the engineering challenges both substantial and interesting. We have no end of challenging and novel problems to solve and a product that is resonating. I promise you will not be bored. Feel free to each out to me to informally chat about the roles. Full job links in the comments. 🚀
-
bitdrift reposted this
Reason #2 in my “10 reasons not to use bitdrift” series: 🪵 You like paying for logs you’ll never read 👇 There’s a better model for mobile observability https://lnkd.in/edzsqS2k #MobileObservability #DevTools #DeveloperExperience #bitdrift