The right home for your data.

Start with requirements

What data do you process? Which external providers may receive it? What availability does your team need? Answer these questions before selecting a cloud or hardware.

First create a concise inventory of data and connections. Which content should live in AIOS, which external systems will be connected, and which model providers may be involved in each task? The platform’s location does not answer these questions automatically. Even in an environment you operate, you must decide whether a model request may use external infrastructure and which information it needs.

Compare four operating models

Public cloud simplifies getting started. Private cloud creates a dedicated environment. Own cloud keeps the environment in your cloud account. On premises brings the platform to your infrastructure. Model access boundaries are configured separately.

Compare deployment models against your actual responsibilities. For networking, the database, object storage, runtimes and user administration, record who makes decisions and who operates each part. The labels public cloud, private cloud, own cloud and on premises do not replace that agreement. In particular, establish how updates are prepared and who takes the first step when a problem occurs.

AIOS

01Start with requirements

02Compare four operating models

03Plan ongoing operations

Plan ongoing operations

Updates, backups, monitoring and responsibilities are part of deployment. Define who operates each component and how changes are introduced. Your own infrastructure also needs a clear operating plan.

Plan for day-to-day operations during the selection process. Backups need a responsible operator and an agreed recovery check. Monitoring needs someone who responds to relevant signals. Also record how new connectors, model connections and access are introduced. This turns an infrastructure choice into an operating plan people can follow.

Try it yourself

Adapt the placeholders to your task. This example is a template for your work with AIOS.

Proposed deployment model: [Public cloud / Private cloud / Own cloud / On premises]
Data processed: [Types and responsible teams]
Required connections: [External system → purpose]
Permitted model access: [Task → allowed local/external execution]
Operational owners: [Component → person/team]
Updates: [Owner, preparation, rollout]
Backups and recovery: [Owner and agreed recovery check]
Monitoring and incidents: [Contact and first step]
Open decisions: [Question → responsible person]

This template captures requirements; agree service commitments and responsibilities separately.

Four deployment models as a starting point