Just Dashboard Reviewed templates
Choose a template, understand first sign-in, and know which catalogue entries can deploy.
The Template source in Deployments → New project contains reviewed application definitions. Just Dashboard 0.8.4 ships 62 definitions so an existing deployment can still resolve its version; 57 are offered for new projects. The catalogue has not changed since 0.7.0. Each card names the application, its purpose, and how the first person gains access.
The catalogue includes databases and infrastructure tools as well as applications such as n8n, Grafana, Uptime Kuma, Vaultwarden, Nextcloud, Jellyfin, code-server, Ollama, Open WebUI, ntfy, Qdrant, NocoDB, DocuSeal, Seerr, and SearXNG. Search, or use the topic chips in the picker: Productivity, Media, Monitoring, Automation, AI, Developer tools, Databases, Web & files, and Game servers.
Choose by first sign-in
The tag on each card says how you get in, and choosing the card expands it into a sentence. It can say:
| Card says | What to expect |
|---|---|
| you create the first account | The application asks its first visitor to create an account. |
| password generated here | The dashboard generates a password and supplies the named username. An administrator can reveal it from the deployed project's First sign-in card. |
| token generated here | A generated token is the credential a client or browser needs. |
| no sign-in page | There is no browser sign-in; a program connects with a named secret. The project's card is titled How to connect. |
| no sign-in at all | The application has no sign-in of its own. Decide how to protect its route before publishing it. |
A template's access instructions come from its reviewed definition. Do not assume every application starts with an admin account or a password printed in a container log. Five former entries are retired from the new-project catalogue because their first-access path could not be stated safely: File Browser, wallabag, MinIO, Syncthing, and Healthchecks. Existing projects can still resolve those definitions for their retained releases, and their First sign-in card says the template is no longer offered.
Check whether it can deploy
A card tagged Preview only cannot deploy, and choosing it explains why. In 0.8.4 that applies to the two game-server templates, Minecraft (Java Edition) and Minecraft (Bedrock Edition): the game-server integration is not available in this release, and deployments cannot yet write a template's configuration files before start or publish a UDP port. Template deployments also cannot download a startup artifact. A direct API request does not bypass those limits. Choose a supported template, an ordinary image, or a Compose project whose requirements you can express in the available runtime instead.
For a supported template, select it, fill its required inputs, press Use this template, and inspect the resulting source, runtime, domain, and storage on Review. Passwords and other self-issued secrets are generated on the server when the project is created and stored encrypted. The project's Overview → First sign-in card then tells you what to do and, for an administrator, offers an audited reveal of a generated credential.
Templates are versioned definitions rather than scripts fetched at click time. Their image, inputs, checks, storage, and first-access metadata are shipped with the dashboard. Still review the shown public address, visitor password, direct ports, and backup plan for the service you are putting on your server.