The pain it kills

Self-hosting means hand-minting API keys, copy-pasting them into five config files, wiring every service to every other, and never remembering which key goes where when it's time to rotate. skwire makes all of that vanish. It owns the wire graph — so it mints every secret up front, injects each into everyone who needs it, and rotates a key across the whole vertical in one call.

The whole flow

scan your env → build the plan → "I'll set up X, wire Y… want me to just do it?" → heck yeah → MINT every secret → INJECT into provider + every consumer → wired → 🔑 "auto-rotate that key every 90 days — want me to schedule it?"

What you get

🔐 Mint-then-inject

Every secret generated up front, injected pre-boot, cross-service config pushed via each app's API. Zero manual wiring.

🔁 Rotate the vertical

One call re-mints a key and re-injects it everywhere it's used. Schedule rotations from each secret's policy.

💬 Slick chat window

skwire serve — a branded, white-label chat UI. No terminal. Greets you, scans, shows the plan, you click “Heck yeah”.

🛍️ App-store catalog

Best-of-breed open source — servers and desktop apps. The AI lists + recommends. Install, use, then fork your own.

🧩 Embeddable + forkable

Pure-stdlib core, zero deps, cross-platform. import skwire in any project; ship your own pack. Roll your own.

🤝 Trust both ways

A signed plan-hash both you and the machine trust — the AI can't deviate from what you approved.

Try it

pip install skwire        # zero deps, cross-platform
skwire scan               # "mind if I take a look at your env?"
skwire catalog            # browse best-of-breed open source
skwire serve              # the slick chat window — no terminal

Open at every edge

The engine is open. The catalog is a separate repo — adding an app is a PR to a JSON file. Publish your own pack (pip + an entry point), host your own catalog, or take the whole thing and roll your own. No lock-in, ever.