// the take
ZSS is the C-based system services server that lets Zowe (IBM's open-source z/OS tooling layer) talk to low-level mainframe APIs like SAF security, datasets, and USS files through a cross-memory server. It's for teams building or extending Zowe components that need privileged access to z/OS resources, not for general app developers.
The cross-memory server split (ZIS) is a legitimate security design, isolating privileged operations from the HTTP-facing process rather than running everything at one trust level. It supports both RACF and Top Secret (tssparsing.c, secmgmttss.c) instead of assuming one SAF product. The plugin architecture for ZIS (plugins/zis/sample, echo, magic-number) gives a real extension point with working examples, not just a stub API.
This only runs on z/OS with a cross-memory server requiring specific RACF/APF authorizations and program-controlled bits set correctly, so there's zero portability and a real ops learning curve (the README's own troubleshooting section flags a 401 impersonator error from a missing program-controlled bit). 16 stars against 46 forks is a strange ratio for a project this size, suggesting most activity is internal Zowe contributor forks rather than outside adoption. It depends on a separate zowe-common-c submodule with its own PR coordination dance, which is extra friction for any outside contributor. Given the audience is mainframe shops already running Zowe, this isn't something you'd adopt standalone.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →