downtime ── direct cost latency ── your users notice complexity ── operational risk
We build infrastructure tooling for environments where those three lines aren't philosophy - they're the spec. Not DevOps blogging. Not abstractions that demo well and break at 2x load. Every tool we ship is designed to behave correctly at 3am, during the incident, when no one has time to read docs.
⚡ SpindleXModern SSH and SFTP for Python automation A typed Python SSHv2 and SFTP library for async automation, secure file transfer, port forwarding, and controlled SSH/SFTP server workflows. Modern algorithms, strict host key verification, and clear production-facing docs are part of the design. from spindlex import SSHClient
with SSHClient() as client:
client.get_host_keys().load()
client.connect("prod-01", username="ops")
stdin, stdout, stderr = client.exec_command("systemctl status api")
print(stdout.read().decode().strip()) |
|
These are not guidelines. They are load-bearing rules on every decision.
| ❌ Never | ✅ Always |
|---|---|
| Unnecessary abstractions | Explicit over implicit |
| Legacy compatibility layers | Everything is measurable |
| Hidden behavior or implicit magic | Every component is replaceable |
| Complexity that doesn't earn its place | Security defaults that never need overriding |
| 🔨 Now | 🔭 Next |
|---|---|
| SpindleX v1 stable release | Infrastructure runtime layer |
| Expanded key/cipher support | Automation framework suite |
| Performance benchmarking suite | Protocol-level tooling library |
| Public contribution guidelines | High-performance system primitives |
We ship with intent. Before contributing:
| # | Rule |
|---|---|
| 1 | Read the constraints - no exceptions, no "just this once" |
| 2 | Open an issue first - discuss before building anything non-trivial |
| 3 | Performance is a hard gate - regressions block merge, always |
| 4 | Security improvements - always welcome, always reviewed carefully |
