> ## Documentation Index
> Fetch the complete documentation index at: https://docs.skrmir.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Light Mode vs Full Mode

> Comparison of AiOS light mode and full mode across bootstrap scope, dependency footprint, and production readiness.

# Light Mode vs Full Mode

## Audience

This page is for operators, maintainers, and developers choosing between different bootstrap paths.

## Goal and Scope

This page explains:

1. how light mode differs from full mode
2. why both still target K3s as the formal runtime base
3. when to evolve from light mode toward full mode

## Core Concepts

### Shared properties

* both use the binary entry for bootstrap
* both still rely on K3s for formal runtime
* neither means “run the whole platform forever as one local process”

### Light mode

Best for:

* development validation
* minimal platform bring-up
* resource-constrained environments

Characteristics:

* lighter dependency deployment
* faster startup-oriented defaults

### Full mode

Best for:

* production-oriented validation
* fuller dependency and security baselines
* rehearsing a runtime closer to the formal production shape

## Standard Workflow

1. choose a bootstrap mode
2. complete preflight, source selection, and K3s initialization
3. deploy minimal or fuller dependencies according to the chosen mode
4. transition into K3s image-based runtime

## CLI Examples

```bash theme={null}
go run ./cmd/aios
```

## Web UI Path

Choose light/full mode in the install wizard and review the mode-specific guidance.

## Pitfalls / Risk Notes

* light mode does not bypass the clustered runtime model; it only uses a lighter bootstrap configuration
* full mode is not a separate architecture, just a fuller dependency and runtime baseline

## Related Pages

* [Bootstrap: Light Mode](/en/getting-started/bootstrap-light-mode)
* [Bootstrap: Full Mode](/en/getting-started/bootstrap-full-mode)