SLASCONE is available as a managed SaaS solution and, if required, as a private deployment in your own Microsoft Azure subscription. A traditional on-premise installation outside Azure is not supported.
For most customers, the SLASCONE SaaS environment is the recommended deployment model. It provides the fastest path to evaluation, integration, and production use, while avoiding the need to plan, deploy, monitor, and operate dedicated cloud infrastructure.
DEPLOYMENT OPTIONS
SLASCONE supports two deployment options:
SaaS: SLASCONE is operated as a managed cloud service by SLASCONE.
Private Deployment: SLASCONE is deployed into your own Microsoft Azure subscription and operated according to an agreed responsibility model.
Both options are based on the same SLASCONE product and API concepts. The main difference is where the platform is hosted and how much operational responsibility is shifted to the customer side.
RECOMMENDED APPROACH
For most customers, SLASCONE SaaS is the recommended starting point. It is the fastest and simplest way to evaluate, integrate, and operate SLASCONE without having to plan and maintain dedicated cloud infrastructure.
SaaS is also the preferred starting point because it allows teams to focus on the actual licensing implementation first: product modeling, API integration, activation flows, analytics, and rollout.
A private deployment should usually be considered only when there are clear internal security, compliance, data residency, or operational requirements that cannot be addressed with the standard SaaS environment.
Starting with SaaS does not close the door to a private deployment later. If required, the deployment model can be revisited after the initial rollout, typically after 6 to 12 months, when the technical, operational, and compliance requirements are better understood.
SaaS
In the SaaS model, SLASCONE operates and maintains the platform. This includes hosting, updates, monitoring, backups, and the underlying cloud infrastructure.
SaaS is the preferred option for most projects because it reduces operational effort and accelerates the implementation timeline. Your team can focus on licensing logic, product setup, API integration, and customer rollout instead of infrastructure topics.
BENEFITS OF SaaS
Fastest path to evaluation and production rollout
No need to operate dedicated SLASCONE infrastructure
Managed updates, monitoring, and platform operations
Lower initial project complexity
Suitable for most production scenarios
PRIVATE DEPLOYMENT CONSIDERATIONS
A private deployment provides additional control over the hosting environment, but it also introduces additional coordination, infrastructure, monitoring, security, and operational complexity.
For this reason, private deployment is usually best evaluated after the licensing concept and integration approach have been validated.
Private deployment may be relevant if your organization has specific internal requirements for hosting, compliance, data control, update timing, network architecture, or operational governance.
WHEN PRIVATE DEPLOYMENT MAY BE REQUIRED
Your organization requires the SLASCONE environment to run in its own Microsoft Azure subscription.
You have strict internal requirements regarding data residency, network isolation, or infrastructure governance.
Your internal policies require direct control over the cloud resources used by business-critical systems.
You need to align update windows, monitoring, or operational procedures with existing internal processes.
PRIVATE DEPLOYMENT REQUIREMENTS
A private deployment requires an appropriate Microsoft Azure subscription, infrastructure planning, operational alignment, and a clear understanding of responsibilities between your organization and SLASCONE.
Compared to SaaS, this usually requires more preparation before the actual licensing implementation can start. Topics such as Azure resource sizing, networking, security configuration, monitoring, backup, and access management need to be clarified.
STARTING WITH SaaS AND MOVING LATER
Starting with SaaS is often the most practical approach, even if a private deployment is being considered for the future.
This allows your team to validate the licensing model, complete the API integration, collect operational experience, and go live faster. If private deployment is still required, the deployment model can be revisited after the initial rollout, typically after 6 to 12 months.
This approach reduces initial project risk and avoids delaying the licensing implementation because of infrastructure decisions that may become clearer only after real usage.
Comments
0 comments
Please sign in to leave a comment.