# Create your first Mind

Go from an empty workspace to an instance you can connect to.

Source: https://docs.minds.sh/docs/getting-started/first-mind









Creating a Mind gives your applications a home for memory and knowledge. Both Free and Pro are intended to run dedicated Firecracker VM–based Akasha instances. Free caps usage; upgrading is meant to give the same Mind more room to run.

<Callout title="Deployment requirement">
  The initial audit found Render and Kubernetes provisioning paths. The latest local customer flow now delegates to the new instance service, but its hosted Firecracker lifecycle has not yet been verified. Do not use the plan name alone as proof of the deployed runtime. [Instance model](/docs/concepts/instances).
</Callout>

## 1. Open Helm [#1-open-helm]

After signing in, Minds opens the chat workspace. The current interface labels Helm **Operator**. In an empty workspace, choose **Create a new Mind**.

<img alt="An authenticated empty Minds workspace with the Create a new Mind button" src="__img0" />

## 2. Choose a region [#2-choose-a-region]

Choose a location close to the applications that will use the Mind. The creation card shows the available regions and its current selection. Availability and displayed estimates can change.

<img alt="The region selection step in Minds" src="__img1" />

## 3. Name and review [#3-name-and-review]

Use a name you will recognize later, such as **Research memory**. The creation form accepts 2–40 letters, numbers, spaces, or dashes. Review the selected region and plan, then submit once.

<img alt="The name and plan review step in Minds" src="__img2" />

## 4. Confirm readiness [#4-confirm-readiness]

Wait for the operation to finish, then confirm that the Mind appears in the instance selector. Open its management view and record its endpoint. A submitted request is not the same as a ready instance.

Before integrating it, use the [connection check](/docs/getting-started/connection-check) to verify authenticated access. For a memory workflow, follow that with a write and a separate read of a harmless test record.

## If creation fails [#if-creation-fails]

If the page reports an organization lookup error, resolve the organization selection first. If creation reports HTTP 500, check whether a partial instance exists before retrying. Keep the request time, region, and any visible request ID for support; never include your password or capability in a report.

[Provisioning API](/docs/api/platform/provisioning) · [Troubleshooting](/docs/operations/troubleshooting)