self-hosted

The people we're concerned about are not the hundreds of thousands of Sentry users, including those that self-host. We're concerned about people who have taken the software for the purposes of competing directly against us, that hinders our ability to monetize the work. Monetizing the work helps us continue improving the software and distribute it for free use, benefitting those aforementioned real users (e.g. https://github.com/getsentry/self-hosted).

> I mean no slander or disrespect to anyone involved, but there was a DataDog alternative posted sometime in the last few weeks that had a docker-compose with like 15 containers in it. Reminds me of Sentry: https://develop.sentry.dev/self-hosted/ This is their example docker-compose for self-hosting: https://github.com/getsentry/self-hosted/blob/master/docker-... It has: - exim4 (smtp) - memcached - Redis - PostgreSQL - Zookeeper - Kafka - Clickhouse - geoipupdate - 18 containers for something called snuba (integrates with Clickhouse?) - 2 symbolicator containers - web app - cron - 18 other utility containers - Nginx - relay - 2 vroom containers Meanwhile, as far as the other options in the APM space go, this is how Apache Skywalking looks like: - web app - back end API - database (Elasticsearch/Open

> What should people use? I recall Apache Skywalking being pretty good, especially for smaller/medium scale projects: https://skywalking.apache.org/ The architecture is simple, the performance is adequate, it doesn't make you spend days configuring it and it even supports various different data stores: https://skywalking.apache.org/docs/main/v9.5.0/en/setup/back... The problems with it are that it isn't super popular (although has agents for most popular stacks), the docs could be slightly better and I recall them also working on a new UI so there is a little bit of churn: https://skywalking.apache.org/downloads/ Still better versus some of the other options when you need something that just works instead of spending a lot of time configuring something (even when that something might be superior in regards to the features): https://github

yes to the second https://github.com/getsentry/self-hosted/blob/23.4.0/docker-... and only after the embargo is over to the first: https://github.com/getsentry/self-hosted/blob/23.4.0/LICENSE... I also miss the "good old days" when running sentry was like 3 containers, not the 32 of modern Sentry

As all-in-Golang user, wish Tier to succeed too! Want to say Thank you for putting all artefacts online. Same applies to Lago! Admire your focus on Stripe and beginner friendly approach from the day one https://github.com/tierrun/tier/blob/main/pricing/schema.jso... https://docs.tier.run/docs/resources/mapping-to-stripe https://github.com/tierrun/tier/wiki/Stripe-Glossary Lago backend is built with Ruby and GraphQL ... which is kind of deal-breaker for me. No time to invest in Ruby ecosystem. I'm only using opensource products which I can fork and debug later on. https://github.com/getlago/lago-api/tree/619a7a53f98d9a19908... Lago is much closer the production ready however. Solid stand-alone tool already. Tier like projects gives me hope to give SaaS user better embedded billing experience and more control in the future. My biggest scar