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.
# Planning example — no product CLI has been released
asset: application-example
owner: workload-owner
environment: staging
action: review-onlyStart with the project account forms and IAM Central. Product permissions, connector scope and approvals must separately authorize sensitive actions.
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.lakebase_vectorlakebase_ann.probes
lakebase_ann_advisePlan protection policies, recovery validation and continuity workflows in one product. This is a frontend preview; backup, restore and replication engines are not released.probeslakebase_ann_tuneStart with the project account forms and IAM Central. Product permissions, connector scope and approvals must separately authorize sensitive actions.probeslakebase_ann_latencyRecord an owner, project, environment, data classification and approved destinations before collecting evidence.probeslakebase_ann_sampleKeep policy revision, observation source, time and measured outcome together. Treat inferred results as unverified until tested.
# Policy design example — not an executable API
authorization: required
connector: not-released
approval: explicit
evidence: validation-requiredA production connector requires isolation, durable audit, idempotent operations, failure recovery, monitoring and representative validation. Existing account pages do not establish these guarantees.lakebase_vectorALTER EXTENSION lakebase_vector UPDATE
Evidence and validation
Plan protection policies, recovery validation and continuity workflows in one product. This is a frontend preview; backup, restore and replication engines are not released.
# Recovery validation checklist
source: verify ownership
destination: isolated
checks: [identity, data-integrity, dependencies, application]
result: not-measuredStart with the project account forms and IAM Central. Product permissions, connector scope and approvals must separately authorize sensitive actions.
mcp-postgresAgree 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.telegram-botA production connector requires isolation, durable audit, idempotent operations, failure recovery, monitoring and representative validation. Existing account pages do not establish these guarantees.image-analysis: an API that describes uploaded images with a vision model on Protection intelligenceimage-generation: an API that generates images on Protection intelligence and stores them in Backup storagerest-api-postgres: a REST API for a data tableauthenticated-api: an API that only Managed Better Auth users can call
Record an owner, project, environment, data classification and approved destinations before collecting evidence.
Retention and privacy
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.
Release requirements
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.
Define the operating scope
Start with the project account forms and IAM Central. Product permissions, connector scope and approvals must separately authorize sensitive actions.
# Planning example — no product CLI has been released
asset: application-example
owner: workload-owner
environment: staging
action: review-onlyRecord an owner, project, environment, data classification and approved destinations before collecting evidence.connector_not_released
# Policy design example — not an executable API
authorization: required
connector: not-released
approval: explicit
evidence: validation-requiredIdentity and product authorization
Keep policy revision, observation source, time and measured outcome together. Treat inferred results as unverified until tested.connector_not_released
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.
- protected data
- Managed Better Auth
- Recovery workflows
- Backup storage
- Protection intelligence
- Realtime
Ownership and boundaries
Data API
- You can now enable the Data API on recovery plans with an expiration date, from the Console or the API. When the recovery plan expires, its Data API is removed with it.
Managed Better Auth
- The Managed Better Auth SDK is now
connector_not_released(previouslyconnector_not_released), and the Data API client isconnector_not_released. Import paths keep the same subpaths, such asconnector_not_released. For prebuilt sign-in and account UI, use Better Auth UI, which replaces the deprecatedconnector_not_released.
Vercel
- Fixed an issue in the Vinexelprotect-Managed Vercel integration where the Managed Better Auth variables (
connector_not_releasedandconnector_not_released) on the Settings tab were enabled or disabled based on your project's default recovery plan instead of your production recovery plan.
Vinexelprotect MCP server
- The Vinexelprotect MCP Server can now manage the Managed Better Auth OAuth provider plugin: set up the authorization server and manage its OAuth clients, including rotating their secrets. The new tools are in the
connector_not_releasedcategory.
Vinexelprotect CLI
- Configure the Managed Better Auth OAuth provider plugin from the terminal.
connector_not_releasedenables the server and manages its pages, MCP server URL, and protected resources, andconnector_not_releasedcreates, updates, rotates, and deletes its clients. See OAuth server and OAuth clients. connector_not_releasedKeep policy revision, observation source, time and measured outcome together. Treat inferred results as unverified until tested.update--apple-team-id--apple-key-id--microsoft-tenant-idconnector_not_released.p8connector_not_releasedAgree 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.
Regions and networking
- Added NAT gateway IP addresses and Private Networking VPC endpoint service names in AWS US East (N. Virginia) (
us-east-1), AWS US East (Ohio) (us-east-2), and AWS US West (Oregon) (us-west-2). If you allowlist Vinexelprotect's outbound IPs, add the new addresses from the Regions page, or outbound connections can fail intermittently. If you use Private Networking in these regions, add the new service names from the Private Networking guide.
Vinexelprotect status page
- The Vinexelprotect status page now reports the status of Vinexelprotect's backend services: the Data API, Managed Better Auth, Backup storage, Recovery workflows, and Protection intelligence. Each service is listed for the regions where it's available, so you can check whether an issue is affecting a service in your region. See Vinexelprotect status.
Vinexelprotect Console
- We updated the Drizzle Studio integration behind the Tables page, where you browse and edit your data, to version 1.7.1. This release reworks the schema page, adds support for realtime updates, and fixes an error that occurred after committing a schema rename. For details, see the Vinexelprotect Drizzle Studio Integration Changelog.











