All-in-One Developer Portal and Cloud Cost Optimizer →
Internal Developer Portal based on a Cloud Management Platform Approach.
Krateo Platformops is an open source platform that gives users the capability to create any desired resource on basically any infrastructure they’d like.
Be it a K8s cluster, microservice, application, pipeline, database or anything else, Krateo has got your back.
The only requirement is for the resource to be descriptible via a YAML file representing the resource’s desired state.
Seamless Integration
Add, manage and improve efficiency in one centralized, self-service software catalog. Enrich it with your stack.
Enhanced Governance
Let Platform Engineers create ‘golden paths’ and standardize processes and stack for your developers. Manage and give access to different, distributed teams.
Reduced TCO & Costs
Reduce expenses over the entire software lifecycle on technical, operational, process and people.
Platform Highlights
These are the main aspects on which our solution is based.
Key Concepts
Our platform is built on these foundations.
core-provider
The core-provider is a Kubernetes operator that downloads and manages Helm charts. It checks for the existence of values.schema.json and uses it to generate a Custom Resource Definition (CRD) in Kubernetes, accurately representing the possible values that can be expressed for the installation of the chart.
composition-dynamic-controller
The composition-dynamic-controller is an operator designed to manage the lifecycle of a Helm chart based on specifications defined within its Custom Resource (CR) and the actions performed on this CR.
provider-runtime
The third component of Krateo Composable Operations (KCO) in Krateo PlatformOps is the 𝘱𝘳𝘰𝘷𝘪𝘥𝘦𝘳-𝘳𝘶𝘯𝘵𝘪𝘮𝘦, our production-grade version of the controller-runtime. Both runtimes can be used to implement Kubernetes operators.
patch-provider
Its primary purpose is to modify a Kubernetes resource’s values by taking another resource’s value as a source and possibly applying transformations.
eventrouter
This service serves as an active watcher of event resource in the kubernetes system, which:
- consider only events related to involvedObjects with a composition identifier
- takes those events and pushes them to a user specified HTTP hook (called Registration)
eventsse
Subscribed to the eventrouter service as event receiver.
- patches the received event adding a label that references the composition to which the event belongs
- stores the event both in an internal queue and in an etcd storage
resource-tree-handler
This service monitors all Kubernetes events that it receives on the /events endpoint to find create/deleted compositions (the events are obtained through an eventrouter registration).
krateo-frontend
Our frontend can be defined as a data-driven meta-framework, but what does that mean exactly? Essentially, we created an architecture that ensures a consistent user experience by design. This is achieved by pre-packaging graphic elements and layouts that can be used and composed to build the portal pages.
snowplow
A critical architectural choice behind Krateo is that there must be no channel-specific logic querying the backend. In other words, what is displayed and implemented via the portal must be exactly reproducible via the Kubernetes CLI (aka kubectl).
finops-operator-exporter
This finops-operator-exporter is tasked with the creation of a generic exporting pipeline, according to the description given in a Custom Resource (CR).
finops-operator-scraper
This component is tasked with the creation of a generic scraper, according to the description given in a Custom Resource (CR). After the creation of the CR, the operator reads the “scraper” configuration part and creates two resources.
finops-operator-focus
This component is tasked with the creation of a generic exporting pipeline, according to the description given in a Custom Resource (CR). After the creation of the CR, the operator reads the FOCUS fields and creates a new resource for the FinOps Operator Exporter, pointing the url field at the Kubernetes API server and the FOCUS custom resource.
finops-database-handler
This webservice acts as a proxy for all requests to the database, including the possibility of performing computations on the stored data.
finops-prometheus-exporter-generic
This component is tasked with exporting in the Prometheus format a standard FOCUS report.
finops-prometheus-scraper-generic
This component is tasked with scraping a given Prometheus endpoint. The configuration is obtained from a file mounted inside the container in “/config/config.yaml”. The scraper uploads all the data to a CrateDB instance, through the finops-database-handler
Insights
All matters regarding our service.
What is Krateo and how does it help my business?
Krateo is a cloud-native platform that simplifies infrastructure management, optimizes cloud costs, and enhances developer experience through automation and composability.
Who should use Krateo?
CTOs, platform engineers, DevOps teams, and IT managers looking to streamline cloud operations, improve developer productivity, and maintain control over infrastructure.
How does Krateo optimize cloud costs?
By leveraging FinOps principles, Krateo provides real-time cost tracking, budget estimation, and automated scaling to prevent resource waste and optimize expenditures.
What kind of support does Krateo offer?
Krateo provides extensive documentation, a community-driven support model, and enterprise support plans tailored to business needs.
Is Krateo compatible with my existing cloud setup?
Yes! Krateo integrates seamlessly with Kubernetes, cloud providers (AWS, GCP, Azure), and other infrastructure tools to fit into your workflow.
Newsroom
Stay updated with our latest articles.
Contacts
Do you want to try our platform?
Request a demo by filling out the form below.