By role
Platform engineersDesign the paths, review the draftsDevelopersAsk in a sentence, ship the same daySRE and on-callThe cause arrives with the alertHeads of platform and CTOsMake today’s problems impossible tomorrowBy company type
System integratorsForty clients, one practiceSoftware housesSaaS and on-premises, one releaseInfrastructure operatorsDatacenters, tenants, a hypervisor to leave
Your engineers stop doing the work and start approving it.
/healthz. The server answers 404.
Reading the platform.
The last step is yours. Press Approve.
AGENTIKO is made by Krateo and built on Krateo PlatformOps, the open-source control plane these organisations chose.
A ticket is a bug.
Every ticket your platform team receives says one thing: the platform cannot do this yet. You do not fix a bug by processing it faster. You fix what produces it. That is what AGENTIKO does.
“I need an environment for checkout-api.”The same request, every sprint.
Build
AGENTIKO drafts the golden pathThe approved way to request something, which teams then use without a ticket. that was missing. Once a person approves it, the next request is self-service.
“Why does my service keep restarting?”The same page, every night.
Run
AGENTIKO finds the cause and fixes the declarationThe file that describes how a service should be. The platform keeps reality matching it., not the running copy, so the fix survives the next deploy.
“It happened again.”The same lesson, learned twice.
Improve
Every night AGENTIKO reads the day and proposes what the platform should learn, so the same ticket stops coming back.
AGENTIKO proposes. A person approves every change.
Together they make an Intelligent PlatformA platform where declared state and agent reasoning work under the same access rules, and a person confirms every consequential change.. Krateo, a software house in Verona, built Krateo PlatformOps, the open-source control planeThe layer that applies changes to your infrastructure and keeps it in the declared state., and AGENTIKO, the reasoning planeThe layer where agents read the platform, reason about it and draft changes for a person to approve. that works on top of it. Krateo PlatformOps covers Day-1Building the platform: golden paths, self-service, the portal.. AGENTIKO covers Day-2Running and improving it: incidents, upgrades, new pages and integrations..
Reads your platform, reasons about it and drafts changes. Builds, runs and improves. Never applies a change without a person. Perpetual licence, with the model you choose.
Open source under Apache 2.0, already in production. Validates every change, applies what was approved and keeps it true.
Also Azure, Crossplane, Azure DevOps and any API with an OpenAPI spec.
Krateo S.r.l., Verona, Italy. How the two layers work together
Onboard the next client with a change request, and carry every fix across the practice.
See their weekEnvironments on request, and one release for every customer, sovereign installs included.
See their weekLeave a hypervisor wave by wave, and run a sovereign catalogue with a record.
See their weekAGENTIKO proposes changes. Krateo PlatformOps applies them. These results come from the layer that applies them, measured at customers who run it in production.
−70%
maintenance toil across legacy environments and OpenShift
3 weeks → 5 min
to onboard a project across Azure and AWS
2 weeks → 5 min
provisioning on a full Azure estate, through self-service blueprints
AGENTIKO has run at Kiratech since 3 August 2026. Portal pages, root cause analysis and troubleshooting, in alpha, on the platform of a managed service provider.
Krateo works with research institutions on cloud efficiency and open-source AI, and takes part in European programmes for digital sovereignty.
On a hosted sandbox with a sample company loaded. No cluster or card needed.
On a hosted sandbox with a sample company loaded. No cluster or card needed.
Every client is a different estate, and the best fixes live in the heads of a few senior engineers.
Friday, 17:40
AGENTIKO does the work
Reads the new client’s estate, its clusters, Terraform state and pipelines, maps it to the practice’s blueprints and drafts the onboarding as one change request in the client’s git.
A person decides
Your lead architect reviews the plan on Monday morning and merges it. Onboarding starts the same day.
Tuesday, 03:12
AGENTIKO does the work
Diagnoses inside that client’s perimeter, under that client’s policies. Prepares the cause, the evidence and an ordered fix, and drafts the client’s morning report.
A person decides
Your on-call engineer approves from the phone. The client reads who decided, and on what evidence.
Thursday, 02:00
AGENTIKO does the work
The nightly review finds the same health-check fault in eleven other client environments and proposes the fix as a blueprint update for each of them. It ships inert.
A person decides
Your practice lead chooses which clients receive it, and when.
Your best architect’s judgment, applied to every client.
Developers wait for environments, and every regulated customer who installs on premises turns a release into a project.
Monday, 09:10
AGENTIKO does the work
A developer asks in a sentence. The agent follows the golden path the platform team approved: namespace, database, pipeline and a preview address, validated before it applies.
A person decides
The platform team approved the path once. Every order after that runs inside it, and anything outside it comes back as a proposal.
Wednesday, 11:00
AGENTIKO does the work
Drafts the install for that bank’s target, names every key it needs without reading any, and runs a server-side dry run against the bank’s own policies.
A person decides
The bank’s administrator approves in the bank’s git. The secrets stay with the bank.
Saturday, 22:05
AGENTIKO does the work
Correlates logs, metrics and the tenant’s declaration, cites the file it read and proposes the fix with its rollback.
A person decides
The developer on call approves, verifies, and goes back to Saturday night.
Product engineers spend their hours on the product.
The entities want cloud speed, the law wants the data at home, and the hypervisor renewal grows every year.
First quarter
AGENTIKO does the work
Inventories machines and their dependencies, groups them into migration waves towards Kubernetes and Proxmox, and drafts each wave as a change request with its rollback.
A person decides
Your operations lead signs each wave. Every move has a name next to it.
Any working day
AGENTIKO does the work
Drafts it from the service catalogue. Residency, quotas and network rules are enforced by the control plane before anything applies.
A person decides
The entity’s owner approves. The platform refuses whatever the rules forbid, whoever asks.
Every night, 02:00
AGENTIKO does the work
The nightly review reads queue telemetry and the day’s incidents, then proposes alerts, sizing and documentation changes. It holds no tools.
A person decides
Your capacity planner reads the proposals with the morning coffee and adopts what makes sense.
A sovereign cloud catalogue, with the record an auditor asks for.