---
title: "Cursor Apps or while: share a tool built with Cursor (2026)"
url: https://while.sh/en/comparisons/cursor-apps-vs-while-2026/
author: "Grégoire Mougeolle, co-founder of Nextmap"
updated: 2026-11-18
---

# Cursor Apps or while for sharing a tool built with Cursor (2026)

Since November 5, 2026, Cursor builds and hosts a web tool from a single request, with Cursor Apps. We looked at who it can serve, and the answer mostly depends on one thing: do the people who need it have a Cursor account.

Cursor no longer just writes code. Since November 5, 2026, with **Cursor Apps**, Cursor's AI, in the cloud, builds a web tool, adds a Postgres database and sign-in, hosts it and gives you a link (source 1). For your internal tools, it is a strong promise. Before choosing, though, look at **who will need to use it**, because that is where Cursor Apps and while part ways.

> **Our verdict.** while, as soon as colleagues in sales, finance or reception do not have Cursor, or a client needs to use the tool. Cursor Apps only if everyone involved has a Cursor account.

## Cursor Apps and while at a glance

| | Cursor Apps | while |
|---|---|---|
| Who can create | Paid Cursor plans, with cloud work | Your AI: Cursor, Claude, ChatGPT or another one |
| Who can use it | People, groups or the team, behind Cursor sign-in | Your colleagues, a client with a link and a password, or everyone |
| The account required | A Cursor account, except a public tool on an individual plan | A while account, or their email account on the Pro plan; none for a client |
| The data | A Postgres database created when needed | Kept and backed up every day |
| Repositories | Cursor Origin and GitHub | while's repository, or GitHub and GitLab |

## What Cursor Apps does

You ask Cursor's AI, in the cloud, for a tool, and it handles the rest: **the code, the Postgres database, sign-in and hosting** (source 1). If the tool needs to talk to your systems, a data warehouse for example, Cursor asks for the secrets it needs. When you publish, you pick an address, and **security checks** look for secrets left in files or exposed credentials. Nothing goes live until they pass.

Team admins see every tool and every secret, add their own rules to the review, and can unpublish a tool at any time (source 1).


## Who can use it: where the two part ways

A published tool is shared with specific people, groups or your whole team, **always behind Cursor sign-in**. Only individual plans can make a tool public (source 1). For colleagues without a Cursor account, and for your clients, the door stays closed.

<figure class="illus"><img src="/illustrations/cursor-acces-1200.webp" srcset="/illustrations/cursor-acces-768.webp 768w, /illustrations/cursor-acces-1200.webp 1200w" sizes="(min-width: 48rem) 46rem, 100vw" width="1536" height="1024" loading="lazy" decoding="async" alt="Sharing a tool built with Cursor without a Cursor account: Cursor sign-in in front of Cursor Apps, and on while direct access for colleagues and a client with a link and a password" /><figcaption>On while, the tool built with Cursor also serves people who do not have Cursor.</figcaption></figure>

On while, you choose who uses it, starting from the people using it:

- **Your colleagues** sign in with no Cursor account: with a while account for up to 3 people, or, on the Pro plan, with their email account, Google or Microsoft. See [restricting a tool to your colleagues](/en/guides/internal-tool-company-sign-in/).
- **A client or a supplier** uses the tool with [an access link and a password](/en/guides/share-app-with-password/), valid for 1, 7 or 30 days.
- **Everyone**, once a person on your team has approved opening it.

**On this point, while wins**: the tool also serves business teams and clients who do not have Cursor.

## Keep Cursor for coding, and share on while

The two fit together very well. You keep Cursor to build the tool, and **Cursor puts it on while** through while's MCP server, from your project.

> You, to your AI: Put this tool on while, restricted to the sales team, with a link for our client.

The tool **keeps its data, backed up every day**, and its automations run at a set time. The credentials for your other software [stay in while](/en/security/), and Cursor never sees them. Your tools are hosted in France by Nextmap. To compare with Claude artifacts and ChatGPT Sites, read our comparison of [ways to share a tool built with AI](/en/comparisons/share-tool-claude-chatgpt-cursor-2026/).

## Which one to pick, for your team

**Pick while if:**

- The tool must serve colleagues who do not have Cursor.
- A client or a supplier needs to use it, with a password.
- You want data backed up every day and hosting in France.

Pick Cursor Apps only if everyone involved has a Cursor account.

To try while, give this message to your AI, in Cursor or elsewhere. The trial is **free, with no sign-up**, and your tool has its address **in 3 minutes**.

```text titre="The message to give your AI"
Read while.sh/agents and help me get started with while.
```

## Sources

1. [Cursor, Build Live Apps in Cursor](https://cursor.com/changelog/build-live-apps), 2026-11-18

## Questions

### Which Cursor plans include Cursor Apps?

All paid plans where Cursor can work in the cloud. Locally, Cursor does not build these tools (source 1).

### Do you need a Cursor account to use a tool built in Cursor?

For a tool shared with people, groups or the team, yes: it goes through Cursor sign-in. Only individual plans can make a tool public (source 1).

### Does a tool built in Cursor keep its data?

Yes, Cursor creates a Postgres database when the tool needs one, along with sign-in and hosting (source 1).

### How do I share a tool built with Cursor with a client?

On while, a client uses the tool with an access link and a password, valid for 1, 7 or 30 days, with no Cursor account.

### Can I keep Cursor for coding and while for sharing?

Yes. Cursor connects to while through its MCP server, and puts the tool on while from your project.
