Simple per-node annual license, with the ability to mix-and-match.
per node
Enterprise Repo
6 Support Tickets per year
1 business day response time
per node
Enterprise Repo
12 Support Tickets per year
8 Hour response time
Managed Upgrades & Installation
Remote SSH Support
per node
Enterprise Repo
Unlimited Tickets
4 Hour response time
Managed Upgrades & Installation
Remote SSH Support
Dedicated Slack Channel
Yes, Absolutely!
Generally you will only ever need a single controller. The only situation where multiple controllers might make sense is if you plan to resell hosted versions of ComputeStacks, or if you plan to give a single customer their own ComputeStacks environment.
We build integrations based on customer feedback, and our expectation of future demand. For unique integrations, we will generally recommend that our customers review our API documentation and our OAuth2 features. That has generally worked for custom use cases, however please contact us to discuss your unique requirements.
Our enterprise repo provides a slower release cycle from our open-source main branch, as well as, long term support.
For basic & standard plans, the ticket quantity is per-license. For example, if you had 3 servers on the standard plan, you would have a total of 36 tickets per year. They are also not restricted to the individual nodes. They cover all things related to the node, including the controller, images, projects, dns, etc.
If you do not have your own infrastructure, and don't wish to manage the platform, we do offer a cloud version that is managed by us. Please contact us for more details.
Yes, as part of your onboarding experience, we can work with you to reskin the web user interface.
Yes, absolutely! We have customers that are using us in a non-standard environment, and we are happy to work with you.
No! They are exactly the same. The only difference is the level of support you get, access to the more stable long-term supported repository, and of course, you’re supporting the project.
You may mix and match license types within a Region, but not an Availability-Zone. However, all nodes must at least have the Community license. If you wish to use the open-source license, you will need to deploy a separate controller.