> For the complete documentation index, see [llms.txt](https://docs.geodin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.geodin.com/installation-and-licensing/deployment-modes.md).

# Deployment Modes

GeoDin can be installed in two modes, depending on your organization's needs:

* **Per-machine installation:** Each user has their own configuration, dictionaries, custom data types, and system files. This is the default for the Express installation.
* **Central network installation:** All users share the same syslib, dictionaries, custom data types, and configuration via shared folders on a network drive.

The installation folder layout is split across a **bin folder** (executable) and a **syslib folder** (dictionaries, filters, custom data types, configuration). In a per-machine installation, these are typically at `C:\Program Files\GeoDin\` and `C:\ProgramData\GeoDin\` respectively. In a central installation, they can be combined into a single stack on a network share.

## See also

* [Custom installation](/installation-and-licensing/custom-installation.md) - choose between single-user and network installation during setup.
* [Infrastructure and environment setup guide](/installation-and-licensing/infrastructure-and-environment-setup-guide.md) - multi-user deployment, syslib sharing, and database options.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.geodin.com/installation-and-licensing/deployment-modes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.