Database-Eggs Docs · About

About Database-Eggs

Database-Eggs is one universal egg that runs 50+ database engines (with strict version contracts, zero-leak credential handling and hardware-aware tuning) across every Wings-family panel. No bespoke per-engine images, no host root, no stale single-database eggs.

How it works

A single egg JSON dispatches on DATABASE_TYPE. On first boot the runtime downloads the pinned engine release, SHA-verifies it, sizes buffers from the container's RAM/CPU limits, provisions users with high-entropy secrets and supervises the daemon with graceful stop handling.

Security model

Runs unprivileged (UID 988). Secrets are generated with openssl/urandom, persisted to .env with mode 600, and masked in all console output. SCRAM-SHA-256 and per-engine hardening are on by default (SECURITY_HARDENING=1).

Open source

Egg JSON, runtime scripts, tests and CI live in the open. Found a bug or want an engine added? Open an issue or a PR; new eggs and engines are always welcome. See CONTRIBUTING.md for the egg JSON contract.

github.com/PotenFYR-Studios/Database-Eggs

The PotenFYR nest

Database-Eggs is part of the PotenFYR Studios egg family. The unified catalog of every collection (databases, languages, Minecraft, shells) lives at the nest.

nest.potenfyr.in

PotenFYR Studios

PotenFYR Studios builds games, plugins, hosting infrastructure and open-source developer tools, from Minecraft plugins and Pterodactyl eggs to API security. This documentation site is part of the *.docs.potenfyr.in family.

License

Database-Eggs is licensed under the Apache License 2.0 with the Commons Clause. In plain terms, you can: use it for any purpose, commercial use included; run it on any panel or plain Docker; fork it; modify it; redistribute it; self-host it for yourself, your community or your customers; and build products or services on top of it.

What you cannot do: sell the software itself; offer a paid product or service whose value derives entirely or substantially from this software's functionality; or use PotenFYR names, logos or trademarks. If you redistribute the software, keep the license notices intact, including the Commons Clause notice.

The authoritative text is the repository's LICENSE file (Apache-2.0 with the Commons Clause License Condition v1.0); this page is a summary, not legal advice.