← All products
The SRE for your container services

Tiphys

Builds, scales and runs your services, and fixes what breaks. It asks before it changes anything.

Builds, scales and runs container services on Kubernetes, on any cloud or your own hardware, checks them continually, finds why something broke and proposes the fix. Use it as a SaaS or On-Prem. Every change waits for approval, and model use is included in every plan.

app.tiphys.intelligant.ai

Name
Helmsman of the Argo, who steered it through the Clashing Rocks.
Runs
SaaS or On-Prem; Kubernetes today, more orchestrators coming
Model
Included; your own on Enterprise
Changes
Approval-gated and logged
What it does

The SRE legwork, off your team’s plate.

Build and scale

Images, service definitions and rollouts, and the capacity to carry the load, written for your team to approve.

Find the cause

Ask why a service is failing. Tiphys reads logs, events, metrics and configuration and tells you what it found.

Propose the fix

The fix comes back as a change to the service or its configuration, with a diff and its impact, for your team to review.

Keep the record

Every query and action goes into the audit trail, which you can export, and every change waits for a person’s approval.

See it work

Ask if you’re ready. It checks.

Asked whether a cluster is ready to deploy from its repository, Tiphys checks, finds the gap and asks PETROS for the platform part. Once it's merged, Tiphys installs it one approved step at a time and checks its own work: yes, you can deploy.
Works with

What Tiphys connects to.

Available means built, tested and supported today. Beta works, with the gap noted. Coming is planned and not built yet; ask us if you need it.

Clusters

  • KubernetesAvailable
  • Amazon EKSAvailable
  • HelmAvailable
  • Helm on connector clustersinstalls only, SaaSBeta
  • Google GKE, directlyComing
  • Azure AKS, directlyComing
  • Amazon ECSComing
  • HashiCorp NomadComing

Cloud

  • Amazon Web ServicesAvailable
  • Google Cloud accountsComing
  • Microsoft Azure accountsComing

Code

  • GitHubSaaS onlyAvailable
  • GitHub pull requests for fixesa person merges, SaaS onlyBeta

Delivery

  • Argo CDAvailable

Metrics

  • PrometheusOn-Prem onlyAvailable
  • Amazon CloudWatchAvailable
  • GrafanaPromQL through a Prometheus data sourceBeta
  • Datadog metricsmetric queries onlyBeta

Alerts and on-call

  • Prometheus AlertmanagerBeta
  • PagerDutyBeta
  • Datadog alertsBeta

Chat

  • SlackBeta
  • Microsoft TeamsOn-Prem onlyBeta

Tickets

  • JiraSaaS onlyBeta
  • ServiceNowSaaS onlyBeta

Sign-in

  • OpenID Connect sign-inAvailable
  • SAML sign-inComing
The handoff

The team approves the fix

Tiphys reads freely to find what broke. Every change it proposes waits for approval first, and is logged.

  1. Connect

    Use Tiphys as a SaaS, or run it On-Prem. It starts read-only. Model use is included; your own model is an Enterprise option.

  2. Ask

    In plain language. Tiphys reads what it needs to find the cause.

  3. Approve the fix

    Anything that would change a service or its configuration waits for your yes.

See Tiphys on your own work.

A person on the team reads every request and replies by email.