SynVirt Market Positioning — Internal Context

Synced read-only from /home/synnet/mirrors/synvirt-product/docs/internal/POSITIONING.md. Edit at the source, not here.

SynVirt Market Positioning — Internal Context

Status: Internal reference document. NOT a public-facing artifact of the project. Purpose: onboarding, strategic discussions, and context for contributors and tooling.

---

Target market

• Small and medium businesses (SMB) and managed service providers (MSPs) in Mexico and the rest of Latin America.
• Customers that today run a mix of:
  • Proprietary commercial hypervisors with expensive per-socket licensing.
  • Community / open-source hypervisor platforms without a paid support contract, where the operator is also the escalation point.
  • Aging single-node deployments that need a credible 2-node HA story without buying a SAN.

Competitive frame

SynVirt competes in the same buying conversations as:

• Commercial hypervisor suites targeting SMB virtualization (e.g. Proxmox VE, VMware vSAN, StorMagic SvSAN, Scale Computing HC3, VMware vSphere Essentials).
• Open-source stacks assembled by the operator (e.g. plain KVM + DRBD + custom scripts).

The intended differentiation is:

• UX: console-first, operator-friendly TUI on first boot; a clean web wizard afterwards. The reference point for “what ‘easy’ looks like” is the kind of turnkey appliance UX that HC3-style products offer.
• Openness: built on standard open-source components (Debian 13 Trixie, ZFS on root, KVM / Cloud Hypervisor, DRBD + LINSTOR, OVN, etcd). Operators can introspect every layer. No proprietary kernel module chain, no black-box appliance.
• Price: tiered commercial licensing per CPU socket, positioned at roughly half the street price of the proprietary incumbents.

Why this lives in docs/internal/

The documentation policy for the main repo (see memory/feedback_no_third_party_mentions.md in the team-shared memory) forbids naming competing products in code, comments, ADRs, public docs, or commit messages. That policy keeps the public face of the project brand-clean and reduces legal-risk surface.

Strategic framing, on the other hand, legitimately needs to reference those products — you cannot reason about pricing, UX targets, or sales objections in the abstract. This file is the allowed place to do that reasoning. It is not shipped with the product and is not surfaced in customer-facing artifacts.

If you find yourself tempted to paste a chunk of this file into a README, ADR, or commit message: stop and describe the technical property instead.