What is Laritor?
Laritor is a performance monitoring and observability platform for Laravel applications. It captures requests, logs, queries, tasks, and alerts to help developers detect issues early.
Frequently Asked Questions
We compiled every detail on pricing, data retention, privacy, and performance impact so your team can evaluate Laritor with confidence.
Laritor is a performance monitoring and observability platform for Laravel applications. It captures requests, logs, queries, tasks, and alerts to help developers detect issues early.
Laritor is a Laravel-first observability and performance monitoring platform that combines APM-style tracing with logs, metrics, alerts, and AI insights.
Laritor instruments Laravel workflows like HTTP requests, Artisan commands, queues, scheduled tasks, health checks, and database queries without manual instrumentation.
Yes. Laritor tracks queued jobs and scheduled tasks as first-class events so you can monitor performance and failures.
Yes. Laritor tracks feature flag usage so you can understand how flags affect performance and errors.
Yes. Laritor captures server metrics such as CPU, memory, and disk usage to correlate infrastructure health with application performance.
Yes. You can include custom user attributes and contextual data (for example team, role, or subscription status) to enrich traces and logs.
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. The Free plan includes 300K events per month. Pro starts at $10 and includes 20M events per month, with $0.15 per extra 100K events. For 300M+ events, the Custom plan offers a flat monthly rate.
Laritor retains data for 30 days on Free and Pro. Custom plans can include longer retention.
Yes. Laritor uses AI to surface bottlenecks and optimization recommendations to help teams resolve performance issues faster.
Laritor integrates with OpenAI, Gemini, Anthropic, DeepSeek, Ollama, and xAI for AI-driven insights.
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.
Events are billed in 2KB increments. If an event payload is 3KB, it counts 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 almost all deployment environments, including traditional servers, VPS, and serverless platforms.
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) and Netherlands (Amsterdam) regions.
No, currently Laritor only offers our cloud hosted SaaS solution and it is not possible to self host Laritor.
Yes. You can monitor multiple Laravel applications under a single Laritor account.
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 can run alongside other monitoring tools without conflicts.
Yes. Laritor supports data export.
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.
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.
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 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.
Yes, you can setup billing alerts and Laritor will notify you as soon as your spend exceeds the alert threshold.
Still need help?
Send your question to [email protected] or book a call and we’ll walk through your use case together.