top of page
Frequently asked questions
FAQ
Promises are a way to provide anything-as-a-service.(https://teamtopologies.com/key-concepts-content/team-interaction-modeling-with-team-topologies#:~:text=X%2Das%2Da%2DService%20(XaaS)%C2%A0) They are the building blocks that enable teams to design platforms that specifically meet their customer needs.
Promises have been designed with some key features in mind. Promises:
• enable you to build your platform incrementally and in response to the needs of your users.
• codify the contract between platform teams and application teams to deliver a specific service, e.g. a database, an identity service, a supply chain, or a complete development pipeline of patterns and tools.
• are easy to build, deploy, and update.
• are shareable and reusable between platforms, teams, business units, and other organisations.
• add up to a frictionless experience when platform users want to create services that they need to deliver value.
Learn more about Promises in our docs.(https://docs.kratix.io/main/reference/promises/intro)
Kratix can be installed and resources requested in minutes by following our Quick Start docs.(https://docs.kratix.io/main/quick-start) We recommend attending one of our Kratix workshops that will explain how to install Kratix, request resources and write promises. We have found that after the workshops, a proof-of-concept project typically takes between 1 week and 1 month depending on the complexity of the promise and environment.
bottom of page