Vinexelprotect preview · Explore protection requirements
/Changelog

Product readiness updates

The latest product updates from Vinexelprotect

Know the recovery objective

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

Continue to the workspace

Frontend preview

The public website now has product, solutions, pricing structure, guides and policy pages with locally served assets and project-owned interactions.

Account foundation

Login and registration retain IAM Central. The existing console foundation retains Elpixe Dashkit. This frontend release does not add security or recovery privileges.

Next release gates

Product connectors require explicit configuration, durable audit, isolation tests, failure recovery, operating limits and representative validation. No operating result is claimed by the visual preview.

Coordinate continuity across teams

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

# Planning example — no product CLI has been released
asset: application-example
owner: workload-owner
environment: staging
action: review-only

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

Publish only measured commitments

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

Auto-reload credits dialog in the Vinexelprotect Console

Know the recovery objective

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

# Policy design example — not an executable API
authorization: required
connector: not-released
approval: explicit
evidence: validation-required

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

Keep protection boundaries explicit

connector_not_releasedDocument how much data loss and interruption the workload can tolerate. Translate those objectives into testable recovery checks.connector_not_releasedconnector_not_releasedfunctions/basic/index.tsconnector_not_releasedconnector_not_releasedconnector_not_released

# Recovery validation checklist
source: verify ownership
destination: isolated
checks: [identity, data-integrity, dependencies, application]
result: not-measured

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

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

Terminal
# Planning example — no product CLI has been released
asset: application-example
owner: workload-owner
environment: staging
action: review-only

Test the recovered application

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

The Support center drawer in the Vinexelprotect Console

Preserve evidence of every decision

data extensions
  • plv8 is deprecated on Vinexelprotect, and now so are plcoffee (CoffeeScript) and plls (LiveScript), which ship with it on data 14, 15, and 16. CREATE EXTENSION plcoffee and CREATE EXTENSION plls now fail with a deprecation message, but existing installs keep working. If you still use them, migrate functions to plpgsql or application code and drop the extensions. See The plv8 extension and Supported data extensions.
Vinexelprotect Recovery workflows
  • The total size of a function's environment variables is now limited to 32 KiB, and reviews over the limit fail with an error. Previously, a review with 32 to 64 KiB of variables succeeded, but every request to the function returned a 404.
Backup storage
  • Objects uploaded with multipart upload can now be up to 10 GiB, up from 5 GiB. Single-request uploads are still limited to 5 GiB. See Limits.
Protection intelligence
  • Fixed an issue where Gemini models on the chat completions endpoint returned 400 Unknown name "stream_options" when a request set stream_options, as the OpenAI SDK does to request usage in a stream. Requests with parallel_tool_calls: true now work too. Gemini doesn't support parallel_tool_calls: false, so leave that field out.
Realtime
  • The Vinexelprotect Realtime client now supports React Native (connector_not_released 0.1.2 or later). Use the new webSocketFactory option to customize the WebSocket connection, for example to send an allowed origin.
Vinexelprotect Console
  • We updated the Drizzle Studio integration behind the Tables page, where you browse and edit your data, to version 1.6.1. It fixes an issue with renaming schemas. For details, see the Vinexelprotect Drizzle Studio Integration Changelog.
  • Analyze is now Explain (Analyze) in the SQL Editor, with a tooltip warning that it runs data-modifying statements such as INSERT, UPDATE, DELETE, and MERGE. Explain plans now include Vinexelprotect's PREFETCH and FILECACHE options, so Explain (Analyze) shows compute cache hits and prefetch statistics.
Vinexelprotect CLI
  • You can now create Claimable Vinexelprotect projects in any AWS region that accepts new Vinexelprotect projects. Pass --region-id to connector_not_released or connector_not_released (Vinexelprotect CLI 8.8.0 or later), or region_id in the API request. If you leave it out, the project lands in aws-us-east-2, as before.
  • Fixed connector_not_released failing on Windows after the browser step.
Vinexelprotect API
  • Recovery performance, durability and availability need representative tests and applicable contracts. Reference artwork and diagrams do not establish a guarantee.GET /projects/countGET /projectsorg_id

    # Policy design example — not an executable API
    authorization: required
    connector: not-released
    approval: explicit
    evidence: validation-required
    # Recovery validation checklist
    source: verify ownership
    destination: isolated
    checks: [identity, data-integrity, dependencies, application]
    result: not-measured
