Mixing
Sitecore Licensing - Can i use Dev licence to set up Dev-Int, QA, UAT instance?
I'm proposing a new Environment architecture to my organization, that eventually help in setting up the Proper CI/CD setup.
Currently, they have 4 Sitecore licence, so they used each one for QA, UAT, CM and Prod CD.
In contrast i'm proposing to have separate CM and CD for each environment. For example, QA will have its own CM and CD, Like wise, UAT and Prod will have their own CM and CD. But to implement this, we may have to procure more Sitecore licence and my Organization is not ready to spend money for new licenses.
My question is, Can we use the Development license for non production environment? If required, i can restrict access of non production environment to outside world.
I'm open for any other suggestion where i can restrict licensing cost. Your help is appreciated.
licensing
edited Jan 8 at 12:32
Dan Sinclair
1,649525
asked Jan 8 at 10:25
PaRsHPaRsH
1124
add a comment |
I'm proposing a new Environment architecture to my organization, that eventually help in setting up the Proper CI/CD setup.
Currently, they have 4 Sitecore licence, so they used each one for QA, UAT, CM and Prod CD.
In contrast i'm proposing to have separate CM and CD for each environment. For example, QA will have its own CM and CD, Like wise, UAT and Prod will have their own CM and CD. But to implement this, we may have to procure more Sitecore licence and my Organization is not ready to spend money for new licenses.
My question is, Can we use the Development license for non production environment? If required, i can restrict access of non production environment to outside world.
I'm open for any other suggestion where i can restrict licensing cost. Your help is appreciated.
licensing
edited Jan 8 at 12:32
Dan Sinclair
1,649525
asked Jan 8 at 10:25
PaRsHPaRsH
1124
add a comment |
I'm proposing a new Environment architecture to my organization, that eventually help in setting up the Proper CI/CD setup.
Currently, they have 4 Sitecore licence, so they used each one for QA, UAT, CM and Prod CD.
In contrast i'm proposing to have separate CM and CD for each environment. For example, QA will have its own CM and CD, Like wise, UAT and Prod will have their own CM and CD. But to implement this, we may have to procure more Sitecore licence and my Organization is not ready to spend money for new licenses.
My question is, Can we use the Development license for non production environment? If required, i can restrict access of non production environment to outside world.
I'm open for any other suggestion where i can restrict licensing cost. Your help is appreciated.
licensing
edited Jan 8 at 12:32
Dan Sinclair
1,649525
asked Jan 8 at 10:25
PaRsHPaRsH
1124
I'm proposing a new Environment architecture to my organization, that eventually help in setting up the Proper CI/CD setup.
Currently, they have 4 Sitecore licence, so they used each one for QA, UAT, CM and Prod CD.
In contrast i'm proposing to have separate CM and CD for each environment. For example, QA will have its own CM and CD, Like wise, UAT and Prod will have their own CM and CD. But to implement this, we may have to procure more Sitecore licence and my Organization is not ready to spend money for new licenses.
My question is, Can we use the Development license for non production environment? If required, i can restrict access of non production environment to outside world.
I'm open for any other suggestion where i can restrict licensing cost. Your help is appreciated.
licensing
licensing
edited Jan 8 at 12:32
Dan Sinclair
1,649525
asked Jan 8 at 10:25
PaRsHPaRsH
1124
edited Jan 8 at 12:32
Dan Sinclair
1,649525
asked Jan 8 at 10:25
PaRsHPaRsH
1124
edited Jan 8 at 12:32
Dan Sinclair
1,649525
edited Jan 8 at 12:32
Dan Sinclair
1,649525
edited Jan 8 at 12:32
Dan Sinclair
1,649525
1,649525
asked Jan 8 at 10:25
PaRsHPaRsH
1124
asked Jan 8 at 10:25
PaRsHPaRsH
1124
asked Jan 8 at 10:25
PaRsHPaRsH
1124
1124
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
Always ask this question to your Sitecore Sales rep
If you are working at a customer, your sales rep is the only person who can definitively look at your license agreement and validate if it covers the scenario you are attempting. Nobody on this site can definitively answer license questions but them. All that can be provided is a guess at some 'normal' scenarios.
Developer seat vs. Instance license
That said, a 'developer seat' is not typically allowed for network environments. It is meant for a local installation on a developers box. Your non-prod server instances are what can be used for your network instances and it does not matter if they are internally/externally available.
If the customer license is a perpetual license with specific server counts and you want to increase the number of non-production server counts, you will need to talk to a sales rep and obtain additional server counts, or transition to a newer subscription license model and license by environment.
answered Jan 8 at 13:57
Jason St-CyrJason St-Cyr
4,651930
add a comment |
I wrote a blog post not too long ago, which you can find here, although this is already a bit outdated as I believe there's a new licensing model.
Long story short: Always check with your Sitecore sales representative first (account manager if you're a customer, partner manager if you're a partner)
Going by your question I'm assuming you're the end client, not the implementation partner (if you are the implementation partner, please see Vlad's answer).
If you have a perpetual license, you'll usually be licensed to have a certain number of production servers and non-production servers running. Production servers in perpetual are the CM and CD on a production environment. All other servers are classed as non-production.
If you have a subscription license, you'll be allowed to spin up as many production servers as you'd like (which in this case includes reporting and processing servers). As far as I'm aware there is typically a limit on the number of non-production servers.
So, looking at your question it's unlikely you'll be able to split your servers out without being in breach of license (as you mention you are allowed 4 environments and that's what you have), although it is worth checking it with your Sitecore contact.
answered Jan 8 at 13:14
TrayekTrayek
622214
1
Trayek, great answer, just wanted to note that customers on the latest model now have 'environment' subscriptions so instead of limited numbers of non-prod you can now purchase a 'UAT' environment with no specific instance limits in that environment
– Jason St-Cyr
Jan 8 at 13:50
@JasonSt-Cyr Thanks for that addition Jason, I'm not entirely familiar with the new model yet other than knowing there is one, so I didn't feel particularly well placed to go into details on that :-)
– Trayek
Jan 8 at 13:59
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "664"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsitecore.stackexchange.com%2fquestions%2f15905%2fsitecore-licensing-can-i-use-dev-licence-to-set-up-dev-int-qa-uat-instance%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Always ask this question to your Sitecore Sales rep
If you are working at a customer, your sales rep is the only person who can definitively look at your license agreement and validate if it covers the scenario you are attempting. Nobody on this site can definitively answer license questions but them. All that can be provided is a guess at some 'normal' scenarios.
Developer seat vs. Instance license
That said, a 'developer seat' is not typically allowed for network environments. It is meant for a local installation on a developers box. Your non-prod server instances are what can be used for your network instances and it does not matter if they are internally/externally available.
If the customer license is a perpetual license with specific server counts and you want to increase the number of non-production server counts, you will need to talk to a sales rep and obtain additional server counts, or transition to a newer subscription license model and license by environment.
answered Jan 8 at 13:57
Jason St-CyrJason St-Cyr
4,651930
add a comment |
Always ask this question to your Sitecore Sales rep
If you are working at a customer, your sales rep is the only person who can definitively look at your license agreement and validate if it covers the scenario you are attempting. Nobody on this site can definitively answer license questions but them. All that can be provided is a guess at some 'normal' scenarios.
Developer seat vs. Instance license
That said, a 'developer seat' is not typically allowed for network environments. It is meant for a local installation on a developers box. Your non-prod server instances are what can be used for your network instances and it does not matter if they are internally/externally available.
If the customer license is a perpetual license with specific server counts and you want to increase the number of non-production server counts, you will need to talk to a sales rep and obtain additional server counts, or transition to a newer subscription license model and license by environment.
answered Jan 8 at 13:57
Jason St-CyrJason St-Cyr
4,651930
add a comment |
Always ask this question to your Sitecore Sales rep
If you are working at a customer, your sales rep is the only person who can definitively look at your license agreement and validate if it covers the scenario you are attempting. Nobody on this site can definitively answer license questions but them. All that can be provided is a guess at some 'normal' scenarios.
Developer seat vs. Instance license
That said, a 'developer seat' is not typically allowed for network environments. It is meant for a local installation on a developers box. Your non-prod server instances are what can be used for your network instances and it does not matter if they are internally/externally available.
If the customer license is a perpetual license with specific server counts and you want to increase the number of non-production server counts, you will need to talk to a sales rep and obtain additional server counts, or transition to a newer subscription license model and license by environment.
answered Jan 8 at 13:57
Jason St-CyrJason St-Cyr
4,651930
Always ask this question to your Sitecore Sales rep
If you are working at a customer, your sales rep is the only person who can definitively look at your license agreement and validate if it covers the scenario you are attempting. Nobody on this site can definitively answer license questions but them. All that can be provided is a guess at some 'normal' scenarios.
Developer seat vs. Instance license
That said, a 'developer seat' is not typically allowed for network environments. It is meant for a local installation on a developers box. Your non-prod server instances are what can be used for your network instances and it does not matter if they are internally/externally available.
If the customer license is a perpetual license with specific server counts and you want to increase the number of non-production server counts, you will need to talk to a sales rep and obtain additional server counts, or transition to a newer subscription license model and license by environment.
answered Jan 8 at 13:57
Jason St-CyrJason St-Cyr
4,651930
edited Jan 8 at 14:21
answered Jan 8 at 13:57
Jason St-CyrJason St-Cyr
4,651930
answered Jan 8 at 13:57
Jason St-CyrJason St-Cyr
4,651930
answered Jan 8 at 13:57
Jason St-CyrJason St-Cyr
4,651930
4,651930
add a comment |
add a comment |
I wrote a blog post not too long ago, which you can find here, although this is already a bit outdated as I believe there's a new licensing model.
Long story short: Always check with your Sitecore sales representative first (account manager if you're a customer, partner manager if you're a partner)
Going by your question I'm assuming you're the end client, not the implementation partner (if you are the implementation partner, please see Vlad's answer).
If you have a perpetual license, you'll usually be licensed to have a certain number of production servers and non-production servers running. Production servers in perpetual are the CM and CD on a production environment. All other servers are classed as non-production.
If you have a subscription license, you'll be allowed to spin up as many production servers as you'd like (which in this case includes reporting and processing servers). As far as I'm aware there is typically a limit on the number of non-production servers.
So, looking at your question it's unlikely you'll be able to split your servers out without being in breach of license (as you mention you are allowed 4 environments and that's what you have), although it is worth checking it with your Sitecore contact.
answered Jan 8 at 13:14
TrayekTrayek
622214
1
Trayek, great answer, just wanted to note that customers on the latest model now have 'environment' subscriptions so instead of limited numbers of non-prod you can now purchase a 'UAT' environment with no specific instance limits in that environment
– Jason St-Cyr
Jan 8 at 13:50
@JasonSt-Cyr Thanks for that addition Jason, I'm not entirely familiar with the new model yet other than knowing there is one, so I didn't feel particularly well placed to go into details on that :-)
– Trayek
Jan 8 at 13:59
add a comment |
I wrote a blog post not too long ago, which you can find here, although this is already a bit outdated as I believe there's a new licensing model.
Long story short: Always check with your Sitecore sales representative first (account manager if you're a customer, partner manager if you're a partner)
Going by your question I'm assuming you're the end client, not the implementation partner (if you are the implementation partner, please see Vlad's answer).
If you have a perpetual license, you'll usually be licensed to have a certain number of production servers and non-production servers running. Production servers in perpetual are the CM and CD on a production environment. All other servers are classed as non-production.
If you have a subscription license, you'll be allowed to spin up as many production servers as you'd like (which in this case includes reporting and processing servers). As far as I'm aware there is typically a limit on the number of non-production servers.
So, looking at your question it's unlikely you'll be able to split your servers out without being in breach of license (as you mention you are allowed 4 environments and that's what you have), although it is worth checking it with your Sitecore contact.
answered Jan 8 at 13:14
TrayekTrayek
622214
1
Trayek, great answer, just wanted to note that customers on the latest model now have 'environment' subscriptions so instead of limited numbers of non-prod you can now purchase a 'UAT' environment with no specific instance limits in that environment
– Jason St-Cyr
Jan 8 at 13:50
@JasonSt-Cyr Thanks for that addition Jason, I'm not entirely familiar with the new model yet other than knowing there is one, so I didn't feel particularly well placed to go into details on that :-)
– Trayek
Jan 8 at 13:59
add a comment |
I wrote a blog post not too long ago, which you can find here, although this is already a bit outdated as I believe there's a new licensing model.
Long story short: Always check with your Sitecore sales representative first (account manager if you're a customer, partner manager if you're a partner)
Going by your question I'm assuming you're the end client, not the implementation partner (if you are the implementation partner, please see Vlad's answer).
If you have a perpetual license, you'll usually be licensed to have a certain number of production servers and non-production servers running. Production servers in perpetual are the CM and CD on a production environment. All other servers are classed as non-production.
If you have a subscription license, you'll be allowed to spin up as many production servers as you'd like (which in this case includes reporting and processing servers). As far as I'm aware there is typically a limit on the number of non-production servers.
So, looking at your question it's unlikely you'll be able to split your servers out without being in breach of license (as you mention you are allowed 4 environments and that's what you have), although it is worth checking it with your Sitecore contact.
answered Jan 8 at 13:14
TrayekTrayek
622214
I wrote a blog post not too long ago, which you can find here, although this is already a bit outdated as I believe there's a new licensing model.
Long story short: Always check with your Sitecore sales representative first (account manager if you're a customer, partner manager if you're a partner)
Going by your question I'm assuming you're the end client, not the implementation partner (if you are the implementation partner, please see Vlad's answer).
If you have a perpetual license, you'll usually be licensed to have a certain number of production servers and non-production servers running. Production servers in perpetual are the CM and CD on a production environment. All other servers are classed as non-production.
If you have a subscription license, you'll be allowed to spin up as many production servers as you'd like (which in this case includes reporting and processing servers). As far as I'm aware there is typically a limit on the number of non-production servers.
So, looking at your question it's unlikely you'll be able to split your servers out without being in breach of license (as you mention you are allowed 4 environments and that's what you have), although it is worth checking it with your Sitecore contact.
answered Jan 8 at 13:14
TrayekTrayek
622214
answered Jan 8 at 13:14
TrayekTrayek
622214
answered Jan 8 at 13:14
TrayekTrayek
622214
answered Jan 8 at 13:14
TrayekTrayek
622214
622214
1
Trayek, great answer, just wanted to note that customers on the latest model now have 'environment' subscriptions so instead of limited numbers of non-prod you can now purchase a 'UAT' environment with no specific instance limits in that environment
– Jason St-Cyr
Jan 8 at 13:50
@JasonSt-Cyr Thanks for that addition Jason, I'm not entirely familiar with the new model yet other than knowing there is one, so I didn't feel particularly well placed to go into details on that :-)
– Trayek
Jan 8 at 13:59
add a comment |
1
Trayek, great answer, just wanted to note that customers on the latest model now have 'environment' subscriptions so instead of limited numbers of non-prod you can now purchase a 'UAT' environment with no specific instance limits in that environment
– Jason St-Cyr
Jan 8 at 13:50
@JasonSt-Cyr Thanks for that addition Jason, I'm not entirely familiar with the new model yet other than knowing there is one, so I didn't feel particularly well placed to go into details on that :-)
– Trayek
Jan 8 at 13:59
1
1
Trayek, great answer, just wanted to note that customers on the latest model now have 'environment' subscriptions so instead of limited numbers of non-prod you can now purchase a 'UAT' environment with no specific instance limits in that environment
– Jason St-Cyr
Jan 8 at 13:50
Trayek, great answer, just wanted to note that customers on the latest model now have 'environment' subscriptions so instead of limited numbers of non-prod you can now purchase a 'UAT' environment with no specific instance limits in that environment
– Jason St-Cyr
Jan 8 at 13:50
@JasonSt-Cyr Thanks for that addition Jason, I'm not entirely familiar with the new model yet other than knowing there is one, so I didn't feel particularly well placed to go into details on that :-)
– Trayek
Jan 8 at 13:59
@JasonSt-Cyr Thanks for that addition Jason, I'm not entirely familiar with the new model yet other than knowing there is one, so I didn't feel particularly well placed to go into details on that :-)
– Trayek
Jan 8 at 13:59
add a comment |
Thanks for contributing an answer to Sitecore Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsitecore.stackexchange.com%2fquestions%2f15905%2fsitecore-licensing-can-i-use-dev-licence-to-set-up-dev-int-qa-uat-instance%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
