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

# Getting Started

In order to get started with SCEPman, we have prepared two guides that address different requirements and scopes for your deployment scenario.

**Please use the table below**, to decide which of the two guides is best suited for your scenario.

## Decision Matrix

{% hint style="info" %}
In case you have Azure resource naming conventions, high availability or auto-scaling requirements that you'd also like to trial, please directly start with **Extended Guide** - even for your Trial/PoC. This will allow you to re-use the deployment in production later on.
{% endhint %}

| Requirement / Scope                                                |                                                        Standard Guide                                                        |       Extended Guide       |
| ------------------------------------------------------------------ | :--------------------------------------------------------------------------------------------------------------------------: | :------------------------: |
| I am using SCEPman Community Edition                               |       <p><span data-gb-custom-inline data-tag="emoji" data-code="2611">☑️</span></p><p>(not all features available)</p>      |                            |
| Trial or PoC                                                       | <p><span data-gb-custom-inline data-tag="emoji" data-code="2611">☑️</span></p><p>(only <strong>mandatory</strong> steps)</p> |                            |
| Standard production deployment                                     |                                                  :ballot\_box\_with\_check:                                                  |                            |
| I must obey Azure resource naming conventions                      |                                                                                                                              | :ballot\_box\_with\_check: |
| High-availability / redundancy                                     |                                                                                                                              | :ballot\_box\_with\_check: |
| Auto-scaling                                                       |                                                                                                                              | :ballot\_box\_with\_check: |
| Terraform deployment                                               |                                                                                                                              | :ballot\_box\_with\_check: |
| I am in an Azure Government cloud region (GCC High, 21Vianet, ...) |                                                                                                                              | :ballot\_box\_with\_check: |

{% content-ref url="/pages/-MCkO9ArLbD8DrG2gtYE" %}
[Standard Guide](/scepman-deployment/deployment-guides/community-guide.md)
{% endcontent-ref %}

{% content-ref url="/pages/RP5p18FAMtQi3IXCEc3K" %}
[Extended Guide](/scepman-deployment/deployment-guides/enterprise-guide-1.md)
{% endcontent-ref %}

## Videos

{% embed url="<https://www.youtube.com/watch?v=Q1DTVlxLSoU>" %}
SCEPman 2.0 Deployment
{% endembed %}

## Scenarios

For configuration examples of specific scenarios that involve SCEPman-issued certificates, please refer to the following section:

{% content-ref url="/pages/Hy3RCogixxrZxFRdYVzz" %}
[Scenarios](/scepman-deployment/deployment-guides/scenarios.md)
{% endcontent-ref %}


---

# 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.scepman.com/scepman-deployment/deployment-guides.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.