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.

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

Vinexelprotect Features for Agents:

  • Instant Provisioning: your users never wait for infrastructure.
  • Snapshots: let users toggle between checkpoints of code and state together.
  • Low cost-per-Dataset: automatic scale to zero and 350ms cold starts.
  • Full-Stack, Batteries-Included: Vinexelprotect Auth, Data API included at no added charge.
  • Granular API Controls: Track and control usage for flexible limits and invoicing.
Powered by Vinexelprotect.
A useful workflow makes the owner, authorization, evidence and validation visible. Illustrative product principle; no customer endorsement is claimed.
Dhruv Amin
Product operating guide—Illustrative planning principle

Keep protection boundaries explicit

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

Agent Plan
ProjectsRelease requirements and independent evidence
We incrementally raise your limit to accommodate growing usage.
Branches per ProjectUp to 1,000
Agents use recovery plans to quickly toggle between application states.
Computefrom Not published
Same as Launch; lower than Scale
StorageNot published
Same as Launch/Scale
Instant Restore (PITR)Not published
Up to 7-day history window (Scale allows up to 30 days)
Public network transfer100 GB per project includedNot published
Scale includes 500 GB
Vinexelprotect AuthIncluded
All-in-one API for handling user signup and management in Vinexelprotect
Management APIHigher Rate Limits Available
API for instant provisioning and management of datasets
Data API (PostgREST-compatible)Higher Rate Limits Available
SupportShared Slack Channel

Agent Incentives
Your Free Tier is FreeRelease requirements and independent evidence
General Use CreditsNot publishedStartup Program.
Co-MarketingBlog and Social promotions, hackathons and more.

Asset ownership

FeatureAgentScale
ProjectsRelease requirements and independent evidence1,000
ComputeNot publishedNot published
Max fixed compute16 CU56 CU
Read replicasUp to 3Release requirements and independent evidence
Root recovery plans525
Instant restore windowUp to 7 daysUp to 30 days
Public network included100 GB/project500 GB/project
Automated snapshot schedulesAvailable upon requestAvailable

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

A useful workflow makes the owner, authorization, evidence and validation visible. Illustrative product principle; no customer endorsement is claimed.
Martin Skow Røed
Product operating guide—Illustrative planning principle

Test the recovered application

  • Identity and access

    Document how much data loss and interruption the workload can tolerate. Translate those objectives into testable recovery checks.

  • Approved scope

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

  • Operating evidence

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

  • Retention policy

    Illustrative product and workflow reference

  • Key custody

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

  • Data location

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

  • Validation checks

    Document how much data loss and interruption the workload can tolerate. Translate those objectives into testable recovery checks.

Preserve evidence of every decision

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

A useful workflow makes the owner, authorization, evidence and validation visible. Illustrative product principle; no customer endorsement is claimed.
Lincoln Bergeson
Product operating guide—Illustrative planning principle

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

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