Risk Management Framework

Vendor Support Levels

VSL1 — VSL6

A critical component of risk management, Service Level Agreement definition, and strategic technology planning. By clearly categorizing the supportability of a technology stack, this model ensures transparency with clients, protects the organization from unmanageable liabilities, and aligns technical capabilities with long-term business goals.

VSL6 · Strategic VSL5 · Partner VSL4 · Integrator VSL3 · Community VSL2 · Research VSL1 · No-Go
★
Overview

The Business Value of VSL

The Vendor Support Level framework is not just a technical categorization; it is a risk management and ethical governance tool.

It ensures that we only make promises that we can keep. It protects capital by preventing engineers from sinking hundreds of hours into unsupported, dying technology (VSL1/VSL2). Most importantly, it builds long-term client loyalty through radical transparency: clients know exactly what they are buying, what the risks are, and that their core systems (VSL6) are backed by a partner committed to their success for the long haul.

1
Core Philosophy

Transparency, Risk Management & SLA Alignment

The VSL framework exists to answer a fundamental business question: “If this technology fails, who fixes it, how quickly, and at what cost?”

Trust but Verify

This model prevents over-promising. It ensures that SLAs are only applied to technologies where the organization has the actual capacity, vendor backing, or internal expertise to guarantee uptime and resolution.

Strategic Alignment

It forces the business to consciously decide which technologies are core competencies (worthy of heavy investment) and which are peripheral or unacceptable risks.

Client Transparency

By openly sharing a product's VSL status, clients can make informed decisions about their technology stack, understanding exactly where the boundaries of support lie.

2
Detailed Breakdown

Vendor Support Levels (VSL)

VSL6

Remote Support Strategic Solution Offering

Core Definition: The absolute highest tier of commitment. The product is officially supported by the vendor, and Remote Support operates as a formal strategic partner. Crucially, Remote Support guarantees continuity of support even if the original vendor ceases operations or abandons the product.

Key Indicators

  • Significant internal research, development, and financial investment
  • Long history of active, in-house usage (“we eat our own cooking”)
  • Authoritative, deep-level knowledge of the product's architecture
  • Formal strategic alliance or partnership agreement with the vendor
  • A binding, long-term commitment to the platform's roadmap

Typical Use Cases

Core infrastructure offerings (e.g., heavily customized Nextcloud/LibreSign deployments, proprietary backup architectures, or core SME All-in-One Suite components).

SLA & Business Value: This tier qualifies for the highest SLA guarantees (e.g., 99.9% uptime with defined service credits). It forms the foundation of the company's reputation, ensuring clients that their most critical systems are backed by an organization that will not abandon them, regardless of market shifts.
VSL5

Officially Supported (Partner Level)

Core Definition: The product has official, active support from the original vendor, and Remote Support supports and integrates it as a recognized partner.

Key Indicators

  • Access to partner-level vendor support channels
  • Partner training certifications
  • Established integration pathways

Typical Use Cases

Major third-party enterprise tools that complement the core offering but are not the primary focus of internal R&D (e.g., specific monitoring tools, specialized security appliances).

SLA & Business Value: High reliability. Remote Support can confidently offer strong SLAs because there is a clear, supported escalation path to the vendor. The risk is low, but the internal commitment is slightly less absolute than VSL6.
VSL4

Supported (Third-Party Integrator)

Core Definition: The product has official support from the vendor, but Remote Support acts strictly as a third-party supporter or integrator, without a formal partnership.

Key Indicators

  • Standard vendor support channels available to the end-client or Remote Support
  • No privileged access, early beta access, or deep co-development ties

Typical Use Cases

Standard commercial off-the-shelf (COTS) software, common peripheral hardware, or widely used SaaS applications integrated into the client's environment.

SLA & Business Value: Moderate to high reliability. Remote Support can support the integration and basic troubleshooting, but complex bugs or deep architectural issues will rely entirely on the vendor's standard support timelines. SLAs must explicitly state this dependency.
VSL3

No Main Vendor Support (Community / Alternative Support)

Core Definition: The original vendor no longer provides official support (e.g., End-of-Life (EOL), End-of-Support (EOS), or purely community-driven open-source projects). However, support may be available from alternative sources, and Remote Support may choose to support it after thorough research.

Key Indicators

  • Reliance on community forums or third-party maintainers
  • Internal reverse-engineering may be required

Typical Use Cases

Legacy systems that a client refuses to upgrade, or niche open-source tools that lack a commercial backing entity.

SLA & Business Value: High risk. Support is provided on a “best effort” basis. SLAs for this tier must be heavily caveated (e.g., “resolution time is not guaranteed due to lack of vendor backing”). Clients must explicitly accept the risk of eventual obsolescence.
VSL2

No Vendor Support, No Baseline Knowledge (Research Only)

Core Definition: The product has no vendor support, and Remote Support currently possesses no internal knowledge base for it. However, Remote Support is willing to act as a consultant to research possibilities on the client's behalf.

Key Indicators

  • Obscure or highly customized technology
  • Abandoned legacy systems

Typical Use Cases

A client inherits a custom-built application from a previous IT provider and needs Remote Support to evaluate if it can be maintained.

SLA & Business Value: This is a billable consulting/research engagement, not a standard support ticket. There is no resolution SLA. The business value lies in providing the client with a definitive “go/no-go” assessment, often leading to a recommendation to migrate to a VSL4, VSL5, or VSL6 solution.
VSL1

Unsupported and Declined (The “No-Go” Zone)

Core Definition: The product is unsupported by the vendor, and Remote Support explicitly refuses to work on it.

Key Indicators

  • Known insurmountable technical issues
  • Severe security vulnerabilities
  • Documented objections based on disastrous past experiences

Typical Use Cases

Pirated software, fundamentally insecure legacy protocols (e.g., SMBv1, outdated TLS), or notoriously unstable hardware/software combinations that have historically caused data loss or massive SLA breaches.

SLA & Business Value: Zero risk. By drawing a hard line and declining to support VSL1 technologies, Remote Support protects its technical leadership team from wasting time, protects its reputation from inevitable failures, and protects the client from operating in a dangerously unstable environment.
3
Strategic Implementation

Making the Framework Actionable

Pre-Sales and Onboarding

During the initial assessment, every technology in the client's environment is audited and assigned a VSL rating. The client is presented with a clear report highlighting any VSL1, VSL2, or VSL3 risks, along with a roadmap to migrate to VSL4+ or VSL6 solutions.

SLA Contract Drafting

The Service Level Agreement explicitly references the VSL framework. For example: “Core infrastructure (VSL6) is covered by a 99.9% uptime guarantee with proportional service credits. Legacy third-party applications (VSL3) are supported on a best-effort basis and are excluded from uptime guarantees.”

Resource Allocation

Internal training budgets and R&D efforts are heavily skewed toward VSL6 and VSL5 technologies, ensuring the team maintains its “authoritative knowledge” and core competency.

Escalation Pathways

The VSL status dictates the escalation matrix. A VSL6 issue escalates directly to a dedicated vendor partner manager or internal L3/L4 architect. A VSL4 issue escalates to the vendor's public support portal.

Promise Only What You Can Keep

The VSL framework is a commitment to radical transparency — clients know exactly what they are buying, what the risks are, and that their core systems are backed by a partner committed to their success for the long haul.