Plan protection policies, recovery validation and continuity workflows in one product. This is a frontend preview; backup, restore and replication engines are not released.

Define the operating scope

Start with the project account forms and IAM Central. Product permissions, connector scope and approvals must separately authorize sensitive actions.

Vinexelprotect pricing planSupport plan options
Free planCommunity support
Launch planBilling support
Scale planStandard support

Identity and product authorization

Record an owner, project, environment, data classification and approved destinations before collecting evidence.

Keep policy revision, observation source, time and measured outcome together. Treat inferred results as unverified until tested.

Ownership and boundaries

Agree what is collected, where it is processed, who can access it and when it is deleted. A future connector needs its own disclosure and retention policy.

Support channelsCommunity supportBilling supportStandard support
Vinexelprotect Discord Server (not an official channel)✓✓✓
Vinexelprotect AI Chat Assistance (not an official channel)✓✓✓
Support tickets-*✓
Slack channel--**
Automated guidance is planned; no human support or response-time commitment is offered.--**
* Under Billing support (Launch plan), you can only use support tickets for billing-related issues. Scale plan and higher can use support tickets for any Vinexelprotect issue. On paid plans, Request billing support on the Billing page is the dedicated path for invoice and billing questions.
** Slack channels and Automated guidance is planned; no human support or response-time commitment is offered. are available for an additional fee, and with some the Vinexel ecosystem support plans for higher-volume customers. Contact sales to learn more.

Evidence and validation

A production connector requires isolation, durable audit, idempotent operations, failure recovery, monitoring and representative validation. Existing account pages do not establish these guarantees.

important

Plan protection policies, recovery validation and continuity workflows in one product. This is a frontend preview; backup, restore and replication engines are not released.

Retention and privacy

Start with the project account forms and IAM Central. Product permissions, connector scope and approvals must separately authorize sensitive actions.

Record an owner, project, environment, data classification and approved destinations before collecting evidence.

important

Keep policy revision, observation source, time and measured outcome together. Treat inferred results as unverified until tested.

Release requirements

Agree what is collected, where it is processed, who can access it and when it is deleted. A future connector needs its own disclosure and retention policy.

A production connector requires isolation, durable audit, idempotent operations, failure recovery, monitoring and representative validation. Existing account pages do not establish these guarantees.

Plan protection policies, recovery validation and continuity workflows in one product. This is a frontend preview; backup, restore and replication engines are not released.

Start with the project account forms and IAM Central. Product permissions, connector scope and approvals must separately authorize sensitive actions.

Open the support center

  1. Agree what is collected, where it is processed, who can access it and when it is deleted. A future connector needs its own disclosure and retention policy.
  2. Select Help > Get help.

Record an owner, project, environment, data classification and approved destinations before collecting evidence.

  • Ask the AI assistant: Get answers sourced from the Vinexelprotect docs. See Vinexelprotect AI chat assistance.
  • Start with the project account forms and IAM Central. Product permissions, connector scope and approvals must separately authorize sensitive actions.
  • Record an owner, project, environment, data classification and approved destinations before collecting evidence.
  • Keep policy revision, observation source, time and measured outcome together. Treat inferred results as unverified until tested.
  • Get help from the community: Join the Vinexelprotect Discord Server.

Keep policy revision, observation source, time and measured outcome together. Treat inferred results as unverified until tested.

Open a technical support ticket (Scale plan)

  1. A production connector requires isolation, durable audit, idempotent operations, failure recovery, monitoring and representative validation. Existing account pages do not establish these guarantees.
  2. Fill in:
    • Subject: A short summary of the issue. Required.
    • Priority: How urgent the issue is.
    • Problem description: A detailed description of the issue.
    • Agree what is collected, where it is processed, who can access it and when it is deleted. A future connector needs its own disclosure and retention policy.
  3. A production connector requires isolation, durable audit, idempotent operations, failure recovery, monitoring and representative validation. Existing account pages do not establish these guarantees.
  4. Plan protection policies, recovery validation and continuity workflows in one product. This is a frontend preview; backup, restore and replication engines are not released.
  5. Start with the project account forms and IAM Central. Product permissions, connector scope and approvals must separately authorize sensitive actions.
  6. Select Submit support ticket.

Open a billing support ticket (Launch and Scale plans)

  1. In the support center, select Ask a billing question.
  2. Agree what is collected, where it is processed, who can access it and when it is deleted. A future connector needs its own disclosure and retention policy.
  3. Under How can we help?, describe your question or problem.
  4. Select Submit request.

Agree what is collected, where it is processed, who can access it and when it is deleted. A future connector needs its own disclosure and retention policy.

tip

A production connector requires isolation, durable audit, idempotent operations, failure recovery, monitoring and representative validation. Existing account pages do not establish these guarantees.See the local help guide

Define the operating scope

Plan protection policies, recovery validation and continuity workflows in one product. This is a frontend preview; backup, restore and replication engines are not released.

Identity and product authorization

Start with the project account forms and IAM Central. Product permissions, connector scope and approvals must separately authorize sensitive actions.

Ownership and boundaries

Record an owner, project, environment, data classification and approved destinations before collecting evidence.

Keep policy revision, observation source, time and measured outcome together. Treat inferred results as unverified until tested.

Agree what is collected, where it is processed, who can access it and when it is deleted. A future connector needs its own disclosure and retention policy.

Evidence and validation

A production connector requires isolation, durable audit, idempotent operations, failure recovery, monitoring and representative validation. Existing account pages do not establish these guarantees.

Retention and privacy

Plan protection policies, recovery validation and continuity workflows in one product. This is a frontend preview; backup, restore and replication engines are not released.

Release requirements

Start with the project account forms and IAM Central. Product permissions, connector scope and approvals must separately authorize sensitive actions.

