Extensions and Blueprint

The Blueprint extension framework ships pre-installed in Panasaurus. There is nothing to patch, no fork to maintain, and no version drift: extensions written for Blueprint and Pterodactyl install and run out of the box. The Blueprint section of these docs covers what that means for developers.

The admin area

Two pages under Admin → Panasaurus handle everything visual:

• Extensions lists every installed extension with its version, controls, and removal action.
• Marketplace is a live view of the Blueprint ecosystem directory, cached in-app, with search and filters. Each listing shows the exact install command, so you can copy it and go.

The CLI

The panasaurus binary inside the container manages extensions directly (it is also available as blueprint for muscle memory):

docker compose exec panel panasaurus -install extension.blueprint   # install a file
docker compose exec panel panasaurus -list                          # list installed extensions
docker compose exec panel panasaurus -remove extension              # remove an extension
docker compose exec panel panasaurus -help                          # everything else

A typical workflow from the marketplace page: download or reference the .blueprint file, install it, then reload the admin area. The CLI wires up backend routes, admin views, and frontend extension points automatically — the panel's React app exposes the same extension slots Blueprint users already know, so no rebuild is required.

Troubleshooting

If an extension breaks the panel, remove it from the CLI and restart:

docker compose exec panel panasaurus -remove broken-extension
docker compose restart panel

Because data/extensions is a host mount, a broken extension never gets baked into the image — wiping the directory is always a safe escape hatch after a backup.