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

# Infrastructure

- [Vultisig infrastructure](https://docs.vultisig.com/infrastructure/overview.md): Vultisig infrastructure: Vultiserver (Fast Vault co-signer) and the relay (encrypted device messaging).
- [Vultiserver](https://docs.vultisig.com/infrastructure/what-is-vultisigner.md): Vultiserver is the server co-signer for Fast Vaults. One-device signing. Configurable policies are not in the apps yet.
- [How a Vultisig Fast Vault works](https://docs.vultisig.com/infrastructure/what-is-vultisigner/how-does-vultisigner-work.md): How a Vultisig Fast Vault is created and signed. 2-of-2 keygen with Vultiserver, where the server share is stored, and what to do if the server is offline.
- [Vultiserver transaction policies](https://docs.vultisig.com/infrastructure/what-is-vultisigner/what-can-be-configured.md): Vultiserver transaction policies (coming soon): Spending limits, whitelisted addresses, time delays, and custom rules for automated co-signing.
- [Why Vultiserver is safe](https://docs.vultisig.com/infrastructure/what-is-vultisigner/why-is-it-safe.md): Vultiserver security model: Single share can't sign alone, server can't initiate transactions, secure even if compromised. Backup procedures.
- [Vultisig relay server](https://docs.vultisig.com/infrastructure/relay-server.md): Vultisig Relay Server enables encrypted device-to-device communication. End-to-end encrypted keygen and keysign messaging. Open source.


---

# 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.vultisig.com/infrastructure.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.