> For the complete documentation index, see [llms.txt](https://docs.nuvolos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nuvolos.com/how-to-guides/workflows-for-students/start-an-application.md).

# Use applications

## Start an Application

<mark style="color:$primary;">**Outcome**</mark>\
You launch a course Application (RStudio, JupyterLab, MATLAB, VS Code, or similar) and access your course materials inside it.

<mark style="color:$primary;">**Before you start**</mark>

* You have at least one Application configured for your course Instance (your instructor pre-installs these).
* You are signed in to Nuvolos.

The procedure for starting an Application is the same regardless of the role using it. See the canonical procedure: [How-to › Common Workflows › Starting an Application](/how-to-guides/common-workflows/starting-an-application.md).

{% hint style="info" %}
Application startup typically takes 30–60 seconds. The first start may take longer if packages or configuration files need to be initialised.
{% endhint %}

## Stop an Application

<mark style="color:$primary;">**Outcome**</mark>\
You stop a running Application to free up resources.

<mark style="color:$primary;">**Before you start**</mark>

* You have a running Application you want to stop.

The procedure for stopping an Application is the same regardless of the role using it. See the canonical procedure: [How-to › Common Workflows › Stopping an Application](/how-to-guides/common-workflows/stopping-an-application.md).

{% hint style="info" %}
You do not strictly have to stop Applications manually. Nuvolos automatically stops inactive student Applications after one hour. Stopping them explicitly frees resources sooner - useful when your course has a Credit budget or shared GPU schedule.
{% endhint %}