Add groups for teams

Support user groups and adding user groups to apps. This makes it easier to manage a team for one organization, while sharing individual apps with specific groups that are a part of that organization.

Snapshot Engine support

Support Snapshot Engine and snapshot reporting in Cloud.

Build rollbacks

Support rolling back to a previous build. We prevent a failing build from taking over a previously running build, but it still can be useful to roll back if a previous change was preferred.

Automatic log summaries

Automatically summarize new logs, and surface recommended solutions if identified.

Revision descriptions

Add descriptions for individual revisions. Can be useful to mirror a git commit message or git sha to a revision.

Migrate apps between teams

Support migrating an app between two teams.

Add file upload support to Cloud

Plotly Cloud has users upload all app files for every revision. However, sometimes app contains files that don’t change from revision to revision, or files which are too large and should be separated from app source code. We would allow users to upload those files separately to their project and read from those files using a consistent path in their app. You could also write to this file store from your app if you want a persistent state from revision to revision. We would want to allow larger file sizes (e.g. up to 2gb) for each file uploaded.

Drag+drop to upload apps larger than 80mb

Plotly Cloud has a hard limit on app upload size of 80mb. Many Dash apps use large flat files as data sources, so this limit can prevent uploading certain projects. It’s possible today to upload a larger app using publish from dev tools.

Virtual private cloud in Plotly Cloud

Allow all apps and resources in a Team to run in a dedicated instance, i.e. not shared with any other teams on Cloud.

Regional instances for Plotly Cloud teams

Allow a Plotly Cloud team to run all of its resources in a specific region, rather than a region managed by Plotly.

Support background callbacks

Allow developers to publish apps that use background callbacks

Admin role for Teams in Cloud

Add an admin role, which is parallel to Creator/Viewer, which allows: Billing access only for admin Add/remove users only for admin Configure SSO for admin Manage roles only for admin etc.

App analytics

Show analytics on app viewership, callback usage, and more in the Plotly Cloud app viewer. Track viewing components Track per user given auth to the team Track callback usage and page viewership How long viewers are on a page Performance profiling information — page load time, refresh, slow pages…

Persistent files for apps on Cloud

Allow uploading files which persist between app revisions and can be accessed from a fixed path in Cloud.

Publish from Github

Publish an app from an existing Github repository

API key support

Allow users to generate API keys for Plotly Cloud access, making it easier to publish to Cloud from a CI pipeline or job.

Publish charts from notebooks

Add a quick action in the modebar for all Plotly charts to publish those charts directly to Cloud. Charts would be wrapped in the requisite Dash code automatically and published.

Publish from Dash devtools

Support app secrets

Today, we support environment variables, but we can provide native secrets support, via e.g. a secrets file, where contents are encrypted in transit. The initial scope of this ticket is to support secret storage for apps in Plotly Cloud, to be leveraged by Plotly Studio directly, but not directly exposed on the frontend. If this proves useful, we will consider adding a user-facing frontend for secrets management in a following iteration.

Fixed IP range for Cloud

Many data sources are behind firewalls that require IP addresses to be allow-listed to connect. Depending on infrastructure, this often means editing your firewall configuration. Providing fixed IP addresses for Plotly Cloud would allow allow-listing access to private infrastructure from a Plotly Cloud app.

Scheduled Tasks in Plotly Cloud

In Cloud, support running tasks outside of apps on a schedule. Cloud would add a management interface for any number of scripts, and a scheduling system to execute those scripts at regular intervals. The scripts would be able to output data to a filesystem accessible to any other apps running under the same user account in Cloud, allowing separation of data retrieval from the apps themselves.

Automate preflight checks

Always-on apps for Cloud

Provide support for always-on apps for Plotly Cloud rather than just on-demand apps, which sleep when no traffic hits them. This would enable apps to have fast response times even after long periods of inactivity, or to run a background process or recurring task safely.

SOC2 compliance