Pricing: Choose the right plan for you

There's no limit on the number of API requests processed for metrics and analytics, since these rely on aggregated data, but request logs, application logs and traces are subject to monthly quotas.

If you exceed the API consumer limit for your plan, you'll enter a one-time grace period. During this time, you can either upgrade to a higher plan or reduce usage to stay within limits. If the grace period ends and you're still over the limit, Apitally will stop ingesting data from your apps.

If you exceed your monthly quota for request logs, Apitally will stop ingesting new requests until the quota resets at the start of the next month. This won't affect your API metrics. The same applies to application logs and traces.

On the Starter and Premium plans, you can enable usage-based billing at any time under Settings > Billing in the dashboard. It's off by default. If enabled, ingestion continues beyond your monthly quotas, and you're charged for the extra usage at the overage rates shown in the pricing section above.

For API metrics, the Apitally SDKs record the method, path, status code, response time and payload sizes of each request, and combine them into counts and histograms within your application before sending them to Apitally. Aggregated metrics are retained for 13 months.

Request logs capture the details of individual requests, such as the URL, client IP address, user agent, response headers and response time, along with related application logs and traces. Request headers and request and response bodies are only captured if you enable them. Request logs, application logs and traces are retained for 15 days, with longer retention available on request.

The SDKs mask sensitive query parameters, headers and body fields by default, and you can add your own masking rules or exclude requests from logging. Masking and filtering happen within your application, before any data is sent to Apitally. Read more about data collection, privacy controls and retention in our docs.

Apitally currently supports the following web frameworks:

• AdonisJS (Node.js)
• ASP.NET Core (C#)
• BlackSheep (Python)
• Chi (Go)
• Django Ninja (Python)
• Django REST Framework (Python)
• Echo (Go)
• Elysia (Bun)
• Express (Node.js)
• FastAPI (Python)
• Fastify (Node.js)
• Fiber (Go)
• Flask (Python)
• Gin (Go)
• H3 (Node.js / Deno / Bun)
• Hapi (Node.js)
• Hono (Node.js / Bun)
• Koa (Node.js)
• Litestar (Python)
• NestJS (Node.js)
• Starlette (Python)

Please let us know if you're interested in using Apitally with a framework that is currently not supported.

Apitally supports Cloudflare Workers via a Logpush integration and our Serverless SDKs. These currently support Hono and FastAPI.

You can find more details in our setup guide for Cloudflare Workers.

Support for other serverless platforms may be added in the future based on user demand.

Apitally offers a CLI and agent skill that give AI agents like Claude Code, Cursor, and Codex full access to your API metrics and request logs. We chose this approach over MCP because it's more token-efficient and reliable, while giving agents richer investigation capabilities.

Read more about it in our blog post.