server control, rethought
The server knows.
Now you do.
A terminal operator interface built around how diagnosis actually works — not how CLI tools were designed in 1980.
Survey
Focus
Act
survey
Select a module.
The full landscape is already there.
focus
Select a subject.
Live state, read at this moment.
act
Act on live state.
Only what's possible now.
$ curl -fsSL https://suctl.com/install | sh
nothing to configure · later, suctl upgrade updates it in place
see why
single binary
no runtime · linux · macos · windows · arm
survey · focus · act
the operator model
language-agnostic modules
one model · any implementation
The same task — then and now.
renewing an ssl cert on client-b.com
1980s CLI — flags & text LISTING
SURVEYsuctl — survey · focus · act
vs
The three cognitive moments
01 ——
Survey
The full landscape of a module's domain, read live from the authoritative source the moment you enter. Real state, not cached state.
What exists? What is its state?
02 ——
Focus
Select a subject. Everything this module knows about that one thing, read live at the moment of selection. Not last known. Right now.
What is this, right now?
03 ——
Act
Actions computed from live state. Only what's possible given what this subject actually is right now. Absent means impossible. Not greyed out. Absent.
What can I do, given what this actually is?
Documentation
get started
Install, open the REPL, read your server's live state — then write your first module in any language.
read →
concepts
The philosophy and the contribution standard. Why suctl is built the way it is.
read →
reference
Normative specifications for module authors — wire protocol, manifest and surface schemas. You don't need these to use suctl.
read →
newsletter
Know what ships.
Release notes, new modules, use cases. Nothing else.
Low volume. No marketing.
✓ subscribed.
✗ didn't go through — try again in a minute.