{% extends "base.html" %} {% block title %}Settings - Janus{% endblock %} {% block settings_active %}bg-gray-700 text-white{% endblock %} {% block content %}
Set a username and password for remote dashboard access over HTTP/Tailscale. {% if dashboard_password_set %} Current user: {{ dashboard_username }} {% else %} Not configured yet. {% endif %}
When enabled, all API requests must include a valid Janus API key. Takes effect immediately.
Default is on. Keep enabled when this server is reachable on the network.
When enabled with fill-first, each Janus API key is pinned to a stable upstream account (better cache hits, easier per-key spend). With round-robin / sticky round-robin, each Janus key still rotates across the multi-key pool, just on its own staggered counter so different clients start on different accounts.
Requests without a Janus API key share the global rotation counter.
How Janus picks among multiple accounts for the same model. Fill-first always uses the highest-priority available account; round-robin rotates every request; sticky round-robin stays on one account for a number of requests, then rotates.
How Janus routes requests across the models in a combo. Fallback tries each model in order until one succeeds; round-robin rotates across models (honoring the sticky limit below); fusion fans the request out to a panel of models and merges their answers with a judge model.
Only used when the strategy above is set to fusion.
When enabled, full request and response bodies are captured to the local database for troubleshooting. View them on the Request Logs page.
Bodies are truncated at 64 KB and only the most recent requests are kept (configurable retention, default 500). Logs may contain prompts and completions — leave off unless debugging.
No settings stored in the database.
{% endif %}Download the current DB state as a YAML config file. Provider API keys are included in plaintext.
Reset providers, combos, pricing, and settings to the values in your config.yaml. API keys and usage history are preserved.