FAQ

Yes. You can deploy Baseshift inside your own infrastructure or use the Baseshift cloud.

In self-hosted mode, the Baseshift agent and replication server run entirely within your environment, and production data never leaves your network. In both self-hosted and hosted deployments, all access is encrypted, strictly controlled, and fully audited.

You can also apply masking policies to anonymize sensitive fields before clones are created.

Yes. With subsetting policies you can exclude entire tables from getting copied, or filter rows based on specific fields and values. This allows you to run clones with only specific tenants, or just the last month of data.

Yes. Baseshift includes a PII scanner that helps detect columns containing potentially sensitive data, so you can apply masking policies automatically.

You can also define your own masking rules to anonymize specific fields before clones are created, ensuring development and AI workflows run on safe, compliant data.

PostgreSQL, MySQL, MariaDB, MongoDB, DocumentDB are all supported with more databases on the roadmap. Feel free to reach out for more details.

Yes, AI agents need safe, writable environments to experiment and iterate quickly. Baseshift provides fresh database sandboxes on demand, so agents can run parallel workflows without risking production data.

When you launch a clone, you receive a standard database connection string and can connect using your usual tools or CI pipelines to a fully isolated, writable environment.

Clones can also run locally as Docker images and integrate directly into your existing infrastructure.

Yes. You can start with a free plan to test production database cloning in your environment before committing to a paid tier.