devqasandbox
Independent by design.
Each clone gets its own SQL Server container, host port, and generated password. Changes in one clone stay in that clone.
Development. QA. Your next experiment.SQL Server cloning. On your infrastructure.
ONE DATABASE.
ROOM TO BUILD.
Restore once. Give every developer an isolated clone to build, test, and start again.
One base.Restored once. Kept immutable.
Your own clone.Separate container. Separate changes.
eddb create dev --base team-base
Built for the stack
you already know.
SQL Server2022 & 2025
Ubuntu24.04 LTS
Your infrastructureOne Linux VM
A shared starting point.
Space to make it your own.
Build a reusable base from your backup. Create separate SQL Server environments from that base, with storage that grows as data changes.
ONE BASE. EVERY POSSIBILITY.01 / RESTORE
REUSABLE BASEteam-base
Read-only
devFeature work
qaTest freely
sandboxTry an idea
eddb / terminal
eddb build-base team-base --bak ./seed.bak --size 200GRestore a backup into an immutable base. Your clones will start from this same point.
Examples assume an installed, licensed host with storage initialized. Read the setup guide
Your next idea
needs its own database.
Give development and testing their own space, without restoring the same backup for every new environment.
Blue: shared baseOrange: clone changes
More room.
Less duplication.
LVM thin snapshots share the base’s data blocks. Additional storage grows with each clone’s changes.
Monitor real capacity witheddb usage.
Your machine.
Your boundaries.
Set CPU and memory limits per clone. Keep the binary, state, and database environments on a Linux VM you control.
Explore the requirementsThe freedom to try again
Test the migration.
Break the branch.
Keep the starting point.
Refresh a clone from its base when an experiment is done. Its port and password stay the same, so your connection settings can too.
Explore refreshKnow what you’re running.
Clear setup, practical commands, and a defined operating boundary.
What can I use eddb for?
eddb is licensed for internal development and testing, including isolated feature work, QA, and migration experiments. It is not licensed for production database workloads or redistribution.
Does every clone need a full database copy?
No. Clones use LVM thin snapshots to share unchanged base data blocks. Each clone consumes additional physical storage as it writes changes. The total clone count is still limited by the host’s CPU, memory, storage, and available ports.
What do I need to run it?
A supported Linux VM, documented for Ubuntu 24.04 LTS, with capacity for SQL Server, Docker, LVM, and a dedicated data disk. eddb ships as one Linux binary. A current eddb license is required to provision capacity; you remain responsible for SQL Server licensing, firewall rules, backups, and data security.
Can I try it without an existing backup?
Yes. Storage initialization normally builds empty default SQL Server 2022 and 2025 bases, so you can create a first clone without bringing a backup. This requires the normal licensed host setup.
Is eddb a hosted database service?
No. eddb is a single-node Linux CLI. Your containers, data, and local state run on your own VM. eddb does not monitor or secure the environment for you. See the support policy for the operating responsibilities.
Make space
for what’s next.
Your database is the starting point.
What you build from it is
up to you.
For internal development and testing.