Infrastructure

What self-hosted actually means

Self-hosting describes where software runs and who operates it. It does not automatically mean no cloud services, no data transfer or no maintenance.

On this page

Separate execution, access and supporting services

A workspace can run on your machine while an agent still calls a model provider. It can keep repositories locally while a relay helps the browser reach the workspace.

The useful questions are specific: where do files and session history live, which services receive data, who controls access and how can the system be restored?

Four responsibilities to understand

Operation

You need a plan for service updates, host health and resource capacity.

Access

Authentication, networking and account permissions define who can reach the workspace and what they can do.

Data protection

Backups, restore checks and appropriate handling of credentials remain important.

External dependencies

Agent providers, relay services and integrations can have their own data flows and availability constraints.

A boundary worth documenting

In Qodarium's architecture direction, code and compute stay on customer infrastructure. Supporting services may handle account, entitlement, relay and notification metadata. Exact behavior must be documented and checked for the release and integrations in use.

That is a product boundary, not a blanket zero-knowledge or compliance claim. A trustworthy description should say what is known and where validation is still required.

Evaluate a self-hosted product

  1. Map the components

    Identify the browser, application service, data stores, agent runtime and external connections.

  2. Read the operating requirements

    Understand the supported installation, update and backup paths.

  3. Test recovery

    Verify that important state can be restored before you depend on the system.

  4. Review changes over time

    An added integration can introduce a new data flow even when the main application remains self-hosted.

Read next

The Qodarium architecture guide describes the intended component boundaries. The host-readiness checklist is a practical starting point.

A little less watching. A lot more building.

Make room for
long-running ideas.

A workspace that holds the context while you focus on what comes next.

IN DEVELOPMENT · COMMUNITY + TEAM