Clarity Self Hosted
- 09 Jan 2025
- 1 Minute to read
- Print
- DarkLight
- PDF
Clarity Self Hosted
- Updated on 09 Jan 2025
- 1 Minute to read
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
If you are interested in self hosting Clarity within your infrastructure, check out the details below for the requirements. The diagram below shows what parts of Clarity exist within your firewall (as apposed to our SaaS option hosted in AWS).
.png?sv=2022-11-02&spr=https&st=2025-01-18T01%3A49%3A12Z&se=2025-01-18T01%3A59%3A12Z&sr=c&sp=r&sig=ZD83Nn2njQ7NzgTYi5sVKqQnqQp352ekkQ6p9x0nGDs%3D)
Clarity VM (Appliance)
Recommended Specs:
Compute: 4 CPU
Memory: 4GB
Storage: ~40-50GB
Configurable Options
You can choose the following configuration options:
Feature | Options | Recommended |
|---|---|---|
SSH | Enabled or Disabled | Enabled |
Logs | Local or Cloudwatch | Cloudwatch: This lets your Clarity support team be aware of any errors that are generated in the logs. |
On-prem SMTP or AWS | AWS: Clarity will use an AWS service to send emails (reminders, notifications, etc.) |
Database (MySQL)
For the Self Hosted Clarity appliance to work, we will need a MySQL database to store the data for the Clarity Security platform (configuration details below):
Software: MySQL v8.0.23+
Database: New database (name will be needed during configuration)
Storage: 10-20GB
User: Service user with Read/Write to the database above
Clarity Connect (Required for on-prem apps)
See Configuring Clarity Connect (On-Premises) for details on how to configured our on-prem Docker stack for connecting to Active Directory and custom databases.
Need help?
If you have any problems, contact your customer success team. You can also get in touch with our general support via email, open a support ticket. Our general support team is available Monday - Friday from 8:00 AM - 6:30 PM CST.
Was this article helpful?