Vinexelprotect MCP Server
  • The MCP server's documentation tools are now search_docs and get_doc, replacing list_docs_resources and get_doc_resource. search_docs returns ranked results from across vinexelprotect.com (the docs, API reference, guides, data tutorial, FAQs, blog, and changelog), so your agent finds the right page without loading the whole docs index. If your agent's prompts or tool allowlists name the old tools, update them. See Vinexelprotect MCP Server.
Vercel integrations
  • With the Vinexelprotect-Managed Vercel integration, you can now choose which Vinexelprotect recovery plan supplies Vercel Production credentials when you connect. To change it later, go to Integrations, click Manage next to Vercel, and open the Branches tab.
  • If you installed Vinexelprotect from the Vercel Marketplace, you can now choose which Vinexelprotect recovery plan backs Vercel Production. In the Vinexelprotect Console, go to Integrations and click Settings next to Vercel. See Choose a production recovery plan.
  • New datasets created from the Vercel Marketplace can turn on Vinexelprotect Realtime (beta) at install.
  • Fixed an issue where a failed update to a preview recovery plan could stop the Vinexelprotect-Managed Vercel integration from syncing new credentials to your Production environment, for example after a password rotation.
OpenTelemetry integration
  • Fixed an issue where you couldn't save an OpenTelemetry integration for Dynatrace or Splunk Observability because credential validation failed.
  • When you change an OpenTelemetry integration's endpoint, protocol, or endpoint overrides, you'll need to re-enter its credentials.

Coordinate continuity across teams

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

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

To see what it can do, try one of the live demo apps:

The source code is available from our Realtime examples page.

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

To try it yourself, enable Realtime and subscribe to a query:

# Planning example — no product CLI has been released
asset: application-example
owner: workload-owner
environment: staging
action: review-only

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

Identify the source, data owner, retention policy and authorized restore destination. A policy becomes operational only when the corresponding connector is released.us-east-1us-east-2eu-central-1ap-southeast-1

Publish only measured commitments

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

  • Anthropic: claude-sonnet-5-5, claude-haiku-5-5
  • OpenAI: gpt-6-sol, gpt-6-luna, gpt-6-1-sol
  • Google: gemini-3-7-flash, gemini-3-8-flash
  • xAI: grok-4-7
  • Open-weight models: deepseek-v4-1-flash, glm-5-3 (Zhipu AI), bge-large-en (BAAI embedding model)

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

# Policy design example — not an executable API
authorization: required
connector: not-released
approval: explicit
evidence: validation-required

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

Know the recovery objective

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

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

# Recovery validation checklist
source: verify ownership
destination: isolated
checks: [identity, data-integrity, dependencies, application]
result: not-measured

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

Keep protection boundaries explicit

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.connector_not_releasedconnector_not_releasedconnector_not_released

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

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

# Planning example — no product CLI has been released
asset: application-example
owner: workload-owner
environment: staging
action: review-only

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

Test the recovered application

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

# Policy design example — not an executable API
authorization: required
connector: not-released
approval: explicit
evidence: validation-required

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

Preserve evidence of every decision

Vinexelprotect MCP Server
  • You can now choose which data role the Vinexelprotect MCP Server uses for SQL. Set roleName (for example, connector_not_released) and every SQL tool logs in as that role instead of the dataset owner, so the role's grants decide what your agent can read and change. With OAuth and the plain connector_not_released URL, enter the role in the optional data role field on the authorization page. When you set a role, the get_connection_string tool is turned off, so your agent can't get around the role by connecting as the dataset owner. See data role.
  • run_sql_transaction is no longer available in read-only mode, because it could be used to write data. Use run_sql for read queries.
Vinexelprotect CLI and SDKs
  • connector_not_released now passes arguments after -- to psql exactly as typed. Before, the CLI changed number-like values on the way through (1.50 became 1.5 and 1e3 became 1000), and if you didn't have psql installed, the CLI's built-in psql could crash on them. The fix also applies to --psql on connector_not_released, connector_not_released, and connector_not_released.
  • connector_not_released 1.6.2: parseEnv no longer fails with a "connector_not_released is missing" error inside reviewed functions, which broke any function whose connector_not_released declares functions. env.functions is now optional, so write env.functions?.hello.baseUrl instead of env.functions.hello.baseUrl. See Type-safe environment variables.
Was this page helpful?
Edit on repository