centersl/portainer-docs
1
0
Fork 0
mirror of https://github.com/portainer/portainer-docs.git synced 2026-03-27 04:48:31 +07:00
Code Issues Packages Projects Releases Wiki Activity

GITBOOK-20: Include business feature info

Browse Source
This commit is contained in:
Hannah Cooper
2026-02-26 23:16:09 +00:00
committed by gitbook-bot
parent 07fe7bec42
commit 46211300e2
8 changed files with 86 additions and 48 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
admin/environments/policies/README.md
View File

@@ -6,12 +6,12 @@ metaLinks:
# Policies
{% hint style="warning" %}
Policies can only be applied to Edge (Standard) Agent environments that are of version 2.37.0 or greater.
{% hint style="info" %}
This feature is only available in [Portainer Business Edition](https://www.portainer.io/business-upsell?from=ca-file).
{% endhint %}
{% hint style="info" %}
Policies can only be created in Portainer Business Edition.
{% hint style="warning" %}
Policies can only be applied to Edge (Standard) Agent environments that are of version 2.37.0 or greater.
{% endhint %}
Policies introduces a centralized configuration and policy inheritance as part of the Fleet Governance Policies feature set. This allows you to apply configuration, security rules, and cluster settings to groups of environments, rather than configuring each environment individually. By defining settings once at the group level, all child environments inherit those values, helping you keep access consistent and reduce configuration drift. Any created policies will override existing environment level access.

4
admin/environments/update.md
View File

@@ -6,6 +6,10 @@ metaLinks:
# Update & Rollback
{% hint style="info" %}
This feature is only available in [Portainer Business Edition](https://www.portainer.io/business-upsell?from=ca-file).
{% endhint %}
This feature lets you upgrade your Edge Agent deployments directly from Portainer, without the need to log into the remote environments and manually update.
{% hint style="warning" %}

4
admin/registries/browse.md
View File

@@ -6,6 +6,10 @@ metaLinks:
# Browse a registry
{% hint style="info" %}
This feature is only available in [Portainer Business Edition](https://www.portainer.io/business-upsell?from=ca-file).
{% endhint %}
The registry manager extends your container management experience by giving you the ability to browse defined registries and manipulate their content. By using this feature, container users enjoy the benefit of having a single interface to manage any Docker registry deployment, providing a consistent look and feel across any provider.
{% hint style="info" %}

26
admin/settings/general.md
View File

@@ -24,6 +24,10 @@ Replaces our logo with your own. Toggle on and enter the URL to the logo. The re
### Login screen banner
{% hint style="info" %}
This feature is only available in [Portainer Business Edition](https://www.portainer.io/business-upsell?from=ca-file).
{% endhint %}
This setting allows you to specify a custom text banner that will appear on the login screen for all users. This could be used to provide informational detail, a warning message, or whatever you need. To enable this, toggle the **Login screen banner** option on and enter your message in the **Details** box.
<figure><img src="../../.gitbook/assets/2.16-settings-login-screen-banner.png" alt=""><figcaption></figcaption></figure>
@@ -41,7 +45,7 @@ You can deploy containers and services using Portainer's set of built-in app tem
### Automatic Portainer patch updates
{% hint style="warning" %}
This is a beta feature and is only available in Portainer Business Edition.
This is a beta feature and is only available in [Portainer Business Edition](https://www.portainer.io/business-upsell?from=ca-file).
{% endhint %}
{% hint style="info" %}
@@ -126,12 +130,12 @@ In this section you can configure various Kubernetes-specific deployment options
## Certificate Authority file for Kubernetes Helm repositories
This section lets you supply a certificate authority (CA) file for use with HTTPS connections to Helm repositories from Portainer. This is useful if the TLS certificate your Helm repository uses is signed by a custom CA, and applies to both the Helm Repository configured above and to Helm repositories configured per environment.
{% hint style="info" %}
This feature is only available in [Portainer Business Edition](https://www.portainer.io/business-upsell?from=ca-file).
{% endhint %}
This section lets you supply a certificate authority (CA) file for use with HTTPS connections to Helm repositories from Portainer. This is useful if the TLS certificate your Helm repository uses is signed by a custom CA, and applies to both the Helm Repository configured above and to Helm repositories configured per environment.
<figure><img src="../../.gitbook/assets/2.18-settings-helmcafile.png" alt=""><figcaption></figcaption></figure>
## SSL certificate
@@ -166,6 +170,10 @@ After making changes to this section, click **Apply Changes**.
## Additional functionality
{% hint style="info" %}
This feature is only available in [Portainer Business Edition](https://www.portainer.io/business-upsell?from=ca-file).
{% endhint %}
This section contains options for enabling and configuring additional functionality within Portainer.
| Field/Option | Overview |
@@ -176,6 +184,10 @@ This section contains options for enabling and configuring additional functional
## Experimental features
{% hint style="info" %}
This feature is only available in [Portainer Business Edition](https://www.portainer.io/business-upsell?from=ca-file).
{% endhint %}
This section allows you to enable experimental Portainer features for use in your deployment. These features are in early development and have gone through a limited set of testing, and are provided to users in order to gather feedback on the feature at an earlier stage of development.
{% hint style="danger" %}
@@ -208,6 +220,10 @@ Log in as an admin user. From the menu select **Settings**, then scroll down to
### Backing up to S3
{% hint style="info" %}
This feature is only available in [Portainer Business Edition](https://www.portainer.io/business-upsell?from=ca-file).
{% endhint %}
With Portainer Business Edition you have the option to store a backup of your configuration in an S3 bucket, either on demand or on a defined schedule.
To do this, log in as an admin user, select **Settings** from the menu, then scroll down to **Backup Portainer**.
@@ -264,6 +280,10 @@ When you're ready, click **Restore Portainer**. The restore might take a few mom
## Portainer support
{% hint style="info" %}
This feature is only available in [Portainer Business Edition](https://www.portainer.io/business-upsell?from=ca-file).
{% endhint %}
In this section you will find settings related to troubleshooting your Portainer installation.
### Support bundle

62
faqs/licensing/what-is-the-pricing-for-business-edition.md
View File

@@ -40,11 +40,12 @@ To find out what we mean by node check out: [What is a node for licensing purpos
**Perfect for small businesses, or those beginning their containerization journey.**
* 5, 10, 15 node options
* For commercial (business) use&#x20;
* Community Support
* Community support
* Max of 16 vCPUs per node
* Payment via online purchase only
* Click-through license agreement
* For commercial (business) use&#x20;
* Limited to organizations with ≤ $50 million in annual revenue.
### **Scale**
@@ -52,12 +53,14 @@ To find out what we mean by node check out: [What is a node for licensing purpos
**Ideal for businesses who require access to expert assistance and commercial support**
* 5, 10, 15, 20, 25, 30, 35 node options
* 5, 10, 15, 20, 25 node options
* 9x5 Next Business Day support
* Onboarding support
* Max of 24 vCPUs per node
* Payment via invoice (bank transfer or credit card)
* Vendor onboarding (ability to purchase via Reseller)
* For commercial (business) use&#x20;
* Limited to organizations with ≤ $100 million in annual revenue.
### Enterprise
@@ -67,42 +70,37 @@ To find out what we mean by node check out: [What is a node for licensing purpos
Everything in Scale plus:&#x20;
* Includes 10 nodes, then add the extra nodes you need, up to 32vCPUs, up to 64vCPUs and unlimited vCPUs options.&#x20;
* From 32 vCPUs to unlimited vCPUs per node
* Production and Non-Production node options
* Assigned Success Engineer
* Custom Master Software and Service Agreement
* Security Assessment Report&#x20;
* Software Bill of Materials&#x20;
* Business-critical support option&#x20;
* [Managed Platform Services option](https://www.portainer.io/portainer-managed-platform-services?hsLang=en)
* TAA Compliance Certificate
* Assigned support engineer
* Customizable license agreement
* Security assessment report&#x20;
* 24/7 Support option
* Managed Platform Services option
***
## For Edge/IIoT Deployments
[**Contact sales**](https://www.portainer.io/contact-sales?hsLang=en) **to explore pricing**
[**Contact sales**](https://www.portainer.io/contact-sales?hsLang=en) **to explore your options and pricing**
Buy a Professional or Enterprise Plan, then Add On Nodes
### **Professional**&#x20;
First, choose from Professional or Enterprise Plans:&#x20;
* Manage up to 100 Edge / IIoT devices with one Portainer Server (nodes licensed separately)
* Onboarding assistance
* 9x5 support
* Click-through license agreement
* Can manage up to a maximum of 100 nodes
* Professional Services available as additional option
| Professional | Enterprise |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <ul><li>Scale by adding nodes</li><li>Onboarding assistance</li><li>9x5 support</li><li>Customer Success</li><li>Click-through license agreement</li><li>Can manage up to a maximum of 100 nodes (see below options)</li></ul> | <ul><li>Scale by adding nodes</li><li>Onboarding assistance</li><li>Prioritized 9x5 support</li><li>Assigned Success Engineer</li><li>Professional Services available</li><li>Custom MSSA option</li></ul> |
### **Enterprise**&#x20;
Second, add on Nodes:&#x20;
| Edge Server | Edge Gateway/ Industrial PC | LinuxPLC/ MiniPC | IOT Sensor Device |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Annual subscription license for a physical server node limited to 16 cores and deployed in an edge compute environment (Ex: Single Socket Server - Xeon or i9) | <p>Annual subscription license for a node limited to 10 cores and deployed in an edge compute environment (Ex: Intel Atom/i3/i5/i7 CPUs)</p><p><em>Minimum order 50 nodes</em></p> | <p>Annual subscription license for a node limited to 4 cores (Ex: Edge PC, Single-Board-Computer, PLC/PFC/PAC, Intel Atom)</p><p><em>Minimum order 100 nodes</em></p> | <p>Annual subscription for a node limited to System-in-Package, CPU clock speed &#x3C;= 1Ghz (Ex: RPi Zero)</p><p><em>Minimum order 1000 nodes</em></p> |
Optional extra services:
| **Portainer 24x7 Support (247SLA)** | Upgrade to 24x7 Global Support SLA |
| ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Extended Onboarding Service (EOS)** | Extra assistance getting Portainer Business integrated with your environment. Valid for 30 days from nominated project start. Add multiple for extended duration. Review full terms and conditions before purchase. |
| **Portainer Professional Services (Services)** | Advanced services for consulting, implementation, configuration and support (hourly basis) |
| **Managed Platform Services** | Portainer's managed platform services team will accelerate your containerization journey. |
<br>
* Manage all your Edge / IIoT devices with one Portainer Server (nodes licensed separately)
* Onboarding assistance
* Prioritized 9x5 support
* Assigned Support Engineer
* Customizable License Agreement
* Vendor onboarding
* Multi-instance available (production, dev, test environments)
* Security Assessment Report
* Professional Services available as additional option

4
user/edge/configurations.md
View File

@@ -6,6 +6,10 @@ metaLinks:
# Edge Configurations
{% hint style="info" %}
This feature is only available in [Portainer Business Edition](https://www.portainer.io/business-upsell?from=ca-file).
{% endhint %}
Edge Configurations are sets of files that can be pre-deployed to your Edge environments in order to provide dynamic configurability on each Edge environment as well as avoid storing large amounts of config files in deployment repositories.
From the menu under **Edge compute** select **Edge Configurations**.

22
user/edge/stacks/add.md
View File

@@ -85,7 +85,7 @@ If you have 2FA configured in GitHub, your passcode is your password.
### GitOps updates
{% hint style="info" %}
This feature is only available in Portainer Business Edition.
This feature is only available in [Portainer Business Edition](https://www.portainer.io/business-upsell?from=ca-file).
{% endhint %}
Portainer supports automatically updating your Edge Stacks deployed from Git repositories. To enable this, toggle on **GitOps updates** and configure your settings.
@@ -114,7 +114,7 @@ For more detail on how automatic updates function under the hood, have a look at
### Relative path volumes
{% hint style="info" %}
This feature is only available in Portainer Business Edition.
This feature is only available in [Portainer Business Edition](https://www.portainer.io/business-upsell?from=ca-file).
{% endhint %}
When you toggle **Enable relative path volumes** to on, you are able to specify relative path references in your compose files. Portainer will create the required directory structure and populate the directories with the relevant files from your Git repository. This feature is only available for Docker Standalone and Docker Swarm environments.
@@ -145,12 +145,16 @@ For more detail on how this feature works, have a look at [this article](../../.
#### Always clone Git repository
{% hint style="info" %}
This feature is only available in [Portainer Business Edition](https://www.portainer.io/business-upsell?from=ca-file).
{% endhint %}
With relative path volumes enabled, you can also toggle **Always clone git repository.** Enabling this option ensures that the Git repository is always cloned for any relative paths defined in your Compose files. The referenced content is then pulled directly from your Git repository to the environment where the stack is deployed.
### GitOps Edge configurations
{% hint style="info" %}
This feature is only available in Portainer Business Edition.
This feature is only available in [Portainer Business Edition](https://www.portainer.io/business-upsell?from=ca-file).
{% endhint %}
You can also choose to deploy device-specific configurations from your Git repository to the devices your Edge stack will be deployed to. To use this, enable the **GitOps Edge configurations** toggle, enter the **Local** or **Remote filesystem path**, **Directory** (relative to the root of your Git repository) and select the **Device** or **Group matching rule** that corresponds to your configuration.
@@ -200,7 +204,7 @@ Select an Edge Stack template to deploy from the **Template** dropdown, and make
### Webhooks
{% hint style="info" %}
This feature is only available in Portainer Business Edition.
This feature is only available in [Portainer Business Edition](https://www.portainer.io/business-upsell?from=ca-file).
{% endhint %}
For the Web editor, Upload and Template build methods you can choose to enable an Edge Stack webhook. This webhook will allow you to trigger updates to the stack by sending a POST request to a specific URL, instructing Portainer to pull the most up to date version of the associated image and re-deploy the stack.
@@ -214,7 +218,7 @@ For Git deployed stacks, this functionality is available via [GitOps updates](ad
### Environment variables
{% hint style="info" %}
This feature is only available in Portainer Business Edition.
This feature is only available in [Portainer Business Edition](https://www.portainer.io/business-upsell?from=ca-file).
{% endhint %}
As an optional step, you can also set environment variables. You can use these to define values in your compose file that would vary between deployments (for example, hostnames, database names, etc).
@@ -246,7 +250,7 @@ Note the compose file is not changed when environment variables are used - this
### Registry
{% hint style="info" %}
This feature is only available in Portainer Business Edition.
This feature is only available in [Portainer Business Edition](https://www.portainer.io/business-upsell?from=ca-file).
{% endhint %}
If your stack requires access to images in private registries, you can specify which registry to use as part of the deployment.
@@ -256,7 +260,7 @@ If your stack requires access to images in private registries, you can specify w
### Pre-pull images
{% hint style="info" %}
This feature is only available in Portainer Business Edition.
This feature is only available in [Portainer Business Edition](https://www.portainer.io/business-upsell?from=ca-file).
{% endhint %}
By default, Docker will start containers within the stack that it already has images for, while at the same time pulling any other images it needs from the upstream registries. In some cases you may want to wait until all of the needed images are pulled to the device before starting the stack. To do this, enable the **Pre-pull images** toggle. This can also help to avoid issues when some images in a stack are unable to be pulled, leading to an incomplete or partial deployment.
@@ -266,7 +270,7 @@ By default, Docker will start containers within the stack that it already has im
### Retry deployment
{% hint style="info" %}
This feature is only available in Portainer Business Edition.
This feature is only available in [Portainer Business Edition](https://www.portainer.io/business-upsell?from=ca-file).
{% endhint %}
If a deployment of an Edge Stack fails (for example if the remote Edge environment is unavailable), by default Portainer will not try and redeploy the stack. If you wish to enable retrying of failed deployments, you can toggle **Retry deployment** to on and set **Retry for** to the length of time you want Portainer to retry deploying the stack.
@@ -278,7 +282,7 @@ When the time selected in **Retry for** is reached, Portainer will stop retrying
### Update configurations
{% hint style="info" %}
This feature is only available in Portainer Business Edition.
This feature is only available in [Portainer Business Edition](https://www.portainer.io/business-upsell?from=ca-file).
{% endhint %}
This section lets you define the method in which your stack updates are deployed across your Edge devices. You can choose to deploy to **All edge devices at once**, or select **Parallel edge device(s)** to specify how many devices to update concurrently.

4
user/edge/waiting-room.md
View File

@@ -6,6 +6,10 @@ metaLinks:
# Waiting Room
{% hint style="info" %}
This feature is only available in [Portainer Business Edition](https://www.portainer.io/business-upsell?from=ca-file).
{% endhint %}
The Edge Devices Waiting room lists any Edge Devices that have connected using the pre-deploy script and are pending association with the Portainer instance. The list can be filtered by Edge Group, group, and tag.
<figure><img src="../../.gitbook/assets/2.18-edge-waitingroom.png" alt=""><figcaption></figcaption></figure>