Zero ops tickets
No more "can someone spin up a DB?" in Slack. Engineers get environments through CI or the API.
DevOps solutionsNo more provisioning tickets. No more shared staging. Every PR, every CI run, every deployment gets its own isolated database: webhook in, clone out, teardown on merge.
Plug in GitHub Actions, Jenkins, GitLab CI, or any tool that speaks REST. One integration, every pipeline gets a production-identical clone URL injected automatically.
View integration examples# .github/workflows/ci.yml
- name: Clone DB for PR
uses: guepard/clone-action@v2
with:
source: production
name: pr-${{ github.event.number }}
token: ${{ secrets.GUEPARD_TOKEN }}
auto_teardown: on_merge
- name: Run tests
env:
DATABASE_URL: ${{ steps.clone.outputs.url }}
run: npm testZero manual provisioning. Every pipeline automated.
The change
Ops tickets
"Can someone provision a staging DB?"
Shared staging
Everyone steps on each other's changes
Manual teardown
Orphaned environments pile up and cost money
Schema drift
Invisible until it breaks production
Zero tickets
Every environment provisioned automatically via API
Clone-per-PR
Every pull request gets its own isolated database
Auto-teardown
Clones destroy themselves on merge or TTL expiry
Drift detection
Caught automatically in every PR pipeline
Plug into any automation tool
Features
PR opened? Clone created. PR merged? Clone destroyed. Connect GitHub, GitLab, or Bitbucket webhooks and never provision manually again.
Every operation is an API call or CLI command. gfs clone, gfs teardown. Script it in bash, call it from Jenkins, pipe it anywhere.
Every pull request gets its own production-identical database. No shared staging. No conflicts. Automatic isolation for every branch.
Set a TTL, trigger on merge, or let CI handle it. Environments self-destruct when done. No orphaned databases. No surprise bills.
Any database, any size. Cloned from production via copy-on-write in under 5 seconds. No pg_dump. No restore. No waiting.
Developers self-serve environments through CI or the API. No more "can someone spin up a DB?" in Slack. No more blocked pipelines.
Developers get realistic data without production credentials. PII masking ensures compliance while keeping data shapes real.
Docker-based engine. Self-host on your infra or use the managed cloud. Works wherever your CI runner lives.
GitHub Actions, GitLab CI, Jenkins, CircleCI, Buildkite, Argo CD. If it can call a REST API, it works with Guepard.
“We eliminated every ops ticket related to database provisioning. CI handles everything now. Engineers never wait for a database.”
Sarah R.
Engineering Lead, Series B SaaS company
Fork prod from GitHub Actions, Helm, or the API: hundreds of envs per pipeline, zero copy overhead, TTL cleanup built in.
CLI + API walkthrough included