> For the complete documentation index, see [llms.txt](https://docs.payfacto.com/payfacto-knowledge/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payfacto.com/payfacto-knowledge/veloce-pos/veloce/installation-and-initial-setup/download-veloce-files.md).

# Download Veloce Files

This section describes how and where to download Veloce files to get started.

***

### Veloce Base Configuration

With Veloce, it is possible to use pre-configured restaurant databases as a starting point for new restaurants.  This is much more efficient than starting from scratch and will save a lot of time.

### Localized Base Configs

Download the appropriate localized base configurations from the links below:

* [English (CA)](http://versions.velocehq.com/base/VeloceBaseEN-0122.zip)
* [English (US)](http://versions.velocehq.com/base/VeloceBaseEN-US-0122.zip)
* [English (UK)](http://versions.velocehq.com/base/VeloceBaseUK-0122.zip)
* [French (CA)](http://versions.velocehq.com/base/VeloceBaseFR-0122.zip)

***

### Veloce Updater

The latest Veloce version can be downloaded here:

* [Veloce Download](http://versions.velocehq.com/v_9/)

If you need an older version, they can be downloaded from here:

* [Old Veloce Downloads](http://versions.velocehq.com/v_9/Old%20version/)

Once all the necessary files are downloaded, copy them on removable media, such as a flash drive or portable hard drive. You may proceed to install Veloce.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.payfacto.com/payfacto-knowledge/veloce-pos/veloce/installation-and-initial-setup/download-veloce-files.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.