Solutions

A Solution is a curated, one-step setup in Quave ONE. Instead of picking a Docker preset and wiring the pieces together yourself, you choose a Solution from the catalog, fill in a short form, and Quave ONE provisions every component for you.

Everything a Solution creates is a normal Quave ONE app environment. There is no special runtime, no separate billing model, and no hidden infrastructure: after the install you get the same logs, metrics, env vars, console, deploys, hosts, backups, and audit trail as any other environment. The Solution only automates the creation and the wiring between components.

Availability

Solutions are being rolled out progressively. If you do not see the Solutions option when creating a new project, contact support to have it enabled for your account.

What a Solution does for you

• Creates one or more connected components. A Solution such as Headscale Stack creates a server environment and an admin UI environment, and points the UI at the server's internal host.
• Generates secrets. Admin passwords and similar values are generated during the install, stored as secret env vars on the created environment, and reported once when the install finishes. Copy them somewhere safe.
• Runs post-install steps. Some Solutions execute a command inside a component after it becomes ready and feed the output into another component's env var. That is how Headscale Stack mints its own API key and configures the admin UI without any manual step.
• Is resumable. Components are linked by a shared solution installation ID, so a partial install can be retried without duplicating what already exists.

Install a Solution

From the dashboard

1. Open your account and start a new project.
2. Choose Solutions.
3. Pick a Solution card and click install.
4. Fill in the inputs. Optional inputs usually have a sensible default; leave them empty to accept it.
5. Confirm. Quave ONE creates the components in dependency order and shows the progress of each one.
6. When the install finishes, copy any generated credentials that are shown. They are also available afterwards as secret env vars on the created environment.

From the Public API

# List the catalog available for an account, with the inputs each Solution needs
curl -H 'Authorization: YOUR_TOKEN' \
    https://api.quave.cloud/api/public/v1/solutions

# Install one
curl -X POST \
    -H 'Authorization: YOUR_TOKEN' \
    -H 'Content-Type: application/json' \
    -d '{
        "accountId": "5f7b1b7b7b7b7b7b7b7b7b7b",
        "solutionSlug": "headscale-stack",
        "appName": "Team VPN",
        "region": "us-5"
    }' \
    https://api.quave.cloud/api/public/v1/solutions

If a multi-component install fails partway through, the error response returns an installationId. Fix the reported problem and repeat the same request with that ID to create only the missing components. See the Apps API for the full request shape and authentication.

From MCP

The Quave ONE MCP server exposes list-solutions and create-solution, so an AI agent can install a Solution the same way the dashboard does. See MCP.

Catalog

Solution	Category	What it installs
Headscale Stack	Networking	A self-hosted Tailscale control plane plus its admin UI, wired together automatically.
Headscale Server	Networking	Only the control plane, for when you already run an admin UI or prefer the CLI.
Headscale UI	Networking	Only the admin UI, pointed at an existing Headscale server.
Tailscale Subnet Router	Networking	A stateless agent that bridges your tailnet into the account's private network.
Metabase	Analytics	Open-source business intelligence with dashboards and SQL over your databases.

Related docs

• App Types — how Solutions compare to Apps, Databases and Services, Functions, and Jobs.
• Environment variables
• Console — run commands inside a component, which several Solutions need for day-2 tasks.