# What’s the difference between Embeddable Managed Cube and my own Cube Core / Cube Cloud?

**URL:** <https://community.embeddable.com/t/what-s-the-difference-between-embeddable-managed-cube-and-my-own-cube-core-cube-cloud/171>\
**Category:** FAQs\
**Created:** [March 2, 2026, 4:22pm UTC](https://community.embeddable.com/t/what-s-the-difference-between-embeddable-managed-cube-and-my-own-cube-core-cube-cloud/171 "2026-03-02T16:22:20Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nauman](https://avatars.discourse-cdn.com/v4/letter/n/779978/32.png) [@Nauman](https://community.embeddable.com/u/Nauman)\
**Post date:** [March 2, 2026, 4:22pm UTC](https://community.embeddable.com/t/what-s-the-difference-between-embeddable-managed-cube-and-my-own-cube-core-cube-cloud/171/1 "2026-03-02T16:22:20Z")

</div>

# What’s the difference between Embeddable Managed Cube and my own Cube Core / Cube Cloud?

## What are the two ways to use Cube with Embeddable?

Embeddable supports two ways of working with Cube:

### 1️⃣ Embeddable Managed Cube (Default)

This is the built-in, fully managed Cube layer that comes included with Embeddable.  
It is the default experience and what most of our [documentation](https://docs.embeddable.com/) refers to.

With Embeddable Managed Cube:

- Data modelling is done inside Embeddable.

- Database connections are configured in Embeddable.

- Environments are managed in Embeddable.

- Caching and pre-aggregations are managed by Embeddable.

* * *

### 2️⃣ Cube Core / Cube Cloud (BYOC — Bring Your Own Cube)

In this setup, you run your own Cube instance:

- Self-hosted [Cube Core](https://cube.dev/docs/product/getting-started/core), or

- Managed [Cube Cloud](https://cube.dev/docs/product/getting-started)

You connect your Cube instance to Embeddable via the **[Data Provider API](https://docs.embeddable.com/data/cube-cloud#data-provider-api)**.

With BYOC:

- All data modelling is done in your own Cube instance.

- Database connections are configured in Cube.

- Environments are managed in Cube.

- Caching and pre-aggregations are managed in Cube.

Embeddable connects only through the [Data Provider API](https://docs.embeddable.com/data/cube-cloud#data-provider-api).

* * *

## Why does the UI look different for Cube Core / Cloud customers?

Most of Embeddable’s UI and [documentation](https://docs.embeddable.com/) assume you are using Embeddable Managed Cube.

If you are using Cube Core or Cube Cloud, some features will not appear or will not apply to you — and this is expected behaviour.

Below are the key differences.

* * *

## Why can’t I see the Data Model Editor?

The **[Data Model Editor](https://docs.embeddable.com/data-modeling/getting-setup)** is only available to Embeddable Managed Cube customers.

If you are using Cube Core or Cube Cloud:

- You define and manage models inside your own Cube instance.

- Those models are then synced into Embeddable.

- You do not need the Data Model Editor in Embeddable.

If you cannot see it, nothing is wrong — it simply doesn’t apply to your setup.

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/embeddable1/original/1X/e888641e4ac561a64c1416738d7eced6c7e29e0d.jpeg)

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/embeddable1/original/1X/74c6f34d905764054732f8c1673dff0618688f17.jpeg)

* * *

## What is the “Refresh” button next to Datasets for?

The **Refresh** button is specifically for Cube Core / Cube Cloud customers.

When you:

1. Make changes to your models in Cube, and

2. Want those changes reflected in Embeddable

You must click **Refresh** to sync the updated models via the [Data Provider API](https://docs.embeddable.com/data/cube-cloud#data-provider-api).

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/embeddable1/original/1X/3e21451aff54aaf1df1d9f98afce1470e6adadb6.png)

Embeddable Managed Cube customers do not typically need this.

* * *

## Do I need to use Environments or Connections in Embeddable?

No — not if you are using Cube Core or Cube Cloud.

The following pages are specific to Embeddable Managed Cube:

- **[Environments](https://docs.embeddable.com/data/environments)**

- **[Connections](https://docs.embeddable.com/data/connect-your-database)**

If you are using your own Cube instance:

- Your database connections live in Cube.

- Your environments live in Cube.

- Embeddable only connects through the [Data Provider API](https://docs.embeddable.com/data/cube-cloud#data-provider-api).

* * *

## Which documentation sections do NOT apply to Cube Core / Cloud customers?

The following sections are written for Embeddable Managed Cube customers and are not operationally relevant to BYOC customers:

- Connect Your Data (except [Data Provider API](https://docs.embeddable.com/data/cube-cloud#data-provider-api))

- Data Modelling (except [SQL-Based Security](https://docs.embeddable.com/data-modeling/row-level-security/sql-based-security) (row-level security))

- Caching / Pre-aggregations (managed within Embeddable)

- Embeddable Caching API

Important exception:  
**[SQL-Based Security](https://docs.embeddable.com/data-modeling/row-level-security/sql-based-security) (row-level security) does apply to all customers**, including Cube Core / Cloud.

* * *

## Can Cube Core / Cloud customers still read the data modelling docs?

Yes.

The Embeddable data modelling docs are helpful for understanding concepts.

However:

👉 Your source of truth for modelling, schema definitions, caching, and pre-aggregations is the **[Cube documentation](https://cube.dev/docs/product/introduction).**

All configuration must be done in your Cube instance.

* * *

## What features apply to ALL customers?

The following areas apply equally to both setups:

- Building components

- Creating dashboards

- Embedding

- Theming

- Component SDK

- Row-level security ([SQL-based security](https://docs.embeddable.com/data-modeling/row-level-security/sql-based-security))

Everything related to the UI and embedding experience works the same way.

* * *

## How does Row-Level Security (RLS) work for Cube Core / Cloud customers?

All customers — including [BYOC](https://docs.embeddable.com/data/bring-your-own-cube) — can test RLS in the Embeddable Builder using:

```auto
presets/security-contexts.sc.yml

```

This file defines named security context presets used during testing.

### Example

```auto
- name: default
  securityContext:
    country: United States
    language: English
  dataProvider: default 
 
- name: main-instance
  securityContext:
    country: Germany
    language: German
  dataProvider: main-instance

```

Each preset:

- Defines RLS identifiers (e.g. `country`, `customer_id`)

- Specifies which `dataProvider` to use

This allows you to test [SQL-based security](https://docs.embeddable.com/data-modeling/row-level-security/sql-based-security) directly in the Embeddable Builder.

* * *

## How do Cube Core / Cloud customers connect to Embeddable?

You connect using the **[Data Provider API](https://docs.embeddable.com/data/cube-cloud#data-provider-api)**.

That is the only required integration point.

You do NOT need to:

- Configure database connections in Embeddable

- Set up environments in Embeddable

- Create data models in Embeddable

All of that is handled in Cube.

* * *

## Where do I check errors?

If you are using Cube Core / Cube Cloud:

- Errors originating from Cube must be investigated in your Cube logs and monitoring tools.

- Embeddable does not have visibility into your Cube instance.

If you are using Embeddable Managed Cube:

- Our team has full log visibility.

- We can help investigate lower-level Cube issues directly.

* * *