redevops.app
Your agent, your key

Sidekick is a shell. The model is yours.

The shell you talk to. It finds what needs attention across your apps and proposes actions; it does not own the model, you do. The six agents below work the same way: they run on the model endpoint you point them at.

The agents

Revenue

CRM, Outreach

Intelligence

BI, Market intel

Content

Content

Finance

Billing, Books

Customer Success

Support, Guide, Lifecycle

Security & Compliance

Compliance, Privacy, Edge sentinel, KYC screening

How keys and models are handled

  • You choose the model: a local model, or a hosted provider you already pay for. We add no fee on those calls.
  • By default the agents call only endpoints inside your own network boundary. Using a hosted provider is an explicit decision: you allow that host, and the change is shown to you before it applies.
  • Keys are named, not pasted: you give the name of an environment variable, or a reference into Vault, KeePassXC or your OS keyring. A key is never a command-line flag.
  • Change the provider or key later by telling Sidekick. The change is previewed, approved, tested with one small call, and rolled back automatically if the test fails. Nothing is reinstalled or restarted.

Works with: Claude, OpenAI, Kimi, Gemini, Grok, Ollama, Local models (CPU, Metal, CUDA), OpenRouter and other LiteLLM models.

Honest limits

  • Quality depends on your model. Small local models can draft; keep approvals on for anything that sends or pays.
  • Automatic fallback between several keys is not built.
  • The Sidekick command-line command for this is in review; the kernel capability behind it ships in v0.3.43.

What a key change looks like

  1. You tell Sidekick: "use my new key" or "switch to the local model".nothing changes yet
  2. Sidekick shows a preview: which provider, which model, where the key is kept, and whether traffic would leave your network.preview with an exact payload
  3. You approve that exact change. The approval works once and only for that payload.single-use approval
  4. The change is applied, tested with one small call, and rolled back automatically if the test fails.test result and receipt