Skip to content

Sponsorship

VirtFoundry is free and open source (Apache 2.0). Sponsorship helps fund development and documentation — without selling the codebase or transferring project leadership.

What sponsorship is

Sponsorship Commercial license / acquisition
Voluntary financial support Purchase of rights or company
Optional visibility (logo, thanks) Contractual exclusivity
May include agreed consulting hours Full control of the OSS project

Sponsors do not automatically get:

  • merge access to main
  • veto power over roadmap or architecture
  • ownership of code already released under Apache 2.0

The maintainer remains responsible for official releases and repository decisions unless a separate contract says otherwise.

Why sponsor?

  • Keep the control plane maintained (KubeVirt, Multus, Gateway API)
  • Prioritize integrations you care about (within agreed scope)
  • Support documentation and reproducible deployment tooling
  • Back an independent Kubernetes-native IaaS alternative

Tiers (draft — subject to maintainer confirmation)

These tiers describe intent; enable GitHub Sponsors or Open Collective when ready.

Supporter — from $5 / month

  • Name in SPONSORS.md (opt-in)
  • Our thanks in release notes when you start sponsoring
  • Logo on SPONSORS.md (linked)
  • Priority for bug triage (not feature veto)
  • Early visibility on release candidates

Bronze — from $200 / month

  • Everything in Sponsor
  • Quarterly 30-minute sync call (roadmap feedback, not binding)
  • Optional logo in documentation footer (when enabled)

Silver — from $500 / month

  • Everything in Bronze
  • Monthly 30-minute sync or async priority channel
  • Acknowledgment on the docs site sponsor block (when enabled)

Custom / Corporate

For SLA, on-prem install support, custom features, or training:

  • Contact the maintainer via GitHub Issues (label: sponsor) or email listed on the org profile
  • Scope, timeline, and price defined in a separate services agreement
  • Still no transfer of OSS copyright unless explicitly negotiated

What sponsors can expect

  • Transparency about how time is spent (releases, docs, integration testing)
  • Professional conduct and clear boundaries (support ≠ product management)
  • No guarantee that every feature request will be implemented

What we ask from sponsors

  • Respect Apache 2.0 and contributor community norms
  • Do not imply official endorsement without approval
  • Understand that public code remains open; paid work may target private branches or consulting deliverables only when contracted

How to sponsor

Setup in progress

Payment links will be added when GitHub Sponsors or Open Collective is configured.

Until then:

  1. Open a GitHub Issue with label sponsor, or
  2. Reach out via the maintainer contact on the virtfoundry organization profile

FAQ

Can a sponsor fork and compete?
Yes — Apache 2.0 allows that. Sponsorship supports the official project, not exclusivity.

Can I pay for a private fork?
Possible under a custom contract; the public main branch and tagged releases stay Apache 2.0 unless you negotiate a different arrangement for new work.

Does sponsoring buy merge rights?
No. Influence is through communication and optional priority, not repository admin.

Is this tax advice?
No. Consult your accountant for sponsorship vs. invoice treatment in your jurisdiction.