Steer your fleet through the clashing rocks.
Tiphys is an AI platform engineer for the orchestrators you run. It reads your clusters, cloud accounts, and repositories, diagnoses problems with live data, and charts a fix. Nothing changes until you give the word.
In Greek myth, Tiphys was the helmsman of the Argo. He read the stars and the wind and steered Jason's crew through the Clashing Rocks. Tiphys does the same for your workloads, whatever orchestrator they run on.
Watch the crew at work.
Short loops from the product, running on sample data.
Lynceus diagnoses a flapping service and waits for approval before changing anything.
Two to steer, one to build.
Ask in plain language. Tiphys hands the work to the right crewmate and passes it between them when a problem crosses boundaries.
Lynceus
The lookout, who could see through sea and stone.
Diagnoses workloads, services, and nodes from live orchestrator state, logs, events, and metrics, so you see trouble before you hit it.
- why is checkout restarting?
- which workloads have no resource limits?
- rotate secrets for payments-svc
Aeolus
Keeper of the winds, who stilled them for the Argo.
Keeps cloud spend on course. Finds drift, idle resources, and right-sizing opportunities across your accounts.
- why did compute spend jump last week?
- list unattached volumes
- which databases are idle?
Argus
The shipwright who built the Argo.
Builds services, environments, and pull requests from your own templates and conventions.
- spin up a staging env for notifications-api
- which services drift from our template?
- scaffold a new Go service
Nothing changes without your approval.
Tiphys reads freely and writes carefully. Every change is proposed, reviewed, signed, and recorded.
Read-only by default
Tiphys runs under service accounts and IAM roles you scope. Writes are off until you enable them.
Approval gates with diffs
Every write arrives as a plan with its impact, a diff, and a dry-run result. You apply, reject, or edit it.
Signed and reversible
Applied changes carry a signature and a rollback token, so any change can be traced and undone.
The ship's log
Every query and action is written to an append-only, hash-chained log you can export to your SIEM.
| Time | Actor | Action | Result | Approver |
|---|---|---|---|---|
| 14:33:52 | lynceus | kubectl.patch | ok | jamie@acme |
| 14:33:44 | lynceus | plan.generated | approved | jamie@acme |
| 14:32:58 | lynceus | prometheus.query | ok | — |
| 14:32:22 | lynceus | kubectl.logs | ok | — |
| 14:18:44 | aeolus | cloud.tag | ok | — |
| 14:11:32 | argus | idp.pr.draft | queued | — |
| 14:04:01 | lynceus | secret.rotate | blocked | needs approval |
Works with the stack you already run.
Connect once. Tiphys reads from your existing tools and follows the conventions it finds there.
- Kubernetes
- EKS · GKE · AKS
- OpenShift
- More on the way
- AWS
- Google Cloud
- Azure
- GitHub
- GitLab
- Argo CD
- Terraform
- Prometheus
- Grafana
- Datadog
- PagerDuty
- Slack
Priced by the clusters you connect.
Every plan includes approval gates, the ship's log, and organization knowledge.
Team
For a single platform team getting started.
- Up to 3 clusters
- 1 cloud account
- Lynceus and Aeolus
- 30-day log retention
Business
Most teamsFor organizations running production across regions.
- Up to 15 clusters
- Unlimited cloud accounts
- The full crew, including Argus
- SSO and role-based access
- 1-year log retention
Enterprise
For regulated environments and large fleets.
- Unlimited clusters
- VPC or self-hosted deployment
- SIEM export and custom retention
- Dedicated support
Already an Intelligant AI customer? Ask about adding Tiphys to your plan.
What teams ask first.
Does Tiphys change anything without asking?
No. Tiphys is read-only by default. When you enable writes, every change is presented as a plan with a diff and impact summary, and nothing is applied until someone with permission approves it.
What access does Tiphys need?
A service account for your orchestrator and a cloud IAM role, both created and scoped by you. Start with read-only roles and widen them per namespace or account when you're ready.
Who are Lynceus, Aeolus, and Argus?
They're the three agents inside Tiphys, named for their jobs. Lynceus watches your clusters, Aeolus keeps cloud spend on course, and Argus builds new services and environments.
How does Tiphys learn our conventions?
It observes your manifests, repositories, runbooks, and past changes, then records the patterns it finds with a confidence score. You can review, edit, or remove anything it has learned.
Where does our data go?
Cluster and cloud data is processed to answer your questions and is not used to train models. Enterprise plans can run Tiphys inside your own VPC.
What happened to Clu?
Clu is now Tiphys. It's built by Intelligant AI and has moved from getclu.dev to tiphys.intelligant.ai.
See Tiphys steer your own fleet.
In a 30-minute demo we connect Tiphys to a test cluster and walk through a real diagnosis. If you're not ready yet, join the waitlist and we'll let you know when your spot opens.