# Create a project (/create-a-project)



## What you choose [#what-you-choose]

Start with a name. Crucible derives the rest and handles setup that would otherwise span several tools and infrastructure workflows.

Select **New Project** to open **Create project**. The project belongs to your current organization, which needs GitHub connected; **Organization settings** shows the connection under **Connections**.

* **Display name**: The name people see, 3 to 30 characters. Crucible derives the **Project slug** from it as you type.
* **Project slug**: The project id. Crucible also uses it for the repository name and the lite deployment's subdomain.
* **Advanced settings**: Override the **Repository name**, choose **Hosting** when your organization has Azure or AWS connected alongside Ciridae (GCP), and choose a **Template** when more than one is enabled. The default template is the [Agents template](/agents-template/).

Select **Create project**. The project page opens and shows each setup step as it runs.

## What you get [#what-you-get]

* **[A workspace ready to build in](/workspaces/)**: **Starter Workspace** opens as soon as setup finishes, with an agent, terminal, and live preview.
* **[A live URL from the start](/deployments/lite-deployment/)**: A lite deployment named **Dev** publishes `main` at the generated URL, ready for demos and early feedback. Add a [full deployment](/deployments/full-deployment/) when production users need dedicated operations.

<Accordions>
  <Accordion title="Under the hood: what creation starts">
    Project creation is a durable workflow rather than a single database write. The [provisioning workflow](/provisioning-workflow/) maps the complete sequence.

    1. Crucible records the project and makes you its project admin.
    2. It creates the sandbox and production Auth projects. The sandbox project accepts local sign-in callbacks.
    3. It creates the GitHub repository and bootstraps it from the selected template.
    4. It adds the template's default integrations, declared in `project.yaml` under `template.default_standard_api_integrations`. The Agents template declares Auth Service, LLM Gateway, Temporal, Modal, Ghost Envs, Ciridae MCP, and Linear Feedback.
    5. It pre-creates the lite deployment and the starter workspace, then provisions both in parallel through their own workflows. The lite deployment tracks `managed_environments.deployment.default_branch` (`main` in the Agents template).

    **New Project** requests no full deployment. The Agents template declares a `prod` full deployment on the `prod` branch; add it with **New deployment** when you need it.
  </Accordion>
</Accordions>