# Where it runs

> Two places to run your shoots: Ondaclip Cloud, hosted by Ondaclip with nothing to manage, or your own infrastructure. Compare them and choose.

You choose where your tutorials are filmed, narrated and edited, once per
product:

- **Ondaclip Cloud**: hosted by Ondaclip. Nothing to set up, nothing to
  manage. Ondaclip runs the shoots and stores the videos.
- **Your infrastructure**: your own cloud project (Google Cloud for now).
  Shoots, demo accounts, models, voices and videos all stay there. An admin
  runs one command, once.

Tutorials, the studio, checks and review work the same way on both. You can
move a product from one to the other later, in its settings.

## Compare

| | Ondaclip Cloud | Your infrastructure |
|---|---|---|
| Who manages it | Ondaclip | You own the project. Ondaclip sets it up once, then keeps only the permissions to start runs and read results |
| Where shoots run | Hosted by Ondaclip, with your workspace isolated from other customers | In your Google Cloud project |
| Demo accounts and secrets | Stored encrypted by Ondaclip, used only to sign in during your shoots, never shown, not even to you | In your project's Secret Manager |
| AI models and voices | Run by Ondaclip, natural AI voices | Run in your project (Vertex AI; Claude through Model Garden if you choose it) |
| Videos | Kept private by Ondaclip; your app reads the published manifest | A private storage space in your project, or a folder your app already reads |
| Billing | Your plan only | Your plan, plus shoots, models and voices on your project's bill |
| Plans | Free and the trial, plus Team and Business | Team and Business |
| Setup | One choice in the studio | One command from a project admin, then the studio does the rest |

### What works only on your infrastructure

None of your code runs on Ondaclip Cloud. These features need your own
project:

- **Commands from your repository** in a tutorial (`run:` in `setup` and
  `cleanup`). See [actions](/docs/actions/).
- **Sign-in written in code** (`signIn` in `tutorial.config.cjs`). On Ondaclip
  Cloud, describe the sign-in form instead.
- **Sign-in with a signed token** (`signIn: firebaseCustomToken`): the token
  is signed by your project's filming account. See
  [a signed token](/docs/signed-token/).
- **Pull request checks on a local app** (`startServer`): Ondaclip Cloud
  films the product's deployed app.

Everything else works on both: forms, demo accounts, every action, the guard,
checks, languages, voices and publishing.

## Choose Ondaclip Cloud

1. In the studio, add the product and connect GitHub
   ([connect your product](/docs/connect-your-product/), steps 1 and 2).
2. At step 3, choose **Ondaclip Cloud**. There's nothing to run.
   Through MCP, your AI agent calls `setup_product` with step `cloud`.
3. Continue with the app, the demo accounts and the first check.

Your workspace is isolated from other customers. Ondaclip keeps nothing from
a shoot except your videos and what your review needs.

## Choose your infrastructure

1. Have a Google Cloud project for the shoots (usually the one for the
   environment you film) and an admin for that project.
2. Follow [connect your product](/docs/connect-your-product/). At step 3,
   enter the project. An admin runs the command the studio shows, once. The
   studio creates whatever is missing, then gives its setup permissions back.
   Through MCP: `setup_product` with step `gcp`, then `plan`, `apply`,
   `finish`.
3. Continue with the app, the demo accounts and the first check.

Nothing leaves your project: the studio only starts runs and reads results.

Source: https://ondaclip.com/docs/where-it-runs/