> 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-researchers/work-with-applications.md).

# Run analyses and applications

## Create an Application

<mark style="color:$primary;">**Outcome**</mark>\
You add a new application (JupyterLab, RStudio, MATLAB, VS Code, or similar) to an instance in your project.

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

* You are an **Instance Editor** or **Space Administrator** of the target instance.
* You are in the Current state of the instance.
* You know which application type you need.

#### Add the Application

{% stepper %}
{% step %}
Navigate to the space and the instance.
{% endstep %}

{% step %}
Make sure you are in the **Current state**.
{% endstep %}

{% step %}
On the sidebar, click the screen icon (**Applications**) to open the Applications list.
{% endstep %}

{% step %}
Click **+ ADD NEW APPLICATION** in the top left.
{% endstep %}

{% step %}
In the Application Marketplace, find the Application you want.
{% endstep %}

{% step %}
Click **+ INSTALL**.
{% endstep %}
{% endstepper %}

For all available Applications, their resource sizes, and the full configuration options, see [Reference › Applications](/reference/applications.md).

## Start an Application

<mark style="color:$primary;">**Outcome**</mark>\
You launch an application and open it ready for use.

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

* The application has been added to an instance you have access to.
* You are signed in to Nuvolos.

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

{% hint style="info" %}
Application startup typically takes 30–60 seconds. The first start of a newly created Application may take longer if dependencies are still being initialised.
{% endhint %}

## Stop an Application

<mark style="color:$primary;">**Outcome**</mark>\
You stop a running application to free up resources and stop accumulating NCU or Credit consumption.

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

* You have a running application you want to stop.

Stopping applications when you are done is good research-budget hygiene: you stop consuming resources you do not need. The procedure for stopping an application is the same regardless of the role. See the canonical procedure: [How-to › Common Workflows › Stopping an Application](/how-to-guides/common-workflows/stopping-an-application.md).

{% hint style="info" %}
Nuvolos auto-stops idle applications after 6 hours (Included sizes) or 1 hour (Credit-based sizes) in research spaces. Stopping explicitly frees resources sooner. The inactivity limit can be configured per application - see [Reference › Applications](/reference/applications.md).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.nuvolos.com/how-to-guides/workflows-for-researchers/work-with-applications.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.