Stravia Docs

Getting started

Use this section to move from a fresh Stravia installation to a request that appears in Request history. The short path is Quick start ; use the other guides when you need to split an individual setup step out.

Follow the first-use path

  1. Choose where Stravia runs. Choose Desktop or Server compares the local Desktop session with Server's browser-based management setup.
  2. Install the matching build. Install Stravia covers release assets and checks before launch. Desktop installers and Server binaries are separate products; Server containers are another deployment option.
  3. Complete first setup. First setup explains the one-time Server bootstrap separately from Desktop's native local session.
  4. Connect an upstream model service. Add a model service covers the service account, supported authentication method, endpoint, and model sync.
  5. Make a model available to clients. Add a model explains the client-facing Model ID and its enabled upstream destination.
  6. Grant the client only needed access. Create an API key covers key scope and the separate optional capabilities.
  7. Send and confirm a request. Make your first request distinguishes the response from its completed Request history entry.

Keep the setup layers separate

The upstream service credential belongs on the Stravia model-service connection. The client API key belongs with the calling client. A Server administrator password is for managing that Server. These credentials serve different roles; do not substitute one for another.

Likewise, saving a service, enabling a model, creating a key, and preparing a client configuration are separate stages. A generated example or Desktop-written configuration does not establish that a client has sent a successful request. Confirm the request at the final step.

When to use a different guide

  • Start with Quick start for the complete shortest walkthrough.
  • Use Connect clients after you have an enabled model and an eligible API key; it provides client configuration previews and request examples.
  • For a self-hosted production deployment, start with Deploy rather than exposing a first-run Server as-is.

Continue learning

After the first request, see Core concepts for how models, routes, keys, history, and usage fit together.