No. Sentry has one codebase between free and paid. We have a Django monolith plus some services where all our features are implemented:
https://github.com/getsentry/sentry
https://github.com/getsentry/relay
https://github.com/getsentry/snuba
https://github.com/getsentry/vroom
etc.
We have a Docker Compose wrapper in a separate repo:
https://github.com/getsentry/self-hosted
We have a private repo called getsentry/getsentry that is another Django app that imports the public one and uses Django signals (iirc) to meter usage for billing. That is what we deploy to SaaS. All product features are implemented in the public repos.
3) How about employee access?
Employee access is managed through UI, I honestly don't know whether it lives in getsentry/sentry (public) or getsentry/getsentry (private). Probably the latter?
2) How do you handle updates to your product?
Employees work in public on GitHub. We ship more or less continuously to SaaS. It's possible to deploy approximately continuously on self-hosted as well, though we also bless monthly snapshots for a more relaxed cadence. Does that answer this question?