About KronoGraph

Overview

KronoGraph is always in development, so we add, improve and remove features based on the needs of our products and customers.

Some features might first be introduced as alpha or beta before they become a stable part of KronoGraph. However, any new feature will be fully tested.

Sometimes we need to deprecate APIs and make breaking changes.

Alpha Features

Alpha features will be marked in the API using an Alpha tag.

  • This is a developmental stage, so we might introduce breaking changes to the API. These will always be announced in the Release Notes.
  • You shouldn't use alpha features in production.
  • We don't provide customer support for alpha features used in a production environment, but we do support alpha features in a development environment.

If you need any help with an alpha feature please contact support.

Beta Features

Beta features will be marked in the API using a beta tag.

  • Some features are introduced as beta from the start, while other alpha features move to beta after further development based on user feedback.
  • This is still a developmental stage, so we might introduce breaking changes to the API. These will always be announced in the Release Notes.
  • You can deploy beta features to production, but note that breaking changes will affect your production upgrades.

Once we've made all intended improvements to beta features, they move out of beta and become a stable part of KronoGraph.

If you need any help with a beta feature please contact support.

Deprecated Features

Deprecated features will be marked in the API using a deprecated tag.

  • You should stop using deprecated features and update your code as soon as possible.
  • All deprecated features will be announced in the Release Notes along with code change suggestions if necessary.
  • We will keep deprecated features available for your use until the next major release.

If you need any help with a deprecated feature please contact support.

Breaking Changes

Breaking changes could be an API update, a replacement feature or a visual change. They can cause your application to stop working.

  • Breaking changes will always be announced in the Release Notes.
  • Most breaking changes happen in a major release, however some breaking changes might be introduced in minor releases.
  • Check your code to see if it is affected by the change and make any changes necessary.

If you need any help with a breaking change please contact support.

Terms of use

These terms do not alter or supersede any existing agreements between you (or your employer) and us.

By accessing or using any Content you agree to be bound by these Terms of Use. Please review these terms carefully before using the website.

The contents of this website, including but not limited to any text, code samples, API references, schemas, interactive tools, and other materials (collectively, the 'Content'), are made available for informational and internal evaluation purposes only. All intellectual property rights in the Content are reserved. No licence is granted to use the Content for any commercial purpose, or to copy, distribute, modify, reverse-engineer, or incorporate any part of the Content into any product or service, without our prior written consent.

This Content is provided “as is” and “as available,” without any representations, warranties, or guarantees of any kind, whether express or implied, including but not limited to implied warranties of merchantability, fitness for a particular purpose, non-infringement, or accuracy. To the fullest extent permitted by applicable law, we expressly exclude and disclaim all implied warranties, conditions, and other terms that might otherwise be implied.

We disclaim all liability for any loss or damage, whether direct, indirect, incidental, consequential, or otherwise, arising from any reliance placed on the Content or from your use of it, to the fullest extent permitted by applicable law. By continuing to access or use the Content, you acknowledge and agree to these terms.