> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cyberun.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# Request access

> How to apply for the Cyberun Studio private alpha, what to prepare, and what happens next.

Studio is in tight alpha. Seats are opened by use case —
applications are reviewed against the validated production paths
first, so the easier it is to see what you're trying to make, the
easier it is to bring you in.

## Before you apply

You'll be a stronger candidate if you can describe, in a few
sentences:

* **What you want to make.** A short film, a music video, an
  episode, an advert, a game cinematic — anything specific is
  better than "video in general".
* **Roughly how long.** Today's alpha is tuned for short-form work.
  If your project is feature-length, mention it so expectations can
  be set up front.
* **Who's on your side.** A solo creator, a two-person team, a
  studio of ten. Knowing who'll actually be in the product helps
  with seat allocation.
* **What's stopping you today.** "The character changes face every
  shot in tools I've tried" is a useful answer. So is "we already
  have a pipeline, we just want better continuity in the AI step".

None of this is required to apply — but the more context your
application carries, the faster the conversation moves.

## How to apply

The application form lives on the marketing site:

<Card title="Request early access" icon="square-arrow-out-up-right" href="https://www.cyberun.cloud/studio">
  [www.cyberun.cloud/studio](http://www.cyberun.cloud/studio) — request access form.
</Card>

You can also write directly to
[sales@cyberun.cloud](mailto:sales@cyberun.cloud) if you have
specific questions, want to talk things through before applying, or
represent an organisation that needs a different on-boarding path.

## What happens next

1. **Review.** Applications are reviewed against current seat
   availability and how many candidates are in conversation that
   week, so response time varies.
2. **Conversation.** If your project fits a path that's actively
   supported, you'll be invited to a short call so both sides can
   sanity-check the fit.
3. **Invitation.** When a seat is opened for you, you'll receive
   an email with a sign-in link for `studio.cyberun.cloud`.
4. **First project.** Sign in with the email you applied with. If
   you already have a Cyberun Cloud account on that email, Studio
   uses the same identity and team. If not, sign-in creates the
   account.
5. **Onboarding.** The first time you open Studio you'll be guided
   through creating a team (if you don't already have one) and
   starting your first project.

## What to expect from the alpha

* **The feature surface is changing.** Things move week to week.
  When a workflow you used yesterday looks different today, that's
  the alpha working as intended.
* **Your feedback is wanted.** Direct feedback shapes what ships
  next. There's an in-product channel for it, plus the email
  address above.
* **Stability is not yet beta-grade.** Save often. Treat the
  exported cut as the source of truth for finished work rather than
  relying on long-running drafts.
* **Capacity is finite.** Generation runs on a shared platform; at
  busy times you may queue behind other teams.

## Frequently asked

### Is there a cost?

Pricing is not published during the alpha. Each application is
worked through individually.

### Do I need my own GPU?

No. Studio uses the same generation backends as Cyberun Cloud, and
compute is provisioned for you.

If your team already runs its own agents in Cyberun Cloud, those
agents are also available to Studio — reach out via the email
address above to check whether that fits your use case.

### Can I use Studio with my Cyberun Cloud account?

Yes. Studio and Cloud share sign-in and the team model. If your
work email already has a Cloud account, the same email gets you
into Studio once access is granted.

### Can my whole team join?

Yes — Studio uses the same teams as Cloud, so once one member of
a team has access, the others can be added through the standard
team-membership flow.

### What if my project doesn't fit?

If your use case is outside what the current alpha can support,
you'll hear back honestly rather than be left in a queue. You're
welcome to re-apply once Studio expands to your area of work.

## Contact

For anything not covered above, write to
[sales@cyberun.cloud](mailto:sales@cyberun.cloud).
