Laritor is a performance monitoring and observability platform for Laravel applications. It captures every request, query, log, task, and alert in your app, helping you detect slowdowns, bugs, and inefficiencies before they impact users.

An event in Laritor is defined as any entry which can be monitored. Examples are requests, commands, scheduled tasks, health checks, task scheduler, queued jobs, queries, cache hits, outbound requests, logs, exceptions, mails, notifications, etc.

Laritor is billed based on usage. A flat fee of $10 for the first 10M events per month, and overage charges of $0.25 per 100K events.

No, Laritor bills you for the total number of events ingested. So there is no limit on how many events you can ingest. Each event is billed in 2KB increments. For example, If a database query is consuming 3KB of data, It is billed as 2 events.

Laritor is built specifically for Laravel. It provides deep insights into Laravel’s internals (queues, jobs, commands, health checks, etc.), lightweight ingestion, AI-powered performance insights, and developer-friendly dashboards. All with zero instrumentation overhead.

Laritor supports all hosting providers and deployment infrastructures. You can run Laritor on shared hosting, Dedicated cloud server, VPS, On-Prem server, etc. There are also no restrictions on deployment environments you can use. You can run laritor on Laravel Octane, Laravel Vapor, AWS Lambda or any other serverless infrastructure.

Laritor supports Laravel 8 and above. We also support Laravel Octane (FrankenPHP, RoadRunner, Swoole) and Laravel Vapor. Compatibility is updated regularly.

Laritor gives you the option to select a geographical region to store your data at the time of signing up. Currently we support US East(New York), US West(San Fransciso), Netherlands(Amsterdam), United Kingdom(London) and India(Bangalore) regions.

No, Currently laritor only offers our cloud hosted SaaS solution and it is not possible to self host laritor.

Yes. Laritor is designed for high-performance production workloads. Our client SDK supports full customization to control what data is ingested and when.

By default, Laritor's client package will redact sensitive information like passwords, credit cards, bank accounts, etc before sending the payload to our servers. Laritor also allows options to anonymize PII information like name, email and phone numbers.

Laritor retains all data ingested for a maximum of 30 days.

Yes. Laritor is an independent tool and does not conflict with other performance monitoring tools.

No. Laritor does not rely on a separate agent to process events. Laritor automatically sends events data in the background as soon as a request is handled, command is executed or queued job is processed.

Yes. You can set spending caps on laritor and once your cap is reached, Laritor will stop ingesting events for the rest of the billing cycle.

Yes, You can setup billing alerts and Laritor will notify you as soon as your spend exceeds the alert threshold.

Laritor's client package is designed to use minimal performance footprint. It is estimated the performance impact of running laritor's client package is less than 10ms. See our commitment to reduce performance footprint.

No. Laritor is specially designed to work with laravel applications only.

Laritor supports native integrations with Slack, Discord, Microsoft Teams, Email and any custom webhook. You can configure custom triggers like slow queries, failed health checks, or 5xx errors.

Laritor collects performance metrics, logs, requests, database queries, scheduled task traces, command execution, and exceptions. You can fully control what’s ingested using the laritor's client package.

Yes. You can redact, anonymize, or filter the data you share with laritor.

Yes. Laritor allows you to define and monitor your custom health checks.

Yes. You can request full deletion of logs, traces, and backups at any time by emailing [email protected].

No. We do not use customer data to train AI models.