# Overview

## What is Cake Red?

It's managed Node-RED inside your Datacake Workspaces. You can purchase Cake Red through an in-portal purchase as a monthly subscription to your workspace. During activation, a separate, self-contained server is provided on which node Red and other components are automatically installed.

## Firewall

Cake Red has an advanced firewall. This allows among other things:&#x20;

* Own whitelisting for URLs (for own APIs)&#x20;
* Port forwarding for UDP and TCP (for incoming server services)

## Public URL

Your server is accessible via its own Cake Red URL. This is structured as follows:

{% embed url="<https://my-workspace-a21c.cakered.io/ui/>" %}
This is just a demo URL - This is what your URL would look like
{% endembed %}

You can use this URL for the following services:

* Hosting the Node-RED Dashboard&#x20;
* Deployment of your own REST-API&#x20;
* Accept incoming connections

## Pricing

Cake Red is available as an optional subscription within your Datacake Workspaces.

It costs: 4&#x39;**,-€** per Month and per Workspace (excl. VAT).&#x20;

![](https://2221155863-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LNA8_b8wmabHgJ0QXoJ%2F-M7D4lBqV76JNLL-C4pr%2F-M7DEpG7YFAA_gT6Y0B1%2FBildschirmfoto%202020-05-13%20um%2015.33.24.png?alt=media\&token=97941bee-2ca5-4f12-a184-e95ab1a9435f)

For this you get:

* Dedicated Virtual Server (non shared)
* 1 Virtual CPU
* 1 GB RAM
* 1 TB Traffic per Month
* 25 GB SSD
* Unlimited Node-RED
* 24/7 Runtime
* Fully upgradable (can install extensions)
* Your own Public URL

## FAQs

### Can I share one Instance between multiple Workspaces?

No. But you can share Devices between Workspaces. So you could create Devices in the Workspaces where Cake Red is installed and create a Flow here that controls the devices. If you want to share this device with other members you can create a separate Workspace and make this device also available through Claiming:

{% content-ref url="../device/claiming" %}
[claiming](https://docs.datacake.de/device/claiming)
{% endcontent-ref %}
