14 ms·
Show HN: We’re open-sourcing our session replay tool
Hey HN! We’re open-sourcing highlight.io (https://github.com/highlight/highlight https://github.com/highlight/highlight), a session replay and error monitoring tool. Highlight.io gives you a high-precision video-like replay of what users are doing when an error or exception occurs in your web app, along with a full-fledged error monitoring experience (similar to bugsnag, rollbar, etc..).
The main value prop of highlight.io is that we help you understand the full context surrounding an error and allow you to drill down to the code path that a user invoked (i.e user clicked button X, sent network request Y, and backend code Z was executed). Some of our customers compare this to a “web debugger” of sorts. A picture of what this looks like in our app is here [1].
For some background, when we worked at our previous companies as engineers, we encountered hard-to-reproduce issues spanning across both the frontend and backend. The main issues were (1) if a customer complained about a problem, it was hard to reproduce the issue without asking for a screen-share or jumping on a video call; and (2) when viewing errors caught by tools like BugSnag or Rollbar, understanding the triggered code path required stitching together logs, errors, and trace; all from different sources.
Highlight.io is completely open source and written in Go and Typescript. To build the replay capability, we use an open source project called rrweb [2] and have worked closely with their team to add support for features like canvas recording, shadow dom recording, and more [3]. Beyond that, we use the OpenTelemetry spec for our SDKs [4], which has made it pretty straight forward to support several languages, even with our small 4-person engineering team!
Our product is completely self-serve at app.highlight.io. Installing it is as easy as a npm/yarn import and installing the backend sdk of your choosing. In addition, given the privacy-centric nature of session replay, we also offer the option to self-host [5].
Highlight.io currently makes money off of our hosted offering, and our self-hosted deployment is completely free. We’re also toying with the idea of an “enterprise” self-hosted deployment, similar to gitlab’s billing model, and thoughts from the community on this front would be appreciated!
And as far as what’s next for us: Our customers are asking to render logs and traces on a highlight.io session (and vice versa), and we’re excited to be going deeper into a developer’s debugging stack. The long term goal is to build a platform that connects replay, errors, logs and more so that engineers can “playback” the full state of a web application.
Overall, we’re quite new to the open source scene and would love the HN community to share their feedback on what we’re building. If anyone has opinions on where we’re going, or what they’d like to see in an open source monitoring product, we’re all ears.
Check us out at highlight.io and at github.com/highlight/highlight to give us a shot.
[1]: https://www.highlight.io/docs/getting-started/frontend-backend-mapping https://www.highlight.io/docs/getting-started/frontend-backe...
[2]: https://github.com/rrweb-io/rrweb https://github.com/rrweb-io/rrweb
[3]: https://highlight.io/docs/general/product-features/session-replay/overview https://highlight.io/docs/general/product-features/session-r...
[4]: https://opentelemetry.io/docs https://opentelemetry.io/docs
[5]: https://www.highlight.io/docs/general/company/open-source/self-host-hobby https://www.highlight.io/docs/general/company/open-source/se...
- TommyDANGerous 4y agoWe use the cloud hosted version and love it. Hope the OSS version is easy to set up.
- vadman97 4y agoWe've put a lot of effort already to make the OSS setup a single `docker compose` command despite the extensive infra we use under the hood. Longer term, we're planning to support other deployment strategies such as kubernetes, cloud templates, and openshift templates. Appreciate any feedback on the self-hosting end here or on our GitHub issues!
- dnsmichi 4y agoGitLab team member here. Thanks for sharing! > We’re also toying with the idea of an “enterprise” self-hosted deployment, similar to gitlab’s billing model, and thoughts from the community on this front would be appreciated! Transparency and an open stewardship of the project can help: https://about.gitlab.com/company/stewardship/ https://about.gitlab.com/company/stewardship/ Make it clear what features are paid, and define that for example free features are never moved to the paid tier.
- podoman 4y agoThat's a good point; we should be clear about what will always be free. Right now, literally everything is free, but what we'd consider putting behind an enterprise tier that are top of mind are: - multi-tenancy - enterprise authentication features (sso, saml, etc..) Re: the gitlab link you sent, we really like the transparency around not making a free feature paid, and the fact that all tests are OSS. Overall, we'll work on something like this. Thanks for pointing it out!
- jonas-w 4y agoKeep https://sso.tax https://sso.tax in mind
- 4y ago