What if Rual pulls the plug?

We've been asked multiple times what would happen if we would cease to exist. While we have no plans of stopping, we understand that doesn't provide any guarantees. Currently we provide two ways of using our platform, you could either buy the platform and take a license for further updates or you could host the platform with us in a shared or private cluster hosted with us.

The latter provides the most risk to our customers in case something may happen, based on the current predicted hosting costs we've prepaid our hosting provider 10 years in advance. Every monthly invoice we receive, we up the open amount to always stay 10 years ahead. This way we minimize the risk our customers will be facing.

Who owns the code?

The code we wrote (the platform), is intellectual property of Deverence Group B.V. All blueprints, logics, comments, documents and architectural choices made within your host are intellectual property of the company paying the license fee on the given host.

We do not own or are allowed to redistribute blocks, blueprints, comments or any other part of your host. We do own the code these blueprints run in. Without a license the use of our platform for personal or commercial use is forbidden, unless the platform has been bought in agreement with Deverence Group B.V.

What's included in your commercial pricing?

We provide this license to use our platform and studio for commercial use, hosted platforms automatically kept up2date with the latest releases, off and on-site back-ups, loadbalancing, enterprise-grade data-storage and 24/7 performance monitoring.

You're allowed to use the platform within the limits of the license of choice, regardless of the numbers of users, blocks, events or blueprints created. This way we hope to provide maximum flexibility combined with high-end hosting.

What is an entity?

The entity is a unique string (mostly a number) linked to a host. Your host and entity together will be your unique connection to your own database, each entity is stored on their own server to comply with the highest security standards.

In all communication on HTTP, HTTPS or WS, you'll need to provide the entity you're trying to grab information from. If you provide an access_token matching a different entity in the same cluster, we'll automatically assume you're trying to communicate using the entity connected with your access_token.