add Operately

[markoa]

Thanks for taking the time to suggest an addition to awesome-selfhosted!

To ensure your Pull Request is dealt with swiftly, please check the following (check the boxes [x]):

• Submit one item per pull request. This eases reviewing and speeds up inclusion.
• You have searched the repository for any relevant issues or PRs, including closed ones.
• Any software you are adding is not already listed at any of awesome-sysadmin, staticgen.com, staticsitegenerators.bevry.me, dbdb.io.
• The file you are adding is formatted as described in addition.md.
• Demo links should only be used for interactive demos, i.e. not video demonstrations. If login credentials are required to access the demo, please link to the credentials directly.
• Comments and unused optional fields have been removed.
• The file you are adding uses kebab-case file naming, for example my-awesome-software.yml.
• Values for platform should match the platforms required to install and run the software.
• Any software project you are adding to the list is actively maintained.
• Any software project you are adding was first released more than 4 months ago.
• Any software project you are adding has working installation instructions.
• You understand that your Pull Request will be merged ~1 week after approval, to allow for further comments if needed.

[Rabenherz112]

Project should prob. be renamed for Operately Community Edition as both the license file and the Deployment options state that a enterprise version exists

[nodiscc]

Are there different editions of the self-hosted version? How do they compare? Are there limitations in the self-hosted edition(s)?

[Technetium1]

I agree this should be marked Community Edition.
From License header https://github.com/operately/operately/blob/main/LICENSE

Files in the 'ee' directory are subject to the Operately Enterprise Edition License located in the 'ee/LICENSE' file.

https://github.com/operately/operately/blob/main/app/ee/LICENSE

How do they compare?

It seems like the main difference is the availability of these routes, which as far as I can tell (without running) do not seem to be necessary to use the software.

pageRoute("", adminpages.SaasAdminPage),
pageRoute("email-settings", adminpages.SaasAdminEmailSettingsPage),
pageRoute("billing-catalog", adminpages.SaasAdminBillingCatalogPage),
pageRoute("site-messages", adminpages.SaasAdminSiteMessagesPage),
pageRoute("companies/:companyId", adminpages.SaasAdminCompanyPage),