ABOUT
Named after a guardian that never slept.
Talos was the bronze automaton Hephaestus forged to guard Crete. It circled the island three times a day, tireless and watchful, and it did the same job every time without being asked. That is a fair description of what infrastructure work should be, and an unfair description of what it usually is.
WHY IT EXISTS
It started as a runbook that stopped scaling.
Talos began with Frappe and ERPNext infrastructure managed the way most of it is managed: SSH, a folder of shell scripts, and a person who remembers which server does what. That works for three servers. At fifteen it becomes the job. At forty it becomes the reason nothing else gets done.
The specific thing that pushed it from scripts to a product was not scale, though. It was the realisation that none of it was reviewable. A destructive operation ran because one person decided it should, produced output into a terminal that got closed, and left no record anybody could query afterwards. Every part of Talos that looks like bureaucracy (tracked jobs, approval gates, the audit ledger) exists because of that.
It grew outward from Frappe because the same problem exists one layer down and one layer up: the Docker host underneath, the cloud account around it, the cluster next to it. The idea is that one control plane over all of them is worth more than four good tools that do not know about each other.
WHO IS BUILDING IT · TALOSFLEET
TalosFleet: an independent team of three, not a company.
Talos is built and owned by TalosFleet: Paras Jain, Aryan Mishra and Vaibhav Rana. It started inside medecro.ai, where the three of us work, as the tool that runs the company’s own infrastructure, and medecro.ai still runs on it. Talos is our first product; TalosFleet is the name we build under.
TalosFleet is not yet a registered company. It has no outside funding and no sales department, and we want that to be clear from the start.
Practically, it means three things. We cannot take payment yet, so the planned paid plans, Talos SaaS and AI tokens supplied by Talos, are not on sale; self-hosted Talos is free and stays free. There is no support contract, only the three of us answering email. And the licence question is open, which is listed below as something we intend to resolve.
Built by Paras, Aryan and Vaibhav · meet the team →WHERE IT ACTUALLY IS
What is proven, and what is not.
Feature lists flatten everything to the same confidence. This does not.
USED IN PRODUCTION
BUILT AND TESTED, NEWER IN PRODUCTION
BETA: BUILT, VALIDATION IN PROGRESS
BETAWHAT IS NEXT
Four things, in roughly this order.
Prove the beta capabilities
Hypervisor, Proxy, DNS & SSL, MCP and MLOps against the real things they manage; the AI Engine end-to-end with a live key. Each loses its beta label by being exercised, not by being declared ready.
An independent security audit
Not yet scheduled. It is planned once funding allows.
Publish the licence
The repository does not yet include a LICENSE file. Publishing one will set out clearly the terms under which you can run Talos.
Documentation depth
The docs cover installing and operating. Per-capability reference comes next.
On the name
This Talos is the DevOps control plane built by TalosFleet. There are other things called Talos in adjacent territory: Talos Linux from Sidero Labs, and Cisco Talos in threat intelligence. We are not affiliated with either; Talos can manage Kubernetes clusters whatever operating system their nodes run. If you arrived here looking for one of those, we apologise for the confusion.
Free to self-host, on a machine you already have.
The fastest way to judge any of the above is to install it and point it at one server.