---
title: "Deploy Streamlit with your AI in 2026: kept for the team"
url: https://while.sh/en/guides/deploy-streamlit/
author: "Aloïs Oddon, co-founder of Nextmap"
updated: 2026-11-19
---

# Deploy a Streamlit app with your AI, over MCP (2026)

Your Streamlit dashboard runs on your laptop. Connected to while over MCP, your AI deploys it in France, and your colleagues sign in with the company account.

> **The short version.** Over MCP, your AI deploys your Streamlit app with while, in France, private to your colleagues if you want. No Dockerfile, no server. What matters, like deleting a database, waits for a person's approval.

## Prerequisites

- A Streamlit app, with its requirements.txt.
- An AI that works in a terminal: Claude Code, Codex, Cursor or Gemini CLI.

## Step 1: Give your AI this message

Open your AI in your app's folder, and paste this message into it:

```text titre="The message to give your AI"
Connect to while with my account (while.sh/agents), then put my app on while.
```

Without an account, your AI deploys your app as a trial, in one request. To keep it, open the link it gives you and create your account.

With your account, your AI adds while's MCP server itself. If it asks you to, restart it. On the first call to while, a page opens in your browser. In Claude Code, if it doesn't open, type /mcp, choose while, then Authenticate. On that page, choose your app, or "A new app", then click Authorize.

## Step 2: Open your app

Your AI gives you your app's address, for example `https://mon-tableau.while.cloud`, over HTTPS.

## What your AI does

It writes while.yaml at the root of your app:

```yaml titre="while.yaml"
apiVersion: while/v1
project: mon-tableau
services:
  - name: web
    port: 8501
    health:
      path: /_stcore/health
```

Your app is installed from requirements.txt, where Streamlit is detected, then started with `streamlit run`, on `streamlit_app.py` or `app.py`, on its usual port, 8501 (source 1). There is no Dockerfile and no command to write. The connection with your browser stays open: if it drops, Streamlit reopens it in less than a second, and your session carries on.


<figure class="illus"><img src="/illustrations/guide-cadre-production-1200.webp" srcset="/illustrations/guide-cadre-production-768.webp 768w, /illustrations/guide-cadre-production-1200.webp 1200w" sizes="(min-width: 48rem) 46rem, 100vw" width="1536" height="1024" loading="lazy" decoding="async" alt="What your AI does to put a Streamlit app in production on while: the while.yaml file, the build and tests, the HTTPS address, the PostgreSQL database backed up every day and a person's approval, in France" /><figcaption>Your AI writes while.yaml, while builds and serves the app over HTTPS, and the previous version stays ready.</figcaption></figure>

## Restrict your app to your colleagues

> You, to your AI: Restrict the app to people in the company.

Your AI makes the service internal:

```yaml titre="while.yaml"
    access: internal
```

Then it asks for the Access role for your domain, @acme.com, on this app, and a person in your organization approves it.

Once your Google Workspace or Microsoft 365 is linked to while, on the Pro plan, your colleagues sign in with their usual account, and your code receives their name and email address, with no sign-in page to write.

## Read another app's database

> You, to your AI: Connect the dashboard to our app's database, read-only.

Your AI gives your Streamlit app read-only access to the database of another of your apps: the dashboard reads, and can never write.

## Prepare the data every night

> You, to your AI: Prepare the dashboard numbers every night at 3 am.

Your AI declares a scheduled job that computes the numbers and stores them in a PostgreSQL database. Your Streamlit app displays them right away, with no long computation in the page.

## Move to your own domain

> You, to your AI: Put the app on stats.acme.com.

Your AI declares the domain, you add the DNS records it gives you, and the HTTPS certificate follows.

## Go back to the previous version

> You, to your AI: Go back to the previous version.

In the 30 minutes after a production release, the previous version comes back in a second. After that, it takes a few seconds. Once the previous version is back, your AI reads what broke in while's logs, fixes it and deploys again.

## Next steps

- [Restrict an internal tool to company accounts](/en/guides/internal-tool-company-sign-in/)
- [Run a scheduled job](/en/guides/run-cron-job/)
- [Compare Python API hosting](/en/comparisons/python-api-hosting/)

## Sources

1. [Streamlit, server configuration (port, address)](https://docs.streamlit.io/develop/api-reference/configuration/config.toml), 2026-11-02

## Questions

### Do I need to write a Dockerfile?

No. Streamlit is detected in your requirements.txt, and your app starts with streamlit run, with no command to write.

### Does my session hold if I leave the page open?

Yes. The connection with your browser reopens on its own, in less than a second, without losing anything from your session.

### Does a very long computation work?

A computation that takes more than 5 minutes runs separately, at night or in the background, and the app displays the result.

### Do my colleagues need to create an account?

No, on the Pro plan: they sign in with their Google Workspace or Microsoft 365 account.

### Where is my app hosted?

In France, by Nextmap, a French company.
