Apr 24, 2024
The first commit
The initial commit to the Laritor Composer package marked the beginning of a Laravel-first observability platform.
View the initial commitAbout Laritor
The story behind why Laritor exists.
Laritor began with a familiar production problem: knowing that something went wrong, but not having the context to understand why.
Meet the founder
Hi, I’m Srinath.
I’m the founder of Laritor. I've been working with Laravel since Laravel 5, and I currently serve as VP of Technology, leading Product, Engineering, DevOps, and QA teams at my day job.
That work has involved building and operating large-scale Laravel applications. I care deeply about developer experience, especially the kind that helps teams spend less time guessing and more time solving real engineering problems.
Laritor came from that experience. It is the tool I wished I had while trying to understand what was actually happening in production.
X GitHubThe problem we kept running into
The difficult production issues rarely looked like exceptions.
A customer could not submit a form. Recommendations disappeared on checkout. Payments became slow. Users experienced problems that could not be reproduced after the fact.
Often, nothing had crashed. These were logical issues shaped by a user role, session data, cached data, timing, background jobs, feature flags, or a particular application state.
Traditional logs rarely held enough context. Generic APM tools showed isolated metrics, but not the complete story. The biggest challenge was not finding exceptions. It was understanding exactly what happened during one request.
Laravel context, connected
Why Laritor was built
I wanted an observability platform that understands Laravel. Not just PHP, metrics, or traces viewed separately.
A request should connect the work that happened inside it. Queries, cache activity, jobs, mails, notifications, outbound requests, logs, and exceptions should appear together, in the order they happened.
Developers should not need to jump between five dashboards to understand one production request.
Talking to other engineering leaders
This was not just my problem.
Conversations with engineering leaders at other companies made the pattern clear. Teams everywhere struggled to reproduce production-only issues and wanted deeper visibility into their Laravel applications.
Those conversations validated the idea behind Laritor. The need was real, and it was shared.
The journey
Iterating toward something teams value.
Nov 07, 2024
Laravel Nightwatch was announced
It was a shock to learn that the Laravel team was building something so close to Laritor. I faced a real dilemma: continue or stop. I had already invested deeply in Laritor, and decided to continue despite knowing I would face strong competition from the Laravel core team.
My reaction to the Laravel Nightwatch announcementJul 04, 2025
Laritor was introduced
After more than a year of development, iteration, and solving hundreds of edge cases, Laritor was introduced publicly.
Nov 09, 2025
The first paying customer
The first paid subscription was a meaningful moment. It showed that someone trusted Laritor enough to pay for the value it provided.
Dec 15, 2025
A major UI refactor
Laritor’s interface was substantially refactored using the feedback customers shared about their daily workflows.
Today
Built with customers
Laritor continues to evolve through direct feedback from the Laravel teams who rely on it.
The hard part
Growth was slower than expected.
At first, almost every customer was on the free plan. It was tempting to wonder whether the product wasn't good enough, or whether Laravel developers simply didn't care about observability.
Instead of assuming, I started talking directly with users. Those conversations changed the product. Many features in Laritor today exist because customers explained what they needed in their actual production workflows.
That habit of listening has remained central to how Laritor is built.
Nov 09, 2025
The first paying customer.
It was not about the money. It was a sign that someone trusted Laritor enough to pay for it. That confidence made it easier to keep investing in the platform and the customer feedback that shapes it.
Laritor today
Trusted to handle Laravel at scale.
Laritor now processes more than 1 billion events per month without impacting the performance of our customers’ applications. Customers trust and run Laritor in their high-traffic applications because of our commitment to providing best-in-class Laravel observability without performance trade-offs. Read about Laritor’s architecture.
The future
A personal commitment to Laravel teams.
I started Laritor because I wanted the observability platform I wished existed while leading engineering teams. Every customer conversation shapes the product. Every feature is built to solve a real production problem.
My commitment is simple. Keep listening. Keep improving. Keep making Laritor the best observability platform for Laravel applications.