You can deploy your Cirkus on a private cloud hosted service, which is managed by us.
In this case there are a number of configurable options which are only available on private clouds, and not on cirkus.com (“public cloud” with own Workspace)
- Domain
- Permissions
- Branding: Company Logo and email
- SSO integrations and allowed authentication methods
- App distribution methods
- DetailedApplication Preferences
- Security
- Cloud Infrastructure
Domain
You can define a custom domain for your private Cirkus server, such as yourcompany.cirkus.com or cirkus.yourcompany.com.
This URL will be used by your web-based users and by your iOS and Mac clients to connect to the server.
If you opt for a subdomain of yourcompany.com, your IT team will need to handle the necessary DNS updates and SSL certificates.
Permissions
You can update the default permissions for your Cirkus server, such as allowing Workspace Members to create projects but not edit them. Additionally, you can create custom permission profiles on a private Cirkus server. Learn more about the standard permissions in this article.
Branding: Company Logo and email
You can customize your Cirkus login page with your company logo and set up a custom email sender and logo for Cirkus notification emails. These options are configured on your private Cirkus server by your Server Administrator and can be modified by contacting support@cirkus.com.
SSO integrations and allowed authentication methods
On your private server, you can specify which authentication methods are available. The current options are email/password (default), OKTA, and Entra ID. Only the selected methods will be offered to your users. Note that OKTA and Entra ID are only available in private clouds and not on cirkus.com.
App distribution methods
If your users will use the iOS or macOS applications, you can define a distribution strategy that works for your company:
1. Distribute Apps from the App Store (Default)
In this scenario, the Cirkus team handles all versioning and distribution of the apps. Use this method if your security policy allows downloading apps from the App Store. You can opt for automatic or manual updates from the App Store, but supported Cirkus versions will always be the latest available there, ensuring your server and web deployments are in sync.
**Note:** If using the Mac and iOS apps from the App Store, users with the same email domain can be automatically routed to your private server and SSO method. Collaborators without the same email domain will need to manually set the Cirkus server to connect to. This setting persists until they log out and needs to be set at each login, so it's advisable not to log out of the applications (applicable from Cirkus 1.95+).
2. Distribute Apps Outside the App Store (e.g., self-managed with Jamf or others)**
In this scenario, the Cirkus team will provide you (or your IT contact) with your own build of the Cirkus applications to distribute for each upgrade. Use this method if your security policy does not allow downloading apps from the App Store. This method requires additional support services. Contact sales@cirkus.com to learn more about this option.
Detailed Application Preferences
Start Day: You can define what day of the week should be the first one across your server.
Task numbering strategy : Per Workspace or Global. This defines if Task numbers should be unique in each Workspace, or across the entire server.
Security
You can define some security rules about the traffic which is allowed to access your server and this can be implemented on the Web Application Firewall which we manage for you, based on IP address or traffic patterns.
You can also specify that only specific email domains can be used to signup on the application
Cloud Infrastructure
Your clouded infrastructure can be deployed at a global location closest to your end users, reducing latency and adhering to data export policies.