Subscription Plan Details
Enterprise & OEM
|Read-write Users (included) The number of read-write user accounts included in the plan. You can upgrade at any time for a fee without changing the plan. Please see the FAQ below for a definition of “Read-write user”.||2||10||100|
|Regular Users The number of user accounts included in the plan. You can upgrade at any time for a fee without changing the plan. See how we define a “user“.||Unlimited||Unlimited||Unlimited|
|Traffic/storage (included)||250 GB||1'000 GB||5'000 GB|
|User Roles & Permission Sets (each) The maximum number of each, user roles and permission sets, which you can use for defining permissions for users onto content and list items, and other entities and features.||10||50||Unlimited|
|Channels The maximum number of specifically permissible and filterable spaces for your content e.g. configured for particular stakeholders or microsites in Picturepark.||2||10||Unlimited|
|Languages The maximum number of languages for content or list items. Note: The system currently features two independent UI languages, English and German.||1||5||Custom|
|Content and List Items (each) The maximum number of each, content and list items, which can be created. If you overuse this quota then you will need to upgrade during a grace period into a higher plan. Please note that both, content and list items, use some space of your Storage quota. See some calculation examples.||50'000||500'000||Custom|
|Custom Schemas The maximum number of layers, virtual types, lists, fieldset and relationship fields you can define yourself within the system. Note: This excludes all schemas which are system provided by default (such as file types, XMP or countries).||25||100||Custom|
|Search-indexed fields The maximum number of fields (including nested fields) on schemas which have been defined to be searchable. See the definition of “nested fields“||1'000||3'000||Custom|
|API Keys The maximum number of API keys or client GUIDs you can use for building service providers, microsites, connectors or any other applications via the Picturepark API and SDK. Please see the FAQ about limited warranties for API Key sharing||2||20||Custom|
|API Calls (Per Minute) The maximum number of calls to the Picturepark API you can send per minute and per API key. If you overuse then you become throttled or hard limited. See additional information on API call types and limitations.||60 (best effort)||240 (warranted)||Custom|
|Support Response Time The time from when we have received your support query until we have sent you a first non-automated reply and started efforts for issue resolution.||< 24 hours (best effort)||< 6 hours (warranted)||< 1 hour (warranted)|
|Warranted Service Availability The period of time during which the Service is warranted to be available per calendar month without critical incidents and excluding scheduled maintenance. Please see the SLA for details.||> 99% (best effort)||> 99.5% (warranted)||> 99.9% (warranted)|
|Recovery Point Objective (RPO) The period of time between the creation of the Customer data (files and object store data) in Picturepark and the backup of the same data onto backup storage.||< 48 hrs (best effort)||< 24 h (warranted)||< 2 h (warranted)|
|Data Retention (of versions) The period of time during which we retain differential backup versions of Customer data (files and object store data) other than the most current version stored on live and backup storage. See further definitions.||Current version The time from when we have received your support query until we have sent you a first non-automated reply and started efforts for issue resolution.||3 days versions||10 days versions w/ priority recovery Recovery will be strictly prioritized resulting in lowest possible RTO|
|Staging Instance Staging instance of your Picturepark for the purpose of testing integrations, developments and configuration changes. Charged per TB and month with two master data copies included per month. Note: While architecturally identical, stage instances might differ with regard to performance and feature availability and are outside of our regular SLA warranties defined for your plan||Optional||Optional||3 staging mo. per year Defined as 5 TB in staging space over three months|
|Picturepark Workflows Defines the number of included Picturepark-provided workflows which provide automation for managing content e.g. with regard to processing, tagging or permission-managing content and metadata. See more details and available workflows.||Two workflows included||Up to five workflows included|
|Picturepark Purchase Options Separate purchase options available for a fee. Add-ons such as workflow tasks or Connectors are subject to the API call quotas and other limits for the plan - see the FAQ below.||
|3rd Party Purchase Options Separate purchase options for apps, connectors or professional services provided by Picturepark partners. Please note that apps, connectors and professional services usually are provided under the terms and conditions of the corresponding partner.|
FAQ & Detailled Definitions
What’s the definition of a Picturepark user and what’s a Regular user?
Picturepark users are defined as a named individual identified by a unique email address having a Picturepark user account. Regular users are unlimited and free. It is not recommended (but also not prohibited) to share regular user accounts among multiple individuals but warranty restrictions might apply for such shared use.
What’s the definition of a Read-write user (RWU)?
A ReadWrite user is a Picturepark user with at least one of the following privileges:
- can create, assign, edit, rights manage or delete files, virtual or list items (directly or via any schema such as a layer, fieldset or relationship fields etc.);
- can create, assign, edit, rights manage or delete schemas, users, roles, permissions;
- can manage system settings (not related to user’s account).
Support users of Picturepark or eligible partners are not counted against the RWU quota.
Can I share a Read-write user account with multiple individuals?
Technically, you can but it is prohibited – even for integrations, apps and microsites. For the sake of clarity, if multiple individuals use a Regular user account then this is no problem except you might lose SLA warranties. But if multiple individuals use a single RWU account via an integrated 3rd party software in an interactive way that provides immediate access to features and data of CP then every such user is regarded a RWU. Exceptions are integrated systems, apps or similar which use at least a single dedicated RWU per integration/app no more often than once every hour (e.g. for batch update jobs from an ERP), or if we have approved such use in writing under terms (e.g. OEM). Please inquire – we’re happy to understand your use case and clarify.
How can I calculate the amount of storage we need?
Calculating your storage needs depends on a variety of factors, and as a consequence it can vary greatly. As a rule of thumb for an average system, you might want to calculate the deduplicated net storage of your files and add to this the intended number of virtual items multiplied by 30 KB and the intended number of list items multiplied by 10 KB. Then multiply the total sum by a factor of 1.5 – 2 for approximating the total amount of storage required (including output formats and a reasonable amount of backup storage). Please note that overuse of your storage quota by more than 10% per month, or for more than one month per calendar quarter, will be charged.
What’s a nested field and how does it relate to search-indexed fields?
If the value of a field contains more fields then we call all these fields “nested fields”. For instance, you can have a layer where you use a field “Product ID” which is sourced by the list “Products” which again can have multiple fields for product attributes which again refer to other lists that define these attributes such as a GTIN (or UPC) code. If indexing on the layer the Product ID field so that content gets found e.g. by the GTIN code then you are also indexing nested fields. This drives up the number of search indexed fields which counts against the quota defined for your selected plan.
What happens if I overuse a license factor without bad intention?
We understand this can happen and hence try to be forthcoming for any overuse that happens without bad intention and that doesn’t violate our Acceptable Use Policy (AUP). As a general rule we always try to warn you prior to having you incur additional costs. However, there might be rare cases where overuse is so significant that we do immediately restrict your use of the service or license factors, and for which we do reserve charging you without having warned you.
Are all API calls counted as the same type?
Yes, we currently count all API calls the same while technically they are not, and highly differ wrt. load on our infrastructure. That said, we constantly monitor our API and reserve the right to throttle or limit any API calls now and in the future, especially if they are “heavy” and threaten to impact our infrastructure to a degree it becomes inoperable for you and other customers. Samples for heavy API calls are: Batch editing of content or list items ((update/delete or assign/unassign layers for many items, especially by filter) with reindexing on content/list items; Schema updates e.g. by changing display patterns; JSON schema/data import or upload/import of Transfers (file content items).
Can I max out my API calls at all times?
No. While you can max out your API calls over a shorter period of time, the effective average number of API calls over a longer period will be lower than the maximum number of calls indicated per plan. This is due to general throttling mechanisms we have in place which limit your API Calls based on your specific and general load, API consumption patterns, and more. However, the higher the maximum defined in your plan, the more you can use on average so it’s good to consider higher plans if you need a higher number of API calls on average and/or for mission critical peak periods.
Can I share API keys with multiple integrators and clients?
While it is not prohibited, we recommend to strictly not share API keys with different clients or integrators. Reasons are: All integrators and clients will receive the same access permissions and will register for the same live stream events, if you use this feature. Additionally, the API call quota is defined per key and then also becomes shared among all clients which might result in lower performance. Debugging becomes complicated too, and other features might be limited. Finally, we also do not warrant any issues arising of or in conjunction with shared API keys.
What Picturepark workflows are available?
As of now, the following workflows exist which all can be triggered on import or update of a content item (content itself or metadata), and also can be defined to meet certain filter criteria for triggering the execution of a workflow:
- Clarifai auto-tagging: Tag images and videos using Clarifai with the option to match Clarifai-provided tags with Picturepark list items in order to support the use of existing controlled vocabularies, and additional features. Note that a Clarifai account is required and not included in our offering.
- Picturepark rule-tagging: Extract select text automatically from any field (incl. e.g. XMP or EXIF information) and copy it into another field or match it with Picturepark list items. E.g. enabling to associate product content based on patterns found in filenames with detailed product information stored on corresponding list items, or importing select set of XMP metadata into specific fields for further editing.
- Picturepark rule-permissions: Add or remove permission sets based on metadata criteria e.g. enabling to publish content to certain user groups via changes in the Copyright or usage permissions. Note: at the moment, time triggered events are not supported (e.g. changing permissions by a certain date and time) this can however be provided via custom integration of a simple time scheduler or BPM systems via you or our partners.
Please ensure to always verify your workflow requirements with a consultant prior to purchasing.
What do I need to consider when purchasing add-ons from Picturepark or 3rd parties, or building custom integrations?
When you are buying any ready-made or custom-developed connectors, microsites or apps from 3rd parties then the app and the data exchanged are subject to the Traffic, API call and API key quotas of your selected subscription plan. Please also ensure that individual users of apps which are capable of writing data into Picturepark via API are properly using a dedicated Read-write user account.
What does the RPO and data retention definitions mean in practice?
The data retention defines the period of time during which we keep backups made from your Customer data (files and object store data) according the RPO defined per plan. In other words: the higher the retention period and the lower the RPO the more likely are we able to recover specific snapshots of your changed Customer data – even if not instantly noticed by you that any such changes were erroneous. If for instance data was accidentally deleted yesterday and you are subscribed to the Premium plan then that deleted data can still be restored from backup versions during a three day period (the retention time) if the deleted data was previously stored for up to 24 hrs – the RPO). Please note that: a) recovery from backups doesn’t necessarily mean that the recovered data becomes available via the Service again (especially for partial data recovery); b) data recovery is subject to reasonable fees unless loss of data has been caused by us; c) we may reduce the amount of backup versions after an initial period of 24 hrs in case of excessive use but shall store no less than a daily snapshot of data for plans with a longer retention time.
What does the “Suisse safe” backup option include?
The Suisse Safe backup option provides you with additional safety by backing up your Customer data onto secure tape backup storage operated in a Swiss Hosting infrastructure that is independent from our primary Hosting infrastructure location and provider. All such backups are made in encrypted format with backup tapes periodically stored offline in a Swiss safe with data retention of up to six months.
What does unlimited mean and which general system limitations apply?
Whenever we speak of “unlimited” or “custom”, system limitations still apply regardless of a plan. Not all limits are hard cut so we might reach out to you in case you overuse, and request a change in usage subject to a grace period (unless you really heavily overused in which case we reserve some more drastic action). In any case, we do not warrant the Service to perform if system limitations are overstepped and also take note that these system limitations will change over time and we explicitly reserve such changes as per the terms of our agreements.
- 100 items referenced per Tagbox or Relationship field
- 100 items of fields added in a fieldset field
- 100 fields per schema
- x Chars/numbers per text or number field etc
- 1000 sortable fields
- 100’000 of active shares and embeds (on aggregate)
- 1000 items per share or embed
- 500 user roles
- 500 permission sets
- 20 Channels
- 100 Languages
- 100 million content or lists items (on aggregate)
- 1000 custom schemas
- 10’000 search-indexed fields
- 100 API keys
- 3000 API Calls per minute