Skip to content
Sencai.docs

Use cases

These start from a situation rather than from a screen or a role. Each one sets up the problem, walks the pages that answer it in order, and says plainly what Sencai does not do about it - which is usually the part that decides whether the approach fits you.

We inherited a cloud account and need to know what is in itRead-only credentials, one discovery scan, and an inventory you can triage - without changing anything at the provider.Operate our Hetzner footprint from one placeNetworks, firewalls, DNS and instances managed against the real provider account rather than recorded in a table.Live network changes are Hetzner Cloud only; firewalls also cover AWS, and DNS covers five providers.Keep a Linux fleet inventoried and measuredOne agent per host, package search across the whole estate, patch-scan results and a per-host hardening score.Make monthly cloud spend visible and attributedWhere the cost records come from, how to split them by tag, and which right-sizing candidates are worth acting on.Spend caps record a limit and send alerts; they do not stop provider spend on their own.Hand an auditor read-only evidenceThe hash-chained audit log, the inventory behind it, and the filtered NIS2 timeline you can export.Onboard the whole company through your identity providerSingle sign-on, SCIM provisioning, the synced directory it produces, and the events worth watching.Single sign-on and SCIM require a paid organization - any paid plan.
Section titled “Related”
  • Learning paths cover an area end to end, organized by who you are rather than by what happened.
  • Tutorials are shorter and finish with one concrete result.
  • Troubleshooting is organized by symptom, for when something is already going wrong.