# Vibe Coding a Database Lab: How I Built DBCanvas to Stop … | Percona Community

**URL:** <https://forums.percona.com/t/vibe-coding-a-database-lab-how-i-built-dbcanvas-to-stop-percona-community/41266>\
**Category:** Community website\
**Created:** [September 16, 2026, 6:39am UTC](https://forums.percona.com/t/vibe-coding-a-database-lab-how-i-built-dbcanvas-to-stop-percona-community/41266 "2026-09-16T06:39:06Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![daniil.bazhenov](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/daniil.bazhenov/32/62_2.png) [@daniil.bazhenov](https://forums.percona.com/u/daniil.bazhenov)\
**Post date:** [September 16, 2026, 6:39am UTC](https://forums.percona.com/t/vibe-coding-a-database-lab-how-i-built-dbcanvas-to-stop-percona-community/41266/1 "2026-09-16T06:39:06Z")

</div>

Percona gives us room to work on our own AI-assisted projects, and I used mine to fix a problem I kept running into. Every time I wanted to try a new database feature, debug something tricky, or reproduce a customer issue, I ended up rebuilding much of the same infrastructure: DNS, TLS, Docker networking, database topologies, users and test data. Over the years, I wrote scripts to automate this but I still found myself copying and pasting post-installation steps from one lab to the next.

* * *
This is a companion discussion topic for the original entry at [https://percona.community/blog/2026/09/16/vibe-coding-a-database-lab/](https://percona.community/blog/2026/09/16/vibe-coding-a-database-lab/)