Laritor
Yes
Laritor vs NightOwl
A NightOwl alternative
for your whole Laravel app.
Laritor tracks exceptions, detects issues, and monitors Laravel performance. Follow requests, queues, queries, and user sessions in one place. Build your own dashboards, inspect server resources, and debug with in-app AI or your coding agent through MCP.
Published by Laritor · Comparison checked · View comparison notes
Laravel native
Designed primarily for Laravel. All tools compared here support Laravel.
NightOwl
Yes
Why choose Laritor over NightOwl?
Laravel monitoring
built around your everyday work.
Both tools track Laravel exceptions, issues, and performance. Laritor manages telemetry storage and adds custom dashboards, session journeys, feature flag insights, and reports. NightOwl stores telemetry in your PostgreSQL database and provides a dashboard for a flat monthly subscription.
More visibility. More control.
- Managed ingestion and storage without a telemetry database to run.
- Unlimited custom dashboards with 85+ widgets.
- Exception tracker issue tracker, or full observability recording.
- Feature flag insights and custom health checks.
- Session journeys across recorded Laravel requests.
- Server CPU, memory, and disk metrics with optional collection.
- Queue wait investigation and optional outbound API body capture.
- Custom event views and daily or weekly PDF reports.
- Your choice of provider for in-app AI, plus exception context through MCP.
Specific team requirements.
- You want raw telemetry stored in your own PostgreSQL.
- You prefer a flat subscription and can operate the agent and database.
- You need direct SQL access, flexible history, or a licensed self-hosted dashboard.
- You want MCP tools that update issues and settings, or Agency client handoffs.
The full feature comparison
Laritor vs NightOwl.
See what you get.
Compare 36 capabilities. See where Laritor gives you more, where NightOwl has an advantage, and what both tools offer.
“Not listed” means a dedicated feature was not found in the public documentation reviewed. Custom instrumentation or an integration may offer another way to meet that need. NightOwl already has issue management, alerts, cache and log analytics, user timelines, MCP, and configurable incoming request body capture. The comparison includes its September 2026 capture updates and distinguishes dedicated views from custom context.
Where Laritor shines
Managed storage, customizable dashboards, session journeys, Pennant analytics, server resources, and scheduled PDF reports.
| Capability | Laritor | NightOwl |
|---|---|---|
| Managed telemetry storage and collection | Less infrastructure to manage Hosted ingestion and storage. Install the Laravel client without running an ingestion agent or telemetry database. | Run a telemetry agent and provide PostgreSQL. NightOwl hosts the dashboard; you operate the data pipeline and database. |
| Unlimited customizable dashboards | 85+ widgets Build unlimited dashboards with 85+ included Laravel widgets. | Application dashboards, filters, and an Agency portfolio view. An equivalent customizable widget builder is not listed. |
| Automatic Pennant performance insights | Understand feature rollouts Feature flag evaluations, activation rates, durations, and related errors. | Feature flag decisions can be attached through Laravel Context. Dedicated automatic Pennant analytics are not listed. |
| Laravel session journeys | Follow a user’s visit Follow recorded requests across a session with users and custom events. | User timelines and request context. A dedicated journey grouped by Laravel session is not listed. |
| Application server resource views | Code and server resources Optional collection of host CPU, memory, and disk metrics, with dedicated server charts. | Team and Agency include agent health and resource signals. A comparable application host CPU, memory, and disk resource view is not listed. |
| Custom dependency health checks | Check your dependencies Checks inside Laravel with result history and failure alerts. | Agent and database pipeline health plus execution thresholds. A dedicated custom dependency check resource is not listed. |
| Database schema explorer | Schema-aware debugging Browse tables, columns, indexes, and relationships beside recorded queries. | Query analytics and PostgreSQL telemetry storage statistics. An application database schema explorer is not listed. |
| Custom daily and weekly PDF reports | Share performance snapshots Choose metrics and receive scheduled PDF application snapshots by email. | Agency portfolio snapshots and dashboards. Custom scheduled PDF performance reports are not listed. |
| Bot and suspicious request views | Understand automated traffic Dedicated traffic analytics with detection settings and recording filters. | Request analytics and route ignore filters. Dedicated bot and suspicious traffic views are not listed. |
| Business event resources and dashboards | See your business workflows Named custom events in timelines, a dedicated resource, and dashboards. | Laravel Context and logs can describe business activity. A dedicated named business event resource is not listed. |
| Ready-to-use problem recording modes | Choose what you record Exception tracker issue tracker, or full observability filters retain related recorded events. | Trace sampling, exception sampling, ignore rules, and custom context. Equivalent named problem recording presets are not listed. |
| In-app AI and provider choice | Debug inside Laritor Recommendations inside Laritor with configurable AI provider and model settings. | MCP connects external coding agents. An equivalent in-app recommendation and provider selection workflow is not listed. |
| Outbound API request and response bodies | Find why API calls fail Optional outgoing headers, payloads, status codes, and response content. | Outgoing URL, method, status, duration, sizes, and request headers. The reviewed record writer does not persist outgoing payload or response bodies. |
| Queue wait and throughput views | Find queue bottlenecks Compare dispatch delay, worker wait, execution duration, and throughput. | Job attempts, failures, execution duration, and throughput. An equivalent dedicated queue wait time view is not listed. |
Where NightOwl shines
Bring your own PostgreSQL database, direct SQL access, flexible retention, a self-hosted dashboard, and MCP automation.
| Capability | Laritor | NightOwl |
|---|---|---|
| Bring your own database | Monitoring data is stored in Laritor’s managed service. | Connect your own PostgreSQL database to store monitoring data. NightOwl’s hosted dashboard reads from it. |
| Direct SQL and configurable history | 30-day retention on the published paid plan. | Query your own telemetry with SQL and set database retention. Hobby shows 14 days; Team and Agency have no dashboard lookback cap. |
| Self-hosted dashboard option | Hosted Laritor service. | Commercial self-hosted dashboard and API license for $5,000 upfront. Optional updates after year one cost $500/year; infrastructure is separate. |
| MCP issue and platform automation | Hosted read-only exception investigation context for coding agents. | Team and Agency MCP can investigate telemetry and change issues, alert channels, settings, and platform resources with scoped access. |
| Agency client handoff workflow | Unlimited apps and users with shared monitoring views. | Agency includes app-scoped access, bulk invites, onboarding templates, a portfolio overview, and client ownership transfers. |
Where there’s a tie
Both are Laravel native and offer exceptions, issue workflows, performance metrics, execution timelines, incoming body capture, alerts, and MCP.
| Capability | Laritor | NightOwl |
|---|---|---|
| Laravel exception tracking | Grouped exceptions, full stack traces, source context, and occurrence details. | Grouped exceptions with stack traces, occurrence history, and linked execution context. |
| Issue management and performance thresholds | A dedicated Issues workspace for detected exceptions, failed executions, and slow activity. | Issue status, priority, assignments, comments, bulk actions, and configurable execution thresholds. |
| Application performance monitoring | Request percentiles, route timings, failure rates, queries, and job performance. | Request and route analytics, P95 latency, timing breakdowns, queries, and background execution metrics. |
| Related execution timelines | Queries, logs, API calls, and other recorded events inside a retained execution. | Trace-correlated requests, queries, jobs, logs, cache, and outgoing HTTP activity. |
| SQL queries and bindings | SQL, bindings, duration, and related execution events. | SQL investigation, bindings, query patterns, timings, and trace context. |
| Job execution and failures | Dedicated job monitoring with attempts, failures, timing, and related events. | Queue and job analytics with attempts, retries, failures, timing, and trace context. |
| Scheduled task monitoring | Scheduled executions, failures, duration, delays, and related events. | Scheduled execution history, duration, failures, thresholds, and related trace activity. |
| Artisan command monitoring | Command executions, status, duration, exceptions, and recorded activity. | Command executions, exit codes, timing breakdowns, exception previews, and related events. |
| Laravel cache monitoring | Cache events, hit/miss analytics, timing, and execution context. | Cache operations, hit/miss analytics, key patterns, timing, and trace context. |
| Application log inspection | Logs in execution timelines and a dedicated searchable resource. | Recorded logs and context, with opt-in context search and severity filtering. |
| Mail and notification activity | Dedicated resources and events linked to retained executions. | Mail and notification views, durations, issues, and thresholds. |
| Request headers, payloads, and responses | Optional capture of request headers, payloads, and response content. | Request headers and configurable payload/response body capture, with status and route filters added in September 2026. |
| Users and custom execution context | Authenticated user context, custom attributes, and recorded user activity. | User timelines and structured Laravel Context metadata inside request details. |
| Exception and performance alerts | Exception and issue alerts through configured integrations. | Slack, Discord, email through your SMTP, and signed webhooks for issues and thresholds. |
| Sensitive data controls | Client-side collection settings and redaction before ingestion. | Nightwatch header/payload redaction and NightOwl JSON response field masking. Review custom context and raw text bodies separately. |
| Sampling and custom filtering | Client-side event controls, sampling, and custom recording filters. | Trace and exception sampling, ignore/pause/resume controls, and route ignore rules. |
| MCP investigation for coding agents | Hosted exception details and recorded execution context through MCP. | Team and Agency MCP tools for exceptions, requests, queries, jobs, logs, users, and other telemetry. |
Major difference
Laritor handles the ingestion backend. NightOwl leaves it to you.
Laritor takes care of ingestion, storage, retention, and scaling. With NightOwl, your team runs the agent and provides PostgreSQL, adding database costs, ongoing maintenance, and server resource usage to your monitoring setup.
-
Keep more server resources for your app
NightOwl’s agent uses CPU and memory, and its SQLite WAL buffer consumes disk space and IOPS. When hosted on your production server, that work competes with your app. Laritor requires no separate ingestion agent or local telemetry database.
-
Skip extra database costs and maintenance
Laritor’s plan includes managed monitoring storage. With NightOwl, budget for PostgreSQL hosting, compute, and storage in addition to its subscription. Your team must also monitor database server health, arrange backups and maintenance, and scale capacity as telemetry grows.
-
Skip the ongoing monitoring upkeep
Laritor applies retention and operates the backend. NightOwl requires agent health checks, process supervision, graceful restarts, and scheduled nightowl:prune cleanup. Ingestion outages or a full buffer can cause new events to be missed.
Why choose Laritor over NightOwl?
See more of your Laravel app.
Fix problems with better context.
Use managed monitoring storage, investigate failures with more context, and build the views your Laravel team needs.
One allowance for the events you record
Compare your usage All Laritor features. $20/month.
20M billable events, unlimited apps and users, and 30-day retention. Choose exceptions, detected issues, or all activity without a separate error or log quota.
NightOwl’s hosted plans start at $5/month, with your own database and agent infrastructure. The calculator adds an automatically sized Supabase database to the NightOwl subscription for a clearer cost comparison.
Cost calculator
Compare your monthly monitoring costs.
Enter your recorded workload once. We automatically estimate a Supabase database for NightOwl and add its compute and storage costs to the subscription.
Laritor / month$20.00USD · Unlimited apps and users · 30-day retention
20,000,000 billable events
NightOwl + Supabase / month$40.00Team · USD · Monthly billing
$15.00 NightOwl + $25.00 Supabase
Estimated Supabase database
Micro · Shared CPU · 1 GB RAM
8 GB provisioned disk · 30-day retention
- Supabase Pro
- $25.00
- Compute
- $10.00
- Compute credit
- −$10.00
- Additional disk
- $0.00
- Database total
- $25.00
Team: up to 3 apps · 5 members per team · MCP · Unlimited dashboard lookback.
Monthly USD estimates before tax. Includes the selected NightOwl plan and one Supabase Pro telemetry database, with its $10 compute credit and 8 GB disk allowance. Agent hosting, maintenance, egress, optional backups, and additional disk I/O are excluded. Laritor includes 20M billable events for $20, then $0.20 per started 100K. Above $500/month, Laritor shows “Ask for a quote.”
How we estimate database size and cost
We assume a 30-day month and 30 days of retained events. Storage uses NightOwl’s published rough compressed baseline of 500 MB per 8.6M rows, applied to the shared event count, plus 25% disk headroom. Disk is rounded up to whole GB with an 8 GB minimum. Larger payloads, indexes, rollups, and PostgreSQL logs can need more space.
Compute follows NightOwl’s request-volume guidance, treating jobs and commands as request-equivalent runs: shared compute up to 50K runs/day, at least 4 dedicated vCPUs above 50K, and at least 8 dedicated vCPUs above 500K. We then select the smallest Supabase instance that meets that floor and its recommended database size. Above 5M runs/day or the largest listed instance’s size, we show “Custom sizing needed.”
This is a planning estimate, not a measured capacity guarantee. It assumes a separate Supabase Pro organization with one telemetry project and an unused $10 compute credit. It uses published monthly compute estimates and general purpose disk at $0.125 per GB above 8 GB. Actual hourly billing, traffic peaks, captured data, dashboard queries, and existing Supabase resources can change the cost.
NightOwl compute guidance ↗ · NightOwl storage baseline ↗ · Supabase instance sizes ↗ · Supabase pricing ↗
Monitoring without a telemetry database
Spend more time improving your app and less time operating its monitoring pipeline.
Managed ingestion and storage
Start monitoring without managing PostgreSQL.
Install the Laritor Composer client, configure your ingest key, and choose the activity you want to record. Laritor manages the ingestion service and stored monitoring data.
NightOwl gives you ownership of raw telemetry in your own PostgreSQL. You also run its agent and handle database capacity, retention, backups, and pipeline operations. Choose Laritor when you want those services managed for you.
Application server resources
See whether the bottleneck is code or server resources.
Compare slow executions with host CPU, memory, and disk metrics collected through an optional Laravel command. Inspect your application’s server resources alongside its performance.
NightOwl’s agent health helps diagnose ingest rates, buffer depth, drain delays, and resource signals. Laritor adds a dedicated application server view for capacity investigation.
Custom health checks
Check the services your app depends on.
Run custom checks from Laravel and review results, history, and failure alerts. Monitor the dependencies that need to be available for your app to work.
NightOwl monitors its telemetry pipeline and detects performance issues. A comparable dedicated resource for your own dependency health checks is not listed.
More context for a fix
Inspect failing API calls, waiting jobs, and AI recommendations beside the execution.
Outbound API context
Find why your API calls are failing.
Capture outgoing payloads and response content when you need them. Inspect what your app sent and what the API returned alongside the related request or job.
NightOwl already records outgoing HTTP timings, status, sizes, and request headers. Its reviewed outbound storage mapping does not persist request or response bodies. Its newer incoming request body capture is a separate feature.
Queue performance
Monitor queue performance and throughput.
Compare dispatch delay, worker wait, execution duration, and throughput. Find whether the job itself is slow or whether work is waiting for a worker.
NightOwl already monitors jobs, retries, failures, and throughput. A comparable dedicated queue wait time view is not listed in the reviewed product and job storage documentation.
In-app AI recommendations
Get help where you are investigating the exception.
Use in-app recommendations and choose your AI provider and model. Or give your coding agent the exception and recorded execution context through Laritor MCP.
NightOwl supports external agents through MCP on Team and Agency, including issue and settings updates. Laritor’s in-app recommendations offer another debugging workflow without leaving the monitoring interface.
Debug with your AI agent
Give your agent the context
behind an exception.
Laritor MCP lets your agent retrieve exception details and the recorded execution timeline. It can inspect those events alongside your code to investigate the cause and work on a fix. In-app AI recommendations are available too.
Both tools support hosted MCP. Laritor adds in-app recommendations and provider choice; NightOwl Team and Agency also expose tools that update issues and settings. Choose your in-app AI provider ↗
Read the Laritor MCP guide
Views built around your Laravel app
Understand user visits, feature rollouts, and business activity across recorded executions.
Customizable dashboards
Build dashboards tailored to your team.
Choose from 85+ widgets and arrange unlimited dashboards for performance, exceptions, queues, users, and server resources.
NightOwl provides application analytics and an Agency portfolio view. An equivalent builder for custom widget dashboards is not listed.
Laravel session journeys
Follow the requests behind a customer’s problem.
Inspect recorded requests from the same session. Add custom events for checkout, subscriptions, and other milestones to understand what happened during a visit.
NightOwl has user timelines and custom request context. Laritor adds a dedicated session journey, so you can investigate activity from a particular visit.
Pennant insights
Understand how feature flags affect your application.
Record Laravel Pennant evaluations automatically and inspect activation rates, durations, and related errors.
NightOwl documents adding feature decisions through Laravel Context. Dedicated automatic Pennant collection and performance views are not listed.
Bot and suspicious traffic
See which traffic is using your server resources.
Compare automated and suspicious requests by route, status, and timing. Open a retained request and adjust detection or recording rules.
NightOwl provides route analytics and ignore rules. Dedicated bot and suspicious traffic analytics are not listed in the reviewed documentation.
Custom events
See the business steps behind an execution.
Record named business milestones and debugging information. Inspect them in timelines, a dedicated resource, and dashboards.
NightOwl can attach Laravel Context and logs to traces. Laritor adds dedicated browsing and analytics for named custom events.
Database schema explorer
Inspect the tables behind a query problem.
Browse application tables, columns, indexes, and relationships beside your recorded queries. Use that context when investigating a slow database operation.
NightOwl has query analytics and storage statistics for its telemetry tables. An application schema explorer is not listed.
Performance in context
See slow requests, errors,
and bot traffic together.
Review request volume, status codes, duration percentiles, and where time is spent. Open a retained request to inspect its queries, logs, API calls, and other recorded events. Explore request monitoring
Application updates for your team
Keep tabs on performance without opening the dashboard every day.
Custom daily and weekly reports
Receive a performance snapshot in your inbox.
Choose the metrics and schedule for a PDF application report. Receive it by email and share the snapshot with teammates.
NightOwl Agency includes portfolio snapshots and application overviews. Built-in custom daily or weekly PDF performance reports are not listed in the reviewed product documentation.
Evaluate Laritor in your app
Try it before you switch.
Use a representative app or environment to compare the details you receive, recording volume, and debugging workflow.
Install and configure the client
Create a Laritor account, install the Composer package, add your ingest endpoint and key, and run the sync command.
Complete installation stepscomposer require binarybuilds/laritor-clientChoose what to record
Start with exception tracker, issue tracker, or full observability. Register the generated filter, then review the data and privacy settings for your app.
Configure recording filtersCompare a real investigation
Inspect a known exception or slow execution, test alert delivery, and compare measured overhead and billable event usage. If you run both tools, include their combined collection work in your evaluation.
Explore exception investigationSet up your team’s workflow
Create your dashboards, choose alert channels, schedule reports, and connect AI. Keep access to your NightOwl database and dashboard while Laritor builds a new record of your application’s activity. There is no documented automatic history import.
Explore Laritor guides
Questions before switching
NightOwl alternative FAQs.
What is Laritor, and why use it as a NightOwl alternative?
Laritor tracks exceptions, detects issues, and monitors Laravel performance. It combines execution context with custom dashboards, session journeys, feature flag insights, server metrics, health checks, reports, in-app AI, and MCP. Choose it when you want dedicated Laravel views and managed monitoring storage.
What is the main difference between Laritor and NightOwl?
Both are Laravel native and offer exception tracking, performance monitoring, issue management, alerts, and MCP. Laritor manages ingestion and telemetry storage. NightOwl uses an agent and a PostgreSQL database you provide, with a hosted dashboard and flat subscription. Laritor adds custom dashboards, session journeys, automatic Pennant insights, and scheduled PDF reports.
Are both Laritor and NightOwl Laravel native?
Yes. Both are designed primarily for Laravel. NightOwl collects Laravel events through the Laravel Nightwatch SDK and its own agent. Laritor uses its Laravel Composer client with hosted ingestion. Laravel native describes their focus, rather than implying that either product is an official Laravel service.
Does NightOwl require a paid Laravel Nightwatch subscription?
No. NightOwl uses the Laravel Nightwatch instrumentation package, but standalone NightOwl does not require a Nightwatch Cloud account, paid subscription, or token. Its own agent receives the telemetry and stores it in your PostgreSQL database. NightOwl’s dashboard subscription is separate.
How does NightOwl pricing compare with Laritor?
NightOwl’s monthly dashboard plans are Hobby $5, Team $15, and Agency $69, without a per-event subscription fee. You provide the database and agent infrastructure. Laritor starts at $20/month with 20M billable events, unlimited apps and users, managed storage, and 30-day retention. Additional Laritor events cost $0.20 per started 100K block.
How does the calculator estimate NightOwl’s Supabase costs?
It adds one Supabase Pro database to the selected NightOwl subscription. Compute follows NightOwl’s daily traffic guidance; storage applies its rough compressed row baseline to the shared event count with 30-day retention and 25% disk headroom. It selects the smallest instance meeting the compute floor and recommended database size, includes Pro’s $10 compute credit and 8 GB disk allowance, and adds $0.125 per extra GB. This is a planning estimate. Agent hosting, maintenance, egress, optional backups, and extra disk I/O are excluded.
Is NightOwl Hobby’s 14-day lookback a data retention limit?
No. It limits the history displayed in the Hobby dashboard. Data remains in your own PostgreSQL according to your retention settings and can be queried directly. Team and Agency have no dashboard lookback cap. Laritor’s published paid plan retains recorded activity for 30 days.
Can I fully self-host NightOwl or Laritor?
NightOwl offers a commercial self-hosted dashboard and API license for $5,000 upfront, with optional $500/year repository updates after the first year. Its telemetry agent is MIT licensed; the dashboard is a separate commercial product. Laritor is a hosted monitoring service. The calculator compares NightOwl’s hosted monthly plans and does not include its self-hosted license.
Does NightOwl’s hosted dashboard access my monitoring data?
Yes. Raw telemetry is stored in the PostgreSQL database you provide, and the hosted dashboard connects to it to display your application data. NightOwl also receives agent health and aggregate infrastructure signals. Keeping the database in your infrastructure differs from running the entire dashboard and API inside your own network.
Do both tools support MCP for AI coding agents?
Yes. Laritor provides hosted read-only exception details and recorded execution context through MCP, plus in-app AI recommendations with configurable providers. NightOwl Team and Agency provide platform and application MCP tools for investigation and changes to issues, settings, and other resources. Hobby does not include MCP.
Does NightOwl capture request payloads and response bodies?
Yes. September 2026 updates added configurable incoming request payload and response body capture with route and status filters. JSON response fields can be masked; raw HTML, XML, and text need separate collection choices. Laritor also supports optional incoming body capture and can additionally capture outbound API payloads and response content.
Can I record only exceptions or detected issues with Laritor?
Yes. Laritor has exceptions-only and issues-only filters that retain related recorded events when a matching problem occurs. Full observability retains all configured activity. NightOwl supports trace sampling, separate exception sampling, and custom ignore rules. Its public documentation does not list equivalent named exception and issue recording presets.
What happens when Laritor’s calculated price exceeds $500?
The calculator shows “Ask for a quote” when Laritor’s estimated monthly price exceeds $500. Exactly $500 stays numeric. NightOwl’s subscription remains flat, but its estimated Supabase costs change with volume. Above 5M runs/day or the largest listed instance’s database size, the calculator shows “Custom sizing needed” instead of extrapolating an unsupported database cost.
Can I run NightOwl and Laritor in parallel?
Yes. Install and configure Laritor alongside NightOwl in a representative app or environment. Compare execution details, alert delivery, retained volume, infrastructure requirements, and combined collection overhead before deciding which workflow fits your team.
Will my NightOwl history transfer to Laritor?
Laritor records new activity after installation. There is no documented automatic import of NightOwl history. Keep access to your NightOwl database and any dashboard subscription you need while Laritor builds a new monitoring record.
About this comparison
Sources and comparison notes.
Published by Laritor, independently of NightOwl. NightOwl’s official product pages, paid plans, architecture, agent source, issues, alerts, MCP, and September 2026 request capture updates were reviewed on . The table acknowledges NightOwl’s Laravel native design, user timelines, custom context, issue workflow, and current body capture. Its older filtering page describes earlier incoming payload limits; the newer configuration and changelog take precedence.
“Not listed” means a dedicated feature was not found in the reviewed public documentation. Custom code or SQL may provide another way to meet that need. The calculator uses monthly USD subscriptions before tax and one retained workload. It adds a Supabase Pro database selected using NightOwl’s traffic and compressed-storage guidance, 30-day retention, 25% disk headroom, and Supabase’s recommended instance sizes. The shared event count is a storage proxy; actual row sizes and records differ. NightOwl does not charge per event, but database and agent capacity remain your responsibility. Its hosted dashboard accesses your PostgreSQL, and the platform receives health and aggregate infrastructure signals. The database estimate assumes one project in a separate Supabase Pro organization and its available compute credit. Traffic bursts, dashboard queries, and payload sizes can change requirements. Agent hosting, maintenance, egress, optional backups, extra disk I/O, trials, grants, the self-hosted license, and custom contracts are excluded.
Start with the data you need
Start optimizing your Laravel app.
Track exceptions, detect issues, and monitor performance.
Try Laritor with 300K events free.