There are a few key considerations that needs to be investigated:
Self-hosting vs. Cloud-hosting
Self-hosting
Benefits
No monthly SaaS-cost
No limitations in terms of number of users, data retention periods, number of websites being monitored etc. associated with a specific hosting plan.
Full control over data retention, encryption, backups etc.
Might be able to utilise pre-existing infra, such as Container App Environments, database servers, Azure security, SSO solutions etc etc
Direct database access guarantees we can build our own integrations if sufficient API support is lacking
Open source
Negatives
Can be complex to setup and maintain, update etc
Considering that the tools we’re looking at have fairly cheap cloud pricing, this is most likely more expensive. This of course depends on how much of our current infra can be utilised for the hosting
More effort to evaluate the tools because of setup process
Liability: The data resides with us and we need to make sure it’s safe.
Backup processes, access control
Need to be on top of legal regulations - both current and future
Limited support when using OSS
Cloud-hosting
Benefits
Easy to quickly evaluate and compare the different tools
Hosting plans seems cheap for our traffic volumes
Low maintenance
Negatives
As per-usual, all plans come with different limitations such as number of users in the tool, data retention period, traffic volume, available features. We might end up on a more expensive plan than necessary in the end to cater for some feature we want.
Might be legal implications around where the data is stored
Want to print your doc? This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (