Learning paths

A learning path is a reading order, not new material. Each one walks you through pages that already exist, in the sequence that avoids doubling back, and adds the part the sidebar cannot tell you: why this page before that one, and what is going to surprise you along the way.

Every path carries a checklist. Ticks are saved in your browser, so you can stop after two pages and pick the path up next week where you left it.

Answer three questions

If you are not sure which path fits, these build one from your answers. Nothing is sent anywhere and the same answers always give the same result.

1 What do you want to do first?

Connect a cloud account See what is already running at a provider, then manage it. Manage servers I already run Put an agent on Linux hosts, wherever they live. Show that what we run is secure Audit trail, access control and compliance evidence. Automate it from my own tools The API, tokens, and AI clients over MCP.

2 What are you running today?

Public cloud Our own servers Kubernetes A mix of all of it

3 Who are you doing this for?

My own team Customers we manage

Answer the first question and a reading order appears here. Or skip it and browse all six learning paths.

All paths

Get started with Sencai → Account, two-factor, the object model, your first organization, and who gets which role. Learning path ·7 pages ·New accounts Connect your cloud and take stock → Add a provider account read-only, scan what is already there, triage the inventory, then provision something new. Learning path ·8 pages ·Cloud operators Run a Linux fleet → Enroll the agent, read what it collects, search packages across every host, and check hardening scores. Learning path ·8 pages ·Fleet operators The day-2 operations loop → Monitoring, incidents, root-cause candidates, runbooks and change control, in the order they depend on each other. Learning path ·8 pages ·On-call teams Security and compliance evidence → The audit log, access restrictions, single sign-on, and the inventory that every compliance view reads from. Learning path ·9 pages ·Security and compliance Build against the platform → The API surface and its conventions, scoped tokens, versioning, MCP for AI clients, and the developer tooling. Learning path ·8 pages ·Developers

If a path is not what you want

• Tutorials are shorter and end with something concrete - a validated credential, an enrolled host, a successful API call.
• Use cases start from a situation rather than from a role.
• Finding your way around maps the application’s own navigation onto the pages here, if you already know the screen you are looking at.