> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-commerce/17.latest/getting-started/requirements.md).

# Requirements

Getting Started with Umbraco Commerce.

In this article, you will find the key steps needed to get started with Umbraco Commerce.

It is assumed that you have an Umbraco 17+ website configured and ready for the Umbraco Commerce installation.

{% hint style="info" %}
For detailed instructions on installing the latest version of Umbraco, refer to the [Umbraco CMS documentation](https://docs.umbraco.com/umbraco-cms/fundamentals/setup/install).
{% endhint %}

## System Requirements

The minimum requirements for using Umbraco Commerce are:

* Umbraco CMS version 17+
* SQL Server 2016+ Database
  * **SQLite** is acceptable for testing but not recommended for live deployments. For more details, see the [Configuring SQLite support](/umbraco-commerce/17.latest/how-to-guides/configure-sqlite-support.md) article.

## Versioning

Umbraco Commerce is an add-on product for Umbraco CMS and follows the [versioning strategy outlined for Umbraco CMS](https://umbraco.com/products/knowledge-center/versioning-and-release-cadence/).


---

# 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.umbraco.com/umbraco-commerce/17.latest/getting-started/requirements.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.