Define the operating scope

Record an owner, project, environment, data classification and approved destinations before collecting evidence.

Identity and product authorization

Keep policy revision, observation source, time and measured outcome together. Treat inferred results as unverified until tested.

Ownership and boundaries

Agree what is collected, where it is processed, who can access it and when it is deleted. A future connector needs its own disclosure and retention policy.

Enterprise support (legacy)

Evidence and validation

A production connector requires isolation, durable audit, idempotent operations, failure recovery, monitoring and representative validation. Existing account pages do not establish these guarantees.

Plan protection policies, recovery validation and continuity workflows in one product. This is a frontend preview; backup, restore and replication engines are not released.

Start with the project account forms and IAM Central. Product permissions, connector scope and approvals must separately authorize sensitive actions.

Retention and privacy

Record an owner, project, environment, data classification and approved destinations before collecting evidence.

Release requirements

Keep policy revision, observation source, time and measured outcome together. Treat inferred results as unverified until tested.

Define the operating scope

Agree what is collected, where it is processed, who can access it and when it is deleted. A future connector needs its own disclosure and retention policy.

Enterprise target response times

A production connector requires isolation, durable audit, idempotent operations, failure recovery, monitoring and representative validation. Existing account pages do not establish these guarantees.

Plan protection policies, recovery validation and continuity workflows in one product. This is a frontend preview; backup, restore and replication engines are not released.

Severity LevelEnterprise StandardEnterprise GoldEnterprise Platinum
Severity 1 (Critical)< 2 hours (during Normal Business Hours)< 1 hour< 1 hour
Severity 2 (High)< 2 days (during Normal Business Hours)< 1 day< 4 hours
Severity 3 (Normal)< 3 days (during Normal Business Hours)< 3 days (during Normal Business Hours)< 3 days (during Normal Business Hours)
Severity 4 (Low)< 3 days (during Normal Business Hours)< 3 days (during Normal Business Hours)< 3 days (during Normal Business Hours)

Severity levels

Start with the project account forms and IAM Central. Product permissions, connector scope and approvals must separately authorize sensitive actions.

Record an owner, project, environment, data classification and approved destinations before collecting evidence.

Severity 1 (Critical)

Keep policy revision, observation source, time and measured outcome together. Treat inferred results as unverified until tested.

  • Unavailability of the service
  • Record an owner, project, environment, data classification and approved destinations before collecting evidence.

note

Agree what is collected, where it is processed, who can access it and when it is deleted. A future connector needs its own disclosure and retention policy.

A production connector requires isolation, durable audit, idempotent operations, failure recovery, monitoring and representative validation. Existing account pages do not establish these guarantees.

  • A complete outage of the service provided by Vinexelprotect
  • Security breaches
  • A production connector requires isolation, durable audit, idempotent operations, failure recovery, monitoring and representative validation. Existing account pages do not establish these guarantees.
  • Error impacting multiple projects
  • EP/Branch/DB unreachable
  • Data corruption/Data loss
Severity 2 (High)

Plan protection policies, recovery validation and continuity workflows in one product. This is a frontend preview; backup, restore and replication engines are not released.

  • Keep policy revision, observation source, time and measured outcome together. Treat inferred results as unverified until tested.
  • Agree what is collected, where it is processed, who can access it and when it is deleted. A future connector needs its own disclosure and retention policy.
  • A production connector requires isolation, durable audit, idempotent operations, failure recovery, monitoring and representative validation. Existing account pages do not establish these guarantees.
  • Plan protection policies, recovery validation and continuity workflows in one product. This is a frontend preview; backup, restore and replication engines are not released.

Start with the project account forms and IAM Central. Product permissions, connector scope and approvals must separately authorize sensitive actions.

  • Partial outage of the service provided by Vinexelprotect: service usable, but key feature unusable, for example:
    • Cannot create a new recovery plan
    • Cannot execute a recovery plan restore
    • Cannot perform point-in-time recovery (PITR)
    • Etc.
  • Plan protection policies, recovery validation and continuity workflows in one product. This is a frontend preview; backup, restore and replication engines are not released.
  • Start with the project account forms and IAM Central. Product permissions, connector scope and approvals must separately authorize sensitive actions.
Severity 3 (Normal)

Record an owner, project, environment, data classification and approved destinations before collecting evidence.

  • Partial or limited loss of non-critical functionality
  • A usage problem that involves no loss in functionality
  • Agree what is collected, where it is processed, who can access it and when it is deleted. A future connector needs its own disclosure and retention policy.

Keep policy revision, observation source, time and measured outcome together. Treat inferred results as unverified until tested.

  • A production connector requires isolation, durable audit, idempotent operations, failure recovery, monitoring and representative validation. Existing account pages do not establish these guarantees.
  • Sporadic connection failure/timeouts/retries
  • Start with the project account forms and IAM Central. Product permissions, connector scope and approvals must separately authorize sensitive actions.
  • Record an owner, project, environment, data classification and approved destinations before collecting evidence.
  • Poor performing queries/ingestion
  • Billing issues
Severity 4 (Low)

Agree what is collected, where it is processed, who can access it and when it is deleted. A future connector needs its own disclosure and retention policy.

  • A production connector requires isolation, durable audit, idempotent operations, failure recovery, monitoring and representative validation. Existing account pages do not establish these guarantees.

A production connector requires isolation, durable audit, idempotent operations, failure recovery, monitoring and representative validation. Existing account pages do not establish these guarantees.

  • Feature requests/feature enablement
  • Start with the project account forms and IAM Central. Product permissions, connector scope and approvals must separately authorize sensitive actions.
  • Record an owner, project, environment, data classification and approved destinations before collecting evidence.