# How to Deploy an Antigravity Website with One Prompt

> Deploy a website built in Antigravity: paste Embarko's deployment prompt into its agent and get a live HTTPS link. No Git or Dockerfile, plus the sandbox fix.

- Page: https://embarko.ai/guides/deploy-antigravity-website
- Updated: 2026-10-14
- Author: The Embarko team
- All guides: https://embarko.ai/guides/llms.txt
- Embarko for agents: https://embarko.ai/llms.txt

---

# How to deploy an Antigravity website with one prompt

**To deploy a website built in Google Antigravity, paste Embarko's deployment prompt into Antigravity's agent.** Copy the prompt from [embarko.ai](https://embarko.ai/), open your project and paste it. The agent packs the folder, uploads it and hands you a live HTTPS link. No Git repo or Dockerfile is needed. Antigravity may ask you to approve the upload, which is normal. [Here is what to expect](https://embarko.ai/guides/deploy-antigravity-website#sandbox).

## Key takeaways

- A website Antigravity builds runs on `localhost`, which only your own computer can open. To share it, it needs a host.
- The usual route asks for a GitHub repository, a hosting account, build settings and secret keys.
- With Embarko, the "one prompt" is the deployment prompt copied from [embarko.ai](https://embarko.ai/). The agent packs the folder, [uploads it](https://embarko.ai/docs/deploy) and [checks the status](https://embarko.ai/docs/status) until the site is `live`.
- Antigravity's terminal sandbox can block network access, so expect it to ask before it runs the upload. Read the command and approve it.
- Your first link needs no account. Press **Keep** within 24 hours and it stays at the same address.

## Why your Antigravity website isn't online yet

When Antigravity builds a website, it runs it on your own machine so you can try it. You'll often see an address like `localhost:3000`. "Localhost" simply means "this computer", so a link that starts with it only works for you. Send it to a friend and it points at their computer, where your site doesn't exist.

Putting a site online is called **deploying**. It takes three things: a server that stays on, your site's files copied onto it, and a public address anyone can open. Together that's called **hosting**. Antigravity writes the site, but something else still has to host it.

## Why deploying from Antigravity gets complicated

Antigravity hands you a project that works. The usual route to a host then asks for more than you may expect:

1. **A GitHub account and a repository**, plus enough Git to push the project.
2. **A hosting service.** Vercel, Netlify and others each have their own sign-up, dashboard and vocabulary.
3. **Build and start settings**, and sometimes a Dockerfile Antigravity didn't write.
4. **Secret keys kept out of the code** and added as environment variables on the host.
5. **Permission prompts and sandbox settings.** Antigravity controls which terminal commands the agent may run and whether they get network access, so even a correct deploy command can stop and wait for you.

That's fair work for a developer. For a small site Antigravity wrote in one sitting, it's a long way from "it runs" to "here's the link".

## The usual route compared with Embarko

Embarko is hosting that your AI tool runs for you. Antigravity's agent packs the site, uploads it and checks that it's live.

| The usual route | With Embarko |
|---|---|
| Push the project to a GitHub repository | No repository. The agent [uploads the folder directly](https://embarko.ai/docs/deploy). |
| Sign up for a host and connect it | Your first link needs no account. |
| Configure the build, maybe add a Dockerfile | No Dockerfile. Embarko [detects the language](https://embarko.ai/docs/deploy) and builds the site itself. |
| Read the build logs yourself | The agent checks the status and hands you the link. |

## What "one prompt" means in Antigravity

The one prompt is Embarko's deployment prompt, a ready-made message that tells the agent how to deploy. It works because Antigravity's agent can run terminal commands in your project. Antigravity comes as an app, a command-line tool and an IDE, and Google's docs describe the permission and sandbox settings for each. The agent follows the prompt, packs the folder, uploads it and reports the live link.

## What to expect when Antigravity asks permission

The upload is a network call from a terminal command, and Antigravity controls both parts. What happens depends on which Antigravity you use:

| Which Antigravity | What it does by default | What to do |
|---|---|---|
| **The app on macOS or Linux** | The Default preset runs terminal commands in a sandbox with no network access. A command that needs the network runs outside the sandbox and asks for your approval, unless an allow rule covers it. | When the agent asks to run the upload outside the sandbox, read the command and approve it. |
| **The app on Windows** | Windows uses Google's previous permission system, where commands you haven't allowed ask for approval. Terminal sandboxing is a preview option. | Read the upload command and approve it. |
| **The CLI** | The sandbox is off by default (`enableTerminalSandbox` is `false`). With it on, sandboxed commands get no network access by default. | Approve the command if the agent asks. With the sandbox on, approve the run outside the sandbox. |
| **The IDE** | Sandboxing is off by default. **Terminal command auto execution** decides whether the agent asks first. | If you turned on terminal sandboxing, also turn on its network access setting, or run the upload in your own terminal. Strict mode turns the sandbox on with network access denied. |

In the app on macOS and Linux, Google's permission presets are **Default**, **Request Review** and **Turbo**, set under **Settings → General → Permission Settings**. Under Request Review the sandbox is off and terminal commands always ask. In the IDE, **Terminal command auto execution** has two options, **Request Review** and **Always Proceed**, which control whether the agent asks before running terminal commands.

You have three ways to get the upload through:

| Option | What to do | What to know |
|---|---|---|
| **Approve the command** (recommended) | When Antigravity asks to run the upload, read the command and approve it. | Check that it only sends your project to `ship.embarko.ai`. A command approved to run outside the sandbox has no sandbox protection. |
| **Allow Embarko's domains** | In the CLI, Google's docs say domains allowed under `read_url` are added to the sandbox's outbound allowlist. Allow `embarko.ai`, `ship.embarko.ai` and `*.embarko.app`. | Google's sandbox page doesn't show the exact rule format, so check its [CLI permissions](https://www.antigravity.google/docs/sandbox?tab=cli) for the current syntax. |
| **Run it yourself** | Ask the agent for the deploy commands and run them in your own terminal. | Nothing is deployed until the upload succeeds, so don't wait for a link before then. On Windows, ask for PowerShell versions that call `curl.exe` and `tar.exe`. |

> Setting names and defaults are from Google's [Antigravity permissions](https://www.antigravity.google/docs/permissions), [sandbox](https://www.antigravity.google/docs/sandbox?tab=cli) and [settings](https://www.antigravity.google/docs/settings?tab=ide) pages as of October 2026. Check those pages if your version differs.

## What you can deploy

Embarko suits small web apps. Here's how common Antigravity projects line up, and what to do if yours needs something else.

| What Antigravity built | Fits? | What to know |
|---|---|---|
| A plain website | Yes | Keep `index.html` at the top of the folder. Published as [static files](https://embarko.ai/docs/static-sites), usually live straight away. |
| A Node.js app | Yes | `package.json` at the top. Read the port from `PORT` and listen on `0.0.0.0`. |
| A Python app | Yes | `requirements.txt` or `pyproject.toml` at the top. |
| A site with a build step (Vite, Create React App) | Yes | Built first, then run as a server app. |
| A small database | Yes, SQLite | Save the file under `DATA_DIR`, [the folder that survives redeploys](https://embarko.ai/docs/data). Keep your own copy of important data. |
| A frontend and a backend in one project | Two apps | [One deploy is one app](https://embarko.ai/docs/two-apps). Deploy each folder as its own app. |
| Postgres or MySQL | Another route | Embarko has [no managed database](https://embarko.ai/docs/data). Use SQLite for small data, or host that app where its database lives. |
| Live updates ([WebSockets](https://embarko.ai/docs/prerequisites)) | Another route | Use regular HTTP polling instead. |
| [Scheduled jobs](https://embarko.ai/docs/prerequisites) | Another route | Run them elsewhere and have them call your site. |
| Heavy processing or a GPU | Another route | Run that part elsewhere. Apps get [256MB of memory and no GPU](https://embarko.ai/docs/deploy). |

**Delete any Dockerfile** Antigravity added. Embarko builds the site itself and [rejects an upload that includes one](https://embarko.ai/docs/deploy).

## How to deploy from Antigravity, step by step

**Before you start:** your site runs locally, and Antigravity's agent can run terminal commands in your project.

### 1. Open the project in Antigravity

Open the folder that holds your site. That folder is what gets uploaded.

### 2. Copy the deployment prompt and paste it into the agent

Open [embarko.ai](https://embarko.ai/) and click the button that copies the prompt (**Host your app** on the home page, **Copy deployment prompt** on [pricing](https://embarko.ai/pricing)). Paste it into a new agent chat, then add one line:

```text
I built a website, help me get it live on Embarko
```

The agent may ask how you want to sign in. Skip the connector option, because Antigravity doesn't have one. Pick **token by email** (give your email, then paste the token from your inbox), or create a token at [embarko.ai/app/tokens](https://embarko.ai/app/tokens). With a token, the app goes into your account and is kept from the start. If you skip, the app still works for 24 hours. [Authentication: three ways in](https://embarko.ai/docs/claim) explains each option.

### 3. Approve the upload

Antigravity may ask before running the upload. Read the command, check that it only sends your project to `ship.embarko.ai`, and approve it. [The table above](https://embarko.ai/guides/deploy-antigravity-website#sandbox) shows when to expect the prompt.

The agent packs the project (leaving out `node_modules`, `.git` and `.env` files), uploads it, and checks the status about every 10 seconds until it reaches `live`. A static site is usually live in the first reply, and a server app builds first, so it takes longer.

The app name becomes your address: 3 to 63 characters (lowercase letters, numbers and dashes, no dash at the start or end), unique across Embarko. If it's taken, the agent picks another. See [app names](https://embarko.ai/docs/deploy).

- A first reply of "202 Accepted" only means the build has started. See [202 Accepted is not live](https://embarko.ai/docs/status).
- If the upload fails with a network error, the sandbox is blocking it and nothing was deployed. See [if something goes wrong](https://embarko.ai/guides/deploy-antigravity-website#errors).

### 4. Open your link and keep it

The agent gives you the address, `your-app-name.embarko.app`. Open it and click around. A link made without a token lasts 24 hours with no reminder email, though an HTML page shows a [countdown banner](https://embarko.ai/docs/claim). The agent's first reply includes a claim link. Open it, sign in or sign up, pick a workspace and press **Keep**, and the app stays at the same address. The link works once and only until the deadline, so keep that message. If you've lost it, ask the agent to [make it permanent with a token](https://embarko.ai/docs/claim).

## Changing the site later

Ask the agent to [redeploy](https://embarko.ai/docs/deploy) with the same name. A kept app needs your deploy token for every later deploy. If you pressed **Keep** on the claim link, the page you land on gives you a prompt that carries a token, so paste it into the agent's chat once. If you kept the app with a token, the agent already has it. You can also create one at [embarko.ai/app/tokens](https://embarko.ai/app/tokens). A kept app keeps [deployment history](https://embarko.ai/docs/rollback) and can [roll back](https://embarko.ai/docs/rollback) to a recent build. Rollback restores code, never data.

To use an API key, keep the app first, then ask the agent to set it as an [environment variable](https://embarko.ai/docs/env-vars) and apply it. A write alone [doesn't reach the running app](https://embarko.ai/docs/env-vars). Static sites can't have environment variables. If your site saves anything, such as form entries or a SQLite file, it must write under `DATA_DIR`, because everything else is wiped on each redeploy. Since Embarko isn't where your code lives, [keep your own copy](https://embarko.ai/docs/rollback) too. A local Git repository is enough.

## If something goes wrong

Failed deploys often come down to a blocked upload, a missing key or setting, or a site listening on the wrong port. Here's what you might see:

| What you see | Likely cause | Fix |
|---|---|---|
| A network or connection error on the upload | Antigravity's sandbox blocks Embarko's domains. Nothing was deployed. | Approve the command to run outside the sandbox, allow the domains ([how](https://embarko.ai/guides/deploy-antigravity-website#sandbox)), or run it in your own terminal. |
| [`403 host_not_allowed`](https://embarko.ai/docs/connectors) | A network sandbox blocks the upload. Nothing was deployed. | Same fix as above. |
| The agent keeps asking before every command | Your permission preset or **Terminal command auto execution** is on Request Review | Approve each command, or add the deploy commands to your allowlist. |
| [Exit code 137](https://embarko.ai/docs/deploy) | The site went over 256MB, often because it runs a dev server | Use the production start command, such as `npm start` after a build, not `vite dev`. |
| [`422 no_manifest_at_root`](https://embarko.ai/docs/errors) | The manifest is in a subfolder | Repackage so it's at the top of the archive. |
| [App gone after a day](https://embarko.ai/docs/claim) | It was never kept | Deploy it again and press **Keep** this time. |
| The link doesn't open, or the status says failed or crashed | The site is listening on the wrong port or only on localhost | Ask the agent: "Make my site read its port from the PORT environment variable and listen on 0.0.0.0, then redeploy." |

Other codes, such as [`409 app_name_taken`](https://embarko.ai/docs/errors), are in the [troubleshooting reference](https://embarko.ai/docs/errors). Don't retry a 409 or 422 unchanged.

## FAQ

### What is Antigravity's terminal sandbox?

It's a restricted space where Antigravity can run the agent's terminal commands. By default in the app on macOS and Linux, commands run there with no network access, so a command that needs the network, such as an upload, runs outside it and asks for your approval. The CLI and IDE have the sandbox off by default.

### Can Antigravity deploy my website?

Yes, if its agent can run terminal commands in your project. It follows Embarko's deployment prompt: it packs the folder, uploads it and returns a live HTTPS link. Copy the prompt from [embarko.ai](https://embarko.ai/), paste it into the agent and approve the command if Antigravity asks. No Git repo or Dockerfile is needed.

### Does Embarko officially support Antigravity?

Not by name. Antigravity isn't mentioned on Embarko's pages and has no Embarko connector. Only Claude has one. Embarko's [connectors page](https://embarko.ai/docs/connectors) says every AI tool can still deploy by pasting the deployment prompt, and that works in Antigravity when its agent can run terminal commands.

### Why does Antigravity ask permission before deploying?

By default, the app on macOS and Linux runs commands in a sandbox with no network access, so the agent asks to run the upload outside it. Read the command, check that it only sends your project to `ship.embarko.ai`, and approve it. On Request Review, it asks before any terminal command.

### Do I need GitHub to deploy from Antigravity?

No. Embarko takes the project folder directly: the agent packs it and uploads it, so there's no repo to create or connect. Embarko isn't where your code lives, so [keep your own copy](https://embarko.ai/docs/rollback), such as a local Git repository or a copy of the folder, so you can redeploy an older version later.

### Will my site stay online?

Once you press **Keep**, yes. An app deployed without a token is deleted 24 hours after its first deploy. Open the claim link from the agent's first reply and sign in to keep it, or ask the agent to [claim it with a token](https://embarko.ai/docs/claim). The link stays the same.

### Is it safe to put my Antigravity site online?

Keep secret keys out of your project files. The agent leaves `.env` files out of the archive, and once you've pressed **Keep** you can add keys as [environment variables](https://embarko.ai/docs/env-vars), which Embarko stores encrypted and nobody can read back. Also remember that anyone with your link can open the site, so if it uses your AI key, set a spending limit with your AI provider if they offer one.

### Is it free?

There's a Free plan with unlimited static websites and **1 dynamic app**. Creator is $9/month billed yearly for up to 5 dynamic apps, and Team is $23/month billed yearly for up to 20. Prices are from [embarko.ai/pricing](https://embarko.ai/pricing) and can change.

## Built something with AI? Ask it to deploy to Embarko.

Copy the prompt, paste it into Antigravity's agent, and get a live link without creating a repo. [Get the deployment prompt →](https://embarko.ai/)

**Keep reading:** [How to deploy an AI app](https://embarko.ai/guides/how-to-deploy-ai-app) · [Deploy from Cursor](https://embarko.ai/guides/deploy-from-cursor) · [Agent quickstart](https://embarko.ai/docs/quickstart) · [Troubleshooting reference](https://embarko.ai/docs/errors) · [Antigravity permissions](https://www.antigravity.google/docs/permissions) · [Pricing](https://embarko.ai/pricing)