🎧Support
Whether you're using our Community Edition or Enterprise Edition, this page is your starting point for getting help, and resolving issues quickly. If you need immediate assistance, please reach out to our support team. Email: [email protected] Community Edition Slack: Join here Enterprise Edition Slack: for our Enterprise customers, we typically set up a private Slack channel for faster, real-time support. If you're an Enterprise user and not yet a member of your dedicated Slack channel, just let us know and we’ll get you added right away.
Community Edition or Enterprise Edition?
Not sure what edition you're using? No worries—we’ve got you covered.
If you open Supervisely at
https://app.supervisely.com
, you're using the Community Edition.If you're accessing it through any other address, you're on the Enterprise Edition.
Enterprise users receive high-priority support—you can reach out to us directly, and we’ll do our best to resolve your issue as soon as possible. If you're contacting us from a personal email address, please mention that you're an Enterprise user to help us prioritize your request.
Cloud-hosted Enterprise Instances
If your Supervisely server address ends with enterprise.supervisely.com
, you're using an Enterprise instance hosted in our Cloud.
This means the Supervisely team is actively managing the server, including updates, backups, maintenance, logs, and troubleshooting. You do not need to collect or send a troubleshooting archive, just contact us directly, and we’ll take it from there.
I Have an Issue
If something’s not working as expected in Supervisely, let’s first narrow down what kind of issue you're facing:
You're having trouble with an app from the Supervisely Ecosystem (or a custom app).
You see an error message in the UI outside of the app (e.g. "Something went wrong").

The platform isn’t throwing errors, but it feels slow or laggy.
Things technically work, but the behavior seems off or unexpected.
You're running into a technical issue with the API or SDK.
You're an Enterprise technical engineer and need help with deployment.
Once you’ve identified the type of issue, scroll down to find the best way to get support.
Issues with Applications
If you're having trouble with an app from the Supervisely Ecosystem (or a custom app), here are some steps you can take:
Check the app's README section and ensure that you followed all setup instructions.

If there are some specific error messages while running the app, please download its logs and share it with our support team.
How to download application logs?
Open the
Tasks & Apps
section in the left sidebar.Check if the needed session is in the
Tasks
tab.

Click on the three dots icon and select the
Logs
option.

In the opened window, click the
Download Logs
button.

If you didn’t find anything in the Tasks tab, then go to the Apps tab:
Open the
Apps
tab, find the needed application and click on the button under it. Then simply click on theOpen error log
.

Click on the
Download Logs
button.

Now, when you downloaded the logs, please share them with our support team for further assistance.
Changing the log level of application
In some cases, we'll need additional logs to diagnose the issue. You can change the log level in two ways:
Option A — Start a new app session with a different log level
Launch the application and click on the
Advanced settings
option.Set the
Log Level
toDebug
orTrace
to capture more detailed logs.Start the application.

Option B — Re-run the same session with a different log level
Open
Tasks & Apps
and find the previous session.Click
Run Again
.In the relaunch dialog, open
Advanced settings
and set theLog Level
toDebug
orTrace
.Start the application.

What happens next
If the app runs with saved inputs, it will automatically repeat the same scenario with the new log level.
If it does not, it will start with the same parameters as last time and be ready for work.
Now, use the application to reproduce the issue. When finished, please download the logs and share them with our support team.
Issues with the platform
If you encounter an error in the graphical user interface while not using any specific application:
Community Edition: Please contact our support team with a description of the issue.
Enterprise Edition: Before reaching out, if you're not using Cloud-hosted Enterprise Instance, and the Remote Logs feature is not enabled, please generate a troubleshoot archive and share it with our support team. This helps us resolve your issue faster.
Enabling Remote Logs
When something goes wrong, the fastest way for our team to help is by seeing what the system sees. Remote logs allow Enterprise customers to securely send system-level logs to the Supervisely team in real time—so we can diagnose and resolve issues without needing a manual troubleshooting archive.
To enable remote log forwarding, run:
sudo supervisely enable-remote-logs
To disable it at any time, use:
sudo supervisely disable-remote-logs
What’s sent? Only system logs.
Remote logging transmits only non-sensitive system-level diagnostics such as service status, error traces, and performance metrics. It does not include any personal data, customer content, project files, credentials, or identifiable information.
We take customer privacy seriously. Remote logs are strictly limited to what’s necessary for technical troubleshooting and are handled securely by the Supervisely team. This ensures faster support without compromising your data integrity or confidentiality.
Slow performance
If you notice that the platform is running slowly, and you're using the Community version of Supervisely, perform a speed test and contact our support team with the results.
For Enterprise version of Supervisely, please do the following:
Open any Labeling Toolbox (such as Image Labeling Toolbox).
Find the Troubleshoot button on the bottom right corner and click it.

Perform the Troubleshoot test, save the results (text or screenshot) and share them with our support team.

Performing a speed test
If you are using the Community Edition of Supervisely, you can perform a speed test to check your connection to our servers. You can use any online speed test tool, such as Speedtest.net, and share the results with our support team. Note, that the speed test should be performed to specific location that matches the region of the Supervisely instance. For example, for the Community Edition, use a server located in Germany (Falkenstein).
Unexpected behavior
If you don't see any errors, but it looks like that something is not working as expected, please try the following steps:
Ensure that you're using latest version of Chromium-based browser (Google Chrome, Microsoft Edge, etc.).
Try the same in the incognito mode with all the extensions disabled.
Clear your browser cache and cookies.
Try using a different browser or device.
If it did not help, check if there any errors appear on the Developer Console. To do it:
Right-click on the page and select "Inspect" (or press Ctrl+Shift+I) to open the Developer Console.
Go to the "Console" tab and look for any error messages.
If the issue persists, please contact our support team with a detailed description of the problem, including any steps to reproduce it as well as screenshots from the Developer Console. In some cases the screen recording of the issue can be helpful as well.
Python SDK or API issues
If you're using our Python SDK or the API directly and encounter an issue, please follow these steps:
Ensure you are using the version of SDK that corresponds to your Supervisely instance. You can check the compatibility table here.
Check out the SDK Reference to make sure you are using the correct methods and parameters.
If you're using the API directly check out the following documentation: Community version API documentation For Enterprise version, the link to the documentation is:
<your-enterprise-domain>/api-docs/
After checks, if you still encounter issues, please contact our support team with a detailed description of the problem. We also appreciate if you could provide any relevant logs, error messages or code snippets to help us assist you better.
Deployment issues
First of all, check out the Enterprise documentation:
If you did not find a solution in the documentation, please contact our support team, and we will do our best to assist you.
Last updated