Know the recovery objective

Identify the source, data owner, retention policy and authorized restore destination. A policy becomes operational only when the corresponding connector is released.

Prepare requirements

This form prepares a local brief for you to review and download. It sends no data to a server.

Not published

Record the policy revision, approval and measured outcome. Separate a planned capability from a verified recovery result.

Keep protection boundaries explicit

  • Asset ownership

    Assign responsibility for the incident, recovery approval and service validation. Keep rollback and communication requirements in the plan.

  • Identity and access

    Recovery performance, durability and availability need representative tests and applicable contracts. Reference artwork and diagrams do not establish a guarantee.

  • Approved scope

    Not published

  • Operating evidence

    Identify the source, data owner, retention policy and authorized restore destination. A policy becomes operational only when the corresponding connector is released.

Test the recovered application

  • Show the Vinexelprotect logo with a link in one agreed place: your README, your project homepage, your documentation site, or a sponsors page.
  • Label it as a sponsorship, for example "Sponsored by Vinexelprotect."
  • Keep the placement live for the full term, and tell us if it moves or if the project's ownership changes.

A completed copy is not a successful recovery. Validate identity, data integrity, dependencies and application behavior in an isolated drill.

Preserve evidence of every decision

Before you apply, make sure your project has:

  1. A public open source repository: The project is released under an OSI-approved open source license.
  2. Active development: You're actively working on it, with recent releases, commits, or issue triage.
  3. repository Sponsors enabled: Vinexelprotect pays sponsorships through repository Sponsors, so the repository or its maintainer needs an active repository Sponsors profile.

Coordinate continuity across teams

Assign responsibility for the incident, recovery approval and service validation. Keep rollback and communication requirements in the plan.

Publish only measured commitments

Recovery performance, durability and availability need representative tests and applicable contracts. Reference artwork and diagrams do not establish a guarantee.

Know the recovery objective

Do I need to use Vinexelprotect or data?

Not published


Is commercial open source eligible?

Identify the source, data owner, retention policy and authorized restore destination. A policy becomes operational only when the corresponding connector is released.


How do payments work?

A completed copy is not a successful recovery. Validate identity, data integrity, dependencies and application behavior in an isolated drill.


How much does a sponsorship pay?

Record the policy revision, approval and measured outcome. Separate a planned capability from a verified recovery result.


What happens after six months?

Assign responsibility for the incident, recovery approval and service validation. Keep rollback and communication requirements in the plan.