Plugins
Look inside the services you run
Signed, read-only packs that let Secronyx answer questions about the databases, brokers and web servers on your hosts.
Available plugins
Pick the services you run
Each plugin is a signed pack for one service. Install it on the hosts that run that service, give it a least-privilege login, and its read-only queries appear next to the built-in ones.
No plugin matches these filters.
Databases
9 pluginsRelational databases.
Messaging & streaming
5 pluginsMessage brokers and queues.
Web, proxy & app servers
9 pluginsWeb servers and reverse proxies.
Platform & orchestration
6 pluginsService discovery, secrets, schedulers and Kubernetes nodes.
Observability & CI
2 pluginsMetrics and alerting.
How plugins work
A declaration, not code
A plugin names a service, how to log in to it, and a fixed set of read-only queries or requests. It contains no code that runs on the host.
One compiled, signed pack
The pack is a single file. The agent checks that it and every folder above it are owned by root, SYSTEM or Administrators, then verifies the signature against a signer you trust, before it parses anything.
Read-only engines
Queries and requests are fixed in the pack. Each engine has a deny-by-default allowlist that lives in the agent, and it is checked when the pack is built, every time it loads, and before every SQL call.
Least-privilege logins
Each plugin ships the grant for a read-only login. For SQL databases the agent asks the server how powerful the login is, and refuses to register the tools when it has more rights than the plugin needs.
Install, verify, load
Four commands on the host
Run them as root (Linux, macOS) or Administrator (Windows) on the host that runs the service.
Trust the signer once per host
secronyx plugin trust add <key-id>.jsonInstall the pack
It verifies the pack and tries the logins that need no secret. A login with too many rights is refused, and the command prints the grant script for a least-privilege one.
secronyx plugin install ./<plugin>-<version>.scxpCreate the least-privilege login
The admin password is read once from stdin and is not stored. Only the new login is kept.
secronyx plugin setup <plugin> --apply --admin-user <admin> < admin-passwordCheck it is ready
secronyx plugin status
Recordings of these steps from the test lab will appear here and on each plugin's page.
Security model, in short
Layers, and what they do not cover
What limits a plugin
- The login: read-only grants, checked by the agent for SQL databases.
- The engine: fixed queries, an allowlist in the agent, read-only transactions that are always rolled back.
- The result: only the columns a tool declares leave the agent, and every call is recorded in the agent's audit log.
What remains
- An administrator can accept a more powerful login on purpose. That choice is audited and shown in status, not prevented.
- Root or Administrator on a host can replace the agent or its trusted signer keys.
- A pack can read anything its login can see, so the least-privilege login matters.
Write your own plugin
Your services, your signing key
Describe your own service in a plugin.yaml, check it, and sign it with a key you create. Hosts load it once they trust your key.