Sleev is going local

Better service reliability and user privacy. Your prompts, your code, your data.

We’re moving the optimization engine out of the cloud. The motivation behind this architecture shift is practical: your private data should not leave your machine. So we built a local gateway to handle context optimizations while keeping session state in a local database.

What changed

Sleev used to relay every LLM request through a cloud gateway; this meant your private and confidential data passed through infrastructure you don’t control.

We replaced that gateway with a local process. When you run sleev, it binds to 127.0.0.1:17321 and handles everything the cloud gateway used to do.

Sleev TUI

We’re building a TUI to manage Sleev and show you insights on your AI usage and savings.
Install it with npm i -g sleev

What’s next

The local gateway and TUI are in active development. We’re focused on making the setup frictionless and the TUI worth opening. If you want to follow along or try it out, check the quickstart.