What local-first means in Ripple
Ripple stores everything in ripple.db under your OS app-data directory. Collections, request history, environments, cookies, OpenAPI design documents, chat sessions, and UI state all persist locally. There is no cloud sync server, no login wall, and no telemetry SDK phoning home.
The app is a Rust-based API workbench — sub-2-second cold start on Apple Silicon, ~45 MB idle memory with AI off, and less than 10 ms request overhead through native Rust HTTP. The shell stays responsive because HTTP, SQL, gRPC, load tests, and mock servers run through native code, not a heavy Electron runtime.
The app works fully offline. The on-device LLM (Son of Anton), SQL drivers, diff engine, and mock server all run in-process — take Ripple on a plane and keep working.
What you get locally
- HTTP, GraphQL, SOAP, and every common body type with {{variable}} interpolation
- WebSocket, SSE, and Socket.IO with per-tab message logs
- gRPC unary + server/client/bidi streaming with reflection
- SQL runner for PostgreSQL, MySQL, and SQLite
- OpenAPI Design Studio with linting, versioning, and local mock servers
- Load Test Lab with configurable concurrency and live metrics
- Developer tools: JWT decoder, diff, encode/decode, network diagnostics
- Optional Son of Anton — GGUF models running via llama.cpp, no cloud round-trips
- rip CLI — headless collection runs with JUnit, JSON, HTML, and GitHub Actions reporters
Team work without a sync SaaS
Ripple Team Workspaces store collections as JSON on disk in a shared folder. External change polling (~3s) auto-reloads when a teammate edits a file. Optional Git init, pull, commit, and push on the workspace folder — conflict backups land in .ripple/conflicts/. No Ripple-managed cloud backend required.
Import what you already have
- Postman v2.1 collections
- Insomnia v4 export bundles
- OpenAPI 2.0 / 3.x and Swagger specs
- WSDL for SOAP collections
- HAR files into request history
- cURL paste to auto-fill any request
Who this is for
- Developers in regulated or air-gapped environments
- Solo builders who refuse vendor cloud lock-in
- Teams that already trust Git over a proprietary workspace
- Anyone tired of API tools that require an account to save a request