Docs — Concepts
Pricing model & retention
Flat pricing, caps not meters
Rudow bills a flat monthly amount per plan. Usage limits are caps, not overage meters: requests past the monthly cap are rejected with a clear message until your next billing cycle or an upgrade. There are no surprise overage charges, ever.
Every plan includes every feature — full-text and natural-language log search, the metrics dashboard, AI chat, the MCP server and team seats. Tiers differ only by usage limits and seats, never by feature gating.
Plan table
| Plan | Price | Projects | Users | Log entries / mo | MCP requests / mo | AI chat / mo |
|---|---|---|---|---|---|---|
| Hobby | Free | 1 | 1 | 200,000 log entries / mo | 700 MCP requests / mo | 70 AI chat messages / mo |
| Dev | $9.99 | 2 | 3 | 1,000,000 log entries / mo | 2,000 MCP requests / mo | 200 AI chat messages / mo |
| Pro | $29.99 | 5 | 10 | 5,000,000 log entries / mo | 10,000 MCP requests / mo | 1,000 AI chat messages / mo |
| Team | $79.99 | 20 | 50 | 20,000,000 log entries / mo | 30,000 MCP requests / mo | 3,000 AI chat messages / mo |
Log retention
Log entries and uploaded log files are retained for 40 days on every plan, enforced by a database TTL index. Entries past the retention window are purged automatically — older data is not recoverable, so export anything you need to keep.
Read-only by design
Rudow ingests and queries logs. It never mutates, rewrites or acts on your systems, configs or deployments. The MCP server exposes read-only tools with the same guarantee — an agent connected to Rudow can investigate, never change anything.
Install paths
- Node.js —
npm install @rudow/node-logger - Python —
pip install rudow - Anything else — the plain HTTP ingest API:
POST https://api.rudow.ai/v1/ingest
Changing plans
Upgrade or downgrade whenever you like; the change applies to your current billing period. Downgrading to Hobby is handled the same way through checkout or the Stripe customer portal.