PerSQL for GitLab
A SQLite branch per merge request.
Connect your projects and every MR gets an isolated branch database (preview-mr-<iid>) — spun up on open, cleaned up on merge or close. Real data for review apps, never shared with production. Billed per use — no per-database fee.
How it works
Add to GitLab
Authorize and connect your projects to your PerSQL namespace.
Branch per MR
preview-mr-<iid> spawns when an MR opens and is dropped on merge or close.
Use it in CI
Run migrations and tests against the branch from .gitlab-ci.yml.
Per-MR databases over MCP
Point a coding agent at the GitLab MCP. mr_recipe returns the .gitlab-ci.yml snippet that spawns or resets the per-MR branch; mr_list shows the active ones. Branches carry the parent's schema, not its rows, so they're cheap until written to.
https://gitlab.persql.com/mcpAuthenticate with a PerSQL bearer token. Tools: mr_list, mr_recipe.