Docs /
... / Deploying Apps / Browse and deploy from the launcher

Browse and deploy from the launcher

Use the app launcher at app.odac.run to browse ready-to-run catalog apps, inspect stack contents and server requirements, pick an image version, and place apps onto your project's Canvas.

Open the launcher

  1. Open the app launcher from your project's Canvas using any of these triggers:

    • Click the floating plus button centered at the bottom of the board when your server is online (see Overview).
    • Click Add App at the top of the left sidebar rail.
    • Double-click any empty spot on the dotted grid.
    • On an empty board, click the dashed Add your first app card in queue mode (see Queueing apps before connecting a server) or Initialize Server Space when a server is connected.

    The launcher slides out beside the left sidebar, and Add App stays highlighted in the rail. If your server is offline, the bottom button displays Server Offline and double-clicking the grid shows Cannot create apps while server is offline. To close the launcher without placing an app, click empty space on the Canvas, click Add App again, or press Escape.

Docked app launcher open beside the left sidebar with Add App highlighted and catalog cards visible

Search the catalog

  1. Keep the Apps tab selected and type an app name or category tag (such as database, postgres, or ai) into Search apps or paste a public GitHub URL (github.com/owner/repo)... to filter the list. Press Down Arrow from the search box to focus the first card and press Enter to add it, or clear your query if No applications found and Try adjusting your search or category appear. To deploy a repository instead, switch to Git Repos or paste a public GitHub URL: see Connect and deploy from GitHub.

Launcher search bar with database typed and matching PostgreSQL and Redis cards below

Read card badges

  1. Multi-app stacks: Apps that deploy multiple linked services together display a teal layers badge with the service count, such as 2 on WordPress or Ollama + Open WebUI. Hover over the layers badge to open a popover listing every included service.

WordPress card in the launcher with its stack badge hovered and the service popover listing Mariadb and Wordpress

  1. GPU requirements: Apps that require a GPU display a chip badge (GPU, NVIDIA GPU, AMD GPU, or Intel GPU). When your server satisfies the requirement (or before a server is attached), the badge appears in green and the card deploys normally. When your server cannot provide a compatible GPU or enough VRAM, the badge turns amber, the card dims, and a note below the tags explains why (for example, This server doesn't have a GPU.). Clicking or dragging an unavailable card shows that requirement in a notification instead of placing it. Apps where GPU acceleration is optional do not show a GPU badge.

Available ComfyUI card with a green GPU badge above an unavailable ComfyUI card dimmed with an amber GPU badge and note

  1. Server access capabilities: Apps that need elevated host permissions display a violet shield badge: Network admin, Raw sockets, Low ports, Priority, or Host access. Hover over the badge to read the elevated access tooltip. Unlike an unmet GPU requirement, this badge is informational only and does not prevent you from placing the app.

WireGuard card showing the violet Network admin badge hovered with its elevated access tooltip

Pick an image version

  1. On catalog cards that offer selectable versions, click the teal version pill on the right side of the tag row (showing the default tag, such as 15-alpine) to open the version menu without placing the card. Type in Filter versions… to narrow down the list, then click a version such as 16-alpine to update the pill (a green checkmark marks the active choice). Click outside the menu or press Escape to keep the current tag.

PostgreSQL card with its version pill clicked and the Filter versions dropdown listing 17-alpine, 16-alpine, 15-alpine, and 14-alpine

Place or cancel an app

  1. Click to auto-place: Click an available card (anywhere outside its version pill) and release without dragging. The launcher closes, ODAC places the app in the nearest open grid spot, and the new card appears dimmed with a spinner and Creating... while it deploys (or QUEUED if no server is attached yet).

Canvas board showing shop active next to a newly auto-placed PostgreSQL card in the Creating state

  1. Drag to a grid spot: Press and hold an available card, then drag it out onto the Canvas. The launcher closes and a translucent preview card labeled Place on canvas snaps to the grid cells under your pointer. Over open cells, the preview shows a bright highlighted border and releasing deploys the app there; over occupied cells, the border turns red and releasing cancels placement with Cannot place here: Collision detected.

Dragging the PostgreSQL preview card onto an open grid cell with a highlighted border while the bottom button turns into a trash icon

  1. Cancel placement: While you drag a card, the floating plus button at the bottom of the Canvas turns into a red trash button. Drag the preview card onto the trash button until it glows and the preview shrinks into it, then release to cancel. You can also right-click or press Escape at any time before releasing to cancel.

Active red trash button at the bottom of the Canvas cancelling app placement