# Syntasso Kratix Enterprise (SKE) {% hint style="info" %} Cortex connects to many third-party vendors whose system interfaces frequently change. As a result, integration behavior or configuration steps may shift without notice. If you encounter unexpected issues, check with your system administrator or refer to the vendor's documentation for the most current information. Additionally, integration sync times vary and are subject to scheduling overrides and timing variance. {% endhint %} [Syntasso Kratix Enterprise (SKE)](https://www.syntasso.io/) is an enterprise-grade platform orchestrator built on [Kratix](https://kratix.io/), an open-source framework for building internal developer platforms on Kubernetes. SKE enables platform teams to deliver self-service infrastructure and services through composable, API-driven abstractions called [Promises](https://docs.kratix.io/main/reference/promises/intro). Integrating SKE with Cortex allows you to: * Dynamically create [Workflows](/streamline/workflows.md) in Cortex that map to Kratix Promises, enabling developers to self-service Kubernetes resources * Register and update entities in Cortex that represent Kubernetes resource definitions managed by SKE * Provide a portal-driven experience where developers can request and manage platform capabilities without needing to learn YAML or kubectl {% hint style="info" %} This integration was built and is maintained by the Syntasso team. For setup and configuration, refer to the [SKE documentation](https://docs.kratix.io/ske). {% endhint %} ## How to configure SKE with Cortex ### Prerequisites Before getting started: * You should have a working [SKE installation](https://docs.kratix.io/ske). * You should have Promises configured in your SKE environment. * You will need a [Cortex API key](/configure/settings/api-keys.md) to connect SKE to your Cortex workspace. ### Configure the integration SKE connects to Cortex via the [Cortex API](https://docs.cortex.io/api). Configuration is managed on the SKE side — refer to the [SKE documentation](https://docs.kratix.io/ske) for detailed setup instructions. Once configured, SKE will automatically create and manage [Workflows](/streamline/workflows.md) in Cortex based on the Promises defined in your platform. ## How the integration works ### Kratix Promises Promises are the core abstraction in Kratix and SKE. A Promise defines a platform capability — such as a database, CI/CD pipeline, or Kubernetes cluster — as a self-service API. Promises encapsulate validation, provisioning, policy enforcement, and Day 2 lifecycle management into a single, governed contract between platform and development teams. When SKE is integrated with Cortex, these Promises are surfaced as Workflows, allowing developers to request resources through the Cortex UI. ## Using the SKE integration As platform adoption grows, a common challenge emerges: *What do we actually have, who owns it, and is it compliant?* The SKE integration with Cortex connects orchestration with organizational visibility, helping teams treat their platform as a product — one that is not only easy to consume but also measurable, governable, and continuously improved. Once configured, SKE dynamically creates, adds, and updates Promises for Kubernetes resource definitions in Cortex, giving platform teams a unified portal experience for managing platform capabilities. ## Demo See the video below for a demonstration of the Kratix integration with Cortex. {% embed url="" %} ## Learn more * [Syntasso website](https://www.syntasso.io/) * [Kratix documentation](https://docs.kratix.io/) * [SKE documentation](https://docs.kratix.io/ske) ## Still need help?[​](https://docs.cortex.io/docs/reference/integrations/aws#still-need-help) The following options are available to get assistance from the Cortex Customer Engineering team: * **Email**: , or open a support ticket in the in app Resource Center * **Slack**: Users with a connected Slack channel will have a workflow added to their account. From here, you can either @CortexTechnicalSupport or add a `:ticket:` reaction to a question in Slack, and the team will respond directly. Don't have a Slack channel? Talk with your Customer Success Manager. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.cortex.io/ingesting-data-into-cortex/integrations/syntasso.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.