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 leaveA perpetual licence for the clusters AGENTIKO looks after. Invite everyone who should review and decide: people never count as seats.
Sandbox
Freefor 5 days
Your first approval on a hosted cluster with a sample company.
Open a sandboxPlatform
Per clusterup to 3 clusters
One platform team running its own estate.
Get a quoteScale
Per clusterup to 10, then per cluster
Many teams, tenants or clients.
Talk to an architectEnterprise
Customperpetual licence
Regulated and sovereign estates.
Talk to an architectFigures depend on how many clusters AGENTIKO looks after. What you need to start.
Value grows with the people who review and decide. A seat price would push the other way.
A perpetual licence for each cluster the agents look after. Easy to count, nothing metered.
Bring the model provider you already contract. Its cost stays on your own invoice.
A licence per managed cluster, with partner margin. Write your runbooks and procedures as your own agents, in YAML, and deliver an Intelligent Managed Platform to every client. Kiratech did it first.
| Sandbox | Platform | Scale | Enterprise | |
|---|---|---|---|---|
| Platform | ||||
| Clusters | 1 hosted | 3 | 10, then per cluster | Unlimited |
| Approvers | Unlimited | Unlimited | Unlimited | Unlimited |
| Build, Run, Improve agents | ✓ | ✓ | ✓ | ✓ |
| Workspaces per tenant or client | No | No | ✓ | ✓ |
| Control and sovereignty | ||||
| Where it runs | Our cluster | Your cluster | Your cluster | Your perimeter |
| Model | Included | Your key | Your key | Your key or in-perimeter |
| Single sign-on | No | Add-on | ✓ | ✓ |
| Audit history | 5 days | 30 days | 1 year | Custom |
| Support | ||||
| Channel | Docs | Shared channel | Priority | Named architect |
| Response times | No | Working hours | Business SLA | Up to 24/7 |
| Add-ons | No | Managed by Kiratech, VM Away migration, extra clusters | ||
Any Kubernetes cluster AGENTIKO reads from or proposes changes to.
Every approval is a person deciding. We want more of them, and a seat price would make you invite fewer.
You contract the model provider directly, and its usage appears on your own invoice.
The control plane is open source under Apache 2.0. Enterprise support for it is part of Scale and Enterprise.
It is deleted after 5 days. Nothing is charged, and you can export the blueprints you approved.
Every approver is included. Tell us how many clusters AGENTIKO should look after.
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.