---
title: Data Model IDE
description: Covers the browser code editor for full data modeling features, branch-based dev APIs, and testing model changes before they reach production traffic.
---

Data model editor provides the code-first experience for building and enhancing the
[data model][ref-data-modeling] of your semantic layer from within your web browser.

Unlike the [Visual Modeler][ref-visual-model] editor, it provides the freedom to use all
available data modeling features at the expense of a code-centric experience.

Cube Cloud can create branch-based development API instances to quickly test
changes in the data model in your frontend applications before pushing them into
production.

<iframe
  width="100%"
  height="400"
  src="https://www.loom.com/embed/101b6291b0ba4d1d8982faa3b8c5bd55"
  title="Loom video"
  frameBorder="0"
  allowFullScreen
/>

## Development Mode

In development mode, you can safely make changes to your project without
affecting production deployment. Development mode uses a separate Git branch and
allows testing your changes in Playground or via a separate API endpoint
specific to this branch. This development API hot-reloads your data model
changes, allowing you to quickly test API changes from your applications.

To enter development mode, navigate to the **Data Model** screen and
click **Dev Mode**.

<Frame>
  <img src="https://ucarecdn.com/a35aefc4-8065-4641-a79d-d441d2789c55/" alt="Entering dev mode" />
</Frame>

If you are entering development mode from the main branch, you will be asked to
choose an existing branch or create a new one. You can configure whether it's possible
to commit directly to the main branch in the deployment settings.

<Frame>
  <img src="https://ucarecdn.com/68ed5627-ab7f-4d16-8dc4-90e48c0e6216/" alt="Entering dev mode modal" />
</Frame>

When development mode is active, the status of the development API will be shown
at the top of the screen. After any changes to the project, the API
will hot-reload, and the API status will indicate when it's ready.

You can exit development mode by clicking **Dev Mode X** in the purple banner. If
you've been editing a data model and navigate away, Cube Cloud will warn you if
there are any unsaved changes:

<Frame>
  <img src="https://ucarecdn.com/67b8e943-0043-4398-84fc-91d83765ed10/" alt="Unsaved changes warning modal" />
</Frame>

## Git integration

To add more Git branches to your Cube Cloud deployment and/or switch between
them, click the branch name in the status bar:

<Frame>
  <img src="https://ucarecdn.com/a3ea164f-b93c-4c83-b7a3-697dd025b74a/" alt="Branch switcher" />
</Frame>

Speaking of Git branches, you can now easily add and remove branches with the
same switcher; click **Add Branch** and enter a name for the new branch
in the popup:

<Frame>
  <img src="https://ucarecdn.com/15ea528f-4a54-40a1-83c7-2f67738a3e8b/" alt="Create a new branch" />
</Frame>

These branches are shared, meaning everyone who has access to the deployment can
see and edit them. This makes them extremely useful for out-of-band experiments
where you can quickly test things in Cube Cloud without having to go through a
CI/CD process.

Unused branches can also be deleted. Ensure you are already on the branch you
want to delete, then open the switcher and click **Remove Branch**:

<Frame>
  <img src="https://ucarecdn.com/f1d37fe6-a6ae-4d78-a801-133639daf1ec/" alt="Delete a branch" />
</Frame>

To share a link to the branch you're currently viewing, click the copy-link
button next to the branch switcher. It copies the current URL with
`?branch=<branch-name>` appended; opening that link switches the recipient to
the same branch.

## Generating data model files

You can generate data model files when [creating a new
deployment][ref-creating-deployment] or at later moment. To open the data model
wizard, click on the **...** button on the right and select **Generate
data model**:

<Frame>
  <img src="https://ucarecdn.com/0f9684c2-a7f5-48a2-9fac-32e050beba5d/" />
</Frame>

It is safe to generate data model files for tables that already have matching cubes.
In that case, existing files will be renamed by appending `.backup` to their names.
You would also be able to review changes to files on the **Changes** tab:

<Frame>
  <img src="https://ucarecdn.com/a8d53348-8441-41f3-969c-df46d41d78b6/" />
</Frame>


[ref-data-modeling]: /docs/data-modeling/overview
[ref-creating-deployment]: /admin/deployment#creating-a-new-deployment
[ref-visual-model]: /docs/data-modeling/visual-modeler