Launch HN: Highlight.io (YC W23) – Open-source, full stack web app monitoring
This is where Highlight.io comes in: our product bridges the gap between client and server to give you a holistic view of your entire application.
At its core, Highlight.io has three main “products”: Session Replay, Error Monitoring, and Logging. The novelty here is not in each product but in how they are connected. For example, in Highlight.io it’s very easy to click from a given error to the associated user session where it is thrown [4], and from a given error, you can easily inspect all of the logs that fired leading up to it. Ensuring that all of our products work together seamlessly with little to no effort is a core principle of our product strategy. If you’re using a common framework [5], for example, we’ll automatically link your frontend sessions with backend errors and logs. No agents, configuring facets, or anything else, It just works.
We depend on several open source projects that help us move quickly. OpenTelemetry (OTEL) [6] is one of them, which helps us with maintainability, i.e. for every language that we support, we only maintain a thin wrapper around its respective OTEL SDK. OTEL is also a great way to enable the community to contribute, and we’re already seeing traction in this space (ie. an open source contributor built a wrapper for a Java SDK [7]).
rrweb [8] is another project we leverage heavily for our session replay product. It drives our ability to record and replay the DOM to visualize user flows in the frontend. We’ve had the privilege to work closely with the rrweb team to ship improvements, and we’re now actively sponsoring the project [9].
ClickHouse [10] has recently become a loved database on our team, as we historically used Opensearch for search-heavy workloads and started to hit growing pains with ingest throughput. We recently rolled it out for our logging product [3] and plan to replace our sessions and errors (and upcoming tracing work) with the database as well.
From a business perspective, Highlight.io is open source under the Apache 2.0 license, and we make money with our hosted product [11]. For the hosted product, you can set billing caps for each offering and we don’t charge for seats. At this point, we have 100+ companies paying for our product (some of which are large enterprises), and thousands of sole developers use Highlight.io every week.
On our roadmap [12] for the future includes metrics, tracing, release management and more. We also are launching several updates this week on our launch week page [13].
Overall, we’re excited to be sharing Highlight.io with the world, and Vadim and I are particularly excited to get some feedback from the HN community. Please give us a test-drive at https://app.highlight.io and let us know what you think. We would love to learn about what you wish you had in an observability product as well as any other experiences and ideas in this space. We look forward to hearing from you!
135 comments
[ 3.1 ms ] story [ 223 ms ] threadThere's a few reasons why someone would use us over Sentry. First is that our session replay product is much more robust imo, though they are working quickly in that space: https://www.highlight.io/docs/general/product-features/sessi...
Secondly, we have a logging product: https://www.highlight.io/docs/general/product-features/loggi...
And lastly, we prefer to keep our product simple and very opinionated. Most of our customers are using common frameworks and we're specifically focused on web. Long term, we see ourselves going in the direction of Datadog, building out a metrics and tracing product over the next 6 months or so.
Why using 6 databases? Kafka, redis, Postgres, ClickHouse, influxdb, opensearch
Why?
Kafka - buffers data ingest so that we never lose recordings. Redis - acts as a cache, optimized for write-heavy processing in our app. Postgres - stores metadata for the data we record. ClickHouse - stores logs and other time-series data that need to be aggregated.
We're looking to simplify the system and replacing InfluxDB + OpenSearch in the near future with ClickHouse as a more performance and cost-effective solution that has proven simpler to maintain.
Also please make sure you have multi-line logs covered out of the gate. (Logtail, for example, doesn't support multiline stacktraces(!))
One thing that isn't clear to me from your marketing is what capability you have to support frameworks that aren't in your list. Do you have a regexp/generic parsing engine/ui?
> Also please make sure you have multi-line logs covered out of the gate. (Logtail, for example, doesn't support multiline stacktraces(!))
Noted. We're doing a push on our logging UX soon and can take a look.
> One thing that isn't clear to me from your marketing is what capability you have to support frameworks that aren't in your list. Do you have a regexp/generic parsing engine/ui?
I'm not entirely sure about the question, but we can receive logs via several specifications. OTEL, HTTP, Fluentbit, etc.. Does that answer your question? Or are you talking more about log filtering (i.e. filtering out logs for a specific log level)?
As someone building a bootstrapped product with my co-founder [1][2] Highlight has been a pretty amazing time save for us; setting up session replaying + monitoring + logging took all of 15 minutes and let me get back to actually focusing on building the product.
We're running on DOKS (Digital Ocean K8s) due to my familiarity with the hosting stack, and I really didn't want to spend the time setting up a cluster agent + log rotation strategy.
Surprisingly, the popular logging providers out there today don't really have alternative quick-start solutions for shipping logs in clusters, but Highlight DID and it also came with error monitoring + session replays.
All in all I'm pretty happy with the product and looking forward to using it more as we approach our product's soft-launch date at the end of this month with some select clubs.
[1] https://embolt.app/ [2] https://demo.embolt.app/admin/
Where did you find this? Did you self-host or go with hosted?
On the docs for ingesting data, I only found some guides for things like aws - not k8s?
And there's just some Docker guides and an open issue regarding hosting: https://github.com/highlight/highlight/issues/4390
Looking forward to dependencies being cut down a bit as it should make it almost trivial to set it up for k8s (both hosting and ingesting logs).
Essentially, we just have an additional logger attached to our stdout logger which ships logs over to highlight using their OpenTelemetry implementation. No infrastructure required, pretty simple.
[1] https://www.highlight.io/docs/getting-started/backend-sdk/ru...
We're planning to support k8s (openshift etc.) in the next 3-6 months. If you have another platform you'd like to see supported, please commented on the issue you linked.
I thought you were an app for people that care about their social media reach (like, twitter tech influencers). Forgiveable since your hero copy is " Build your Reach".
It's super important when writing marketing copy to name your users. If I'm a club chair for the local bowling league and I see "sports leagues" mentioned then my brain will just think "oh, this is for me!"
The first paragraph in your about page is so much better:
> Whether you're a sports club, social group, hobbyist organization, or non-profit, embolt is the solution to running your organization. We believe every club and organization should have a reliable platform to accept online member dues, manage registration, run events, and so much more.
I would replace the hero copy with a condensed version of that.
I agree with what you're saying, our homepage came before our product so we're in a goofy stage of having a nearly finished MVP product and no mention or links to it on the marketing pages.
I get it. it's a business, and it really is open source (thanks for the permissive license), but it often feels more like an after-thought/marketing play, which is completely fine if you're upfront. or maybe I'm just spoiled.
Are there any other things you’d suggest we can change on our site to make it bode better?
https://www.highlight.io/docs/general/company/open-source/ho...
We are not specifically focused on web app monitoring, but you should be able to monitor web app easily, esp. if you want to also monitor backend services and have frontend in JS
And, yeah - we have all the docs for self hosting - https://signoz.io/docs/install/
Docs for Angular apps - https://signoz.io/docs/tutorial/instrumenting-angular-fronte...
[0]: https://www.uxwizz.com/
We do have more SDKs in the works, and occasionally, community members help us out as well (see the comment about our java sdk above). If you have any thoughts, please share (tickets below).
Regarding Elixir, we have some experience with the language within our team, so please reach out if we can build something for you in the short term. I'm at jay [at] highlight [dot] io.
https://github.com/highlight/highlight/issues/5082 https://github.com/highlight/highlight/issues/4452
More specifically, how would that look and work from an sre/product/devops perspective?
Thanks!
If you'd like to ask questions synchronously or over email, I'm a jay [at] highlight [dot] io.
I'll have a better look at the docs tomorrow and try it out.
Good luck, I’ve been having highlights on my radar since your first post on HN.
Congrats on the launch!!
In this mode you can see the cursor move, any selections, etc. You also get a basic view of the network developer tools console for that user.
Fascinating.
1: https://keeb.dev/static/highlight-crazy.png
I have to say though your landing page looks remarkably similar to Posthog. So much so that I am having to double check to make sure you are not the same company.
1. Do you or are you looking to add redux recording? This is a must for us.
2. Why are session replay costs so high? Is there a lot of data stored? Nobody seems to have a cost effective solution once you get to high volumes.
3. I'd happily self-host to take the hit on the storage/database costs internally but $3k per month is unworkable for us. Is there a way around this (I can see how this would potentially break your business model)? 4. Do you have any plans to offer discounts for startups?
Thanks!
I made a ticket here; do you mind helping with some of the points I added?
https://github.com/highlight/highlight/issues/5990
Regarding pricing, at that volume, we charge less than Logrocket (you'll need to reach out to us about it for now: jay [at] highlight [dot] io). We also have features that let you only record sessions with errors if you don't want to record everything. Overall, our goal from a business strategy is to be your one stop shop for application monitoring, not just a specialized tool for session replay like logrocket.
Sorry for the long reply.
I'm not sure why they put "open source" in the pitch. I could care less if it's Open Source. I want a working product and responsive support, not a hippy license agreement.
Sentry currently just drops extra errors (at least this happened to us before we upgraded)
Let me know if that doesn’t answer the question.