Overview
Baseshift gives developers and AI agents safe, production-like database environments. This connector lets Claude operate Baseshift end to end, so you can go from your existing database to a clone you can test against without leaving the conversation. What Claude can do with it: - Connect your existing database. Create a Baseshift Dub from your Postgres, MySQL, MariaDB, or MongoDB instance, or from the built-in demo database. Like dubbing a movie, dubbing your data gives you a prod-like version that's safe to share: a dub is your source database plus its masking and subset policies and a snapshot schedule. No infrastructure changes are required: point it at the database and run the source health check. - Keep data inside your network. With a self-hosted dub, replication, masking, and subsetting all run on your own Kubernetes cluster, so production data never leaves your environment. Claude returns the Helm values and install command; you run them. - Define masking and subset policies. Mask sensitive columns such as names or emails with generated values. Subset to just the slice you need, for example a single tenant or the last three months of data, so clones stay small and fast instead of carrying all of production. - Take snapshots. Create tagged snapshots that bake in the current policies, so every clone starts from fresh compliant data. - Spin up clones in seconds. Start server clones from any ready snapshot and release them when you are done. Each clone is a full, isolated database you can read and write freely. - Run clones as Docker images. Every snapshot can be pulled as a Docker image and connected to any workflow, from local development to CI. Good to know: clone connections for Baseshift Cloud dubs are opened by the Baseshift CLI on your machine over a secure tunnel. The connector prepares everything and returns the exact command to run. Managing dubs and policies requires a full organization user, clone operators can start clones.
