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

# Choosing a Backend

> Local, hosted (Sia Storage), or bring your own indexer: how to decide.

`obsidianlog init` offers three effective choices. All three are available
through the same wizard, and none require touching code.

| Backend                                                            | Infrastructure you run             | Who pays for storage                                         | Best for                                               |
| ------------------------------------------------------------------ | ---------------------------------- | ------------------------------------------------------------ | ------------------------------------------------------ |
| [Local](/storage-backends/local-backend)                           | None (filesystem only)             | N/A, no Sia network involved                                 | Development, testing, offline/air-gapped use           |
| [Hosted (Sia Storage)](/storage-backends/hosted-sia-storage)       | None                               | Subject to your Sia Storage account's current plan and quota | Most users who want managed, durable Sia storage       |
| [Bring Your Own Indexer](/storage-backends/bring-your-own-indexer) | Your own `indexd` (or a partner's) | You, via your own wallet                                     | Compliance/regulated environments wanting full control |

## Recommendation

Start with **Local** to evaluate ObsidianLog with zero setup. Move to
**Hosted (Sia Storage)** when you want real, durable, off-site archival. It
requires no indexer infrastructure from you, but it does require Sia Storage
account approval and is subject to that service's current plan and terms.
Only reach for **Bring Your Own Indexer** if you specifically need to control
the wallet and infrastructure yourself.

## Switching later

Re-running `obsidianlog init` and choosing a different backend writes a new
`config.toml`. It doesn't migrate previously archived data between backends.
Plan your backend choice with that in mind if you're archiving anything you
intend to keep long-term.