# Laravel: From CodeIgniter edits to tools we build with

> Taylor wanted to build web apps, then built a framework. The story of Laravel, its PHP toolkit, and my connection through TomatoPHP.

*2026-11-03T16:46:14Z*

He wanted to build a website, so he built a framework first. Why?

Taylor Otwell wanted to build web apps for his own projects. While using CodeIgniter, he found that the tools he wanted kept pulling him into changes to its core. Should he keep altering the foundations, or build the toolkit he needed?

## In 60 seconds

Laravel began with Taylor’s own web-app development needs. Work started in 2010; the first release arrived in June 2011. Laravel is a framework built on PHP, with routing, database tools, and other facilities for recurring application work. I use it too, and created TomatoPHP: over ninety open-source packages.

## Whose account is this?

Taylor described the initial problem on The Laravel Podcast in 2017 and discussed the development and release dates on Build Your SaaS in 2019. These are two accounts from the creator. His desire to build his own applications supplies the hook; it is a narrative summary, not a quotation or a claim that he had never built a website before.

## Change a bulb, demolish the ceiling

In the 2017 interview, Taylor described wanting an ORM, dependency injection, and template inheritance. Integrating automatically resolved dependencies into CodeIgniter controllers required intrusive changes.

Like changing a light bulb and ending up demolishing the ceiling!

That is our analogy for the work, not a historical home renovation. He could fork the framework or start a new one. He chose a fresh start.

## Development in 2010, release in 2011

In the 2019 interview, Taylor dates the start to around September or October 2010 and the first release to June 2011. Development and public release are different milestones. Laravel did not appear fully formed in a single day.

## A toolkit built on PHP

Laravel is a web application framework, not a new programming language. PHP is the language underneath it. Routing connects a request to the code that handles it; Eloquent lets developers work with database records through models.

Instead of rebuilding the same foundations for every application, you have tools to build on. You still design the business rules, write the application logic, and test the result.

## My connection: TomatoPHP

I use Laravel and created TomatoPHP: over ninety open-source packages. My aim is to turn repeated work into tools other developers can use too. The repositories include Laravel and Filament packages, with contributor credits.

That is a package claim, not a count of every GitHub repository. The collection includes historical packages; check each package’s requirements and compatibility before adopting it. Filament is another layer in the ecosystem, not another name for Laravel.

## Learn it if

Learn it if you know PHP and want to build stores, business systems, or subscription services. Start with a request reaching a route, code working with data, and a response returning to the user. Add tools as your project needs them. Cashier is an official example for subscription billing; it still needs your application logic.

## Frequently asked questions

### Is Laravel a programming language?

No. Laravel is a PHP web application framework. Learn PHP fundamentals so you understand the code you write.

### Did Laravel start in 2010 or 2011?

Development started in 2010. The first public release arrived in June 2011, according to Taylor Otwell’s account.

### Is TomatoPHP the same as Laravel?

No. TomatoPHP is a collection of open-source packages in the Laravel and Filament ecosystem. Check each package’s requirements before using it.

## Sources

- [Taylor Otwell — The Laravel Podcast, 2017](https://laravelpodcast.com/episodes/c7807d42/transcript)
- [Taylor Otwell — Build Your SaaS, 2019](https://saas.transistor.fm/episodes/taylor-otwell-didnt-even-like-computers/transcript)
- [Laravel — framework repository](https://github.com/laravel/laravel)
- [Laravel — routing](https://laravel.com/framework/docs/13.x/routing)
- [Laravel — Eloquent](https://laravel.com/framework/docs/13.x/eloquent)
- [Laravel — Cashier](https://laravel.com/framework/docs/13.x/billing)
- [TomatoPHP](https://github.com/tomatophp)
- [TomatoPHP packages and credits](https://github.com/tomatophp/awesome)
- [Fady Mondy](https://github.com/fadymondy)

## Read next

- [Python](https://fadymondy.com/en/blog/why-slow-python-won-ai)
- [JavaScript](https://fadymondy.com/en/blog/javascript-history-why-it-won)
- [Java](https://fadymondy.com/en/blog/java-history-cable-box-deal-android)
- [C++](https://fadymondy.com/en/blog/cpp-history-from-phd-to-arduino)

---

Source: https://fadymondy.com/en/blog/laravel-history-from-codeigniter-to-tomatophp
