Hey Jcamp -- there are a few issues to consider for each specific case, but basically our product used to be licensed according to one of two models: per server or per user, more or less, although there were a few variants of the per user model including named users vs. seat licenses, etc.
Today, with the release of K2 blackpearl, K2 will be licensed per user, period. It's my understanding that this is a global move towards streamlining our licensing model.
The idea is you pay per user involved in the workflow, whether they design or participate, either way, they're a user. At that point, you can deploy as many servers as you need.
As per Gabriel's post, it does make a lot of sense to setup a robust QA environment to help support and maintain your applications in production.
Hopefully that answers your first question.
As for your second question, you may want to consider the following:
- does each functional area expect to own it's own workflows / sub-workflows?
- is there a centralized IT department that manages all of your business applications?
- do you expect business users to build and manage their own workflows with K2 blackpearl?
The point here being mainly that you may want to consider modelling your environment after your use of the platform itself. Centralized management of your business applications will be easier in a centralized, although perhaps load-balanced, environment. Distrubuted management may be enabled, even simplified, by distributed servers.
The statements and opinions made in my postings are my own, and do not reflect the opinions of SourceCode Technology Holdings, Inc. or its subsidiaries. All information is provided as is with no warranties, express or implied, and grants no rights or licenses.