Laravel site care
Every Laravel app,
kept current.
Uptime from several regions, SSL and domain expiry, advisories in every Composer and npm package, and support dates for Laravel and PHP. Plus the scheduler, queues, migrations and backups, from inside the app. One screen for every Laravel app you look after.
01 · What Porro checks
Checks from the outside.
Facts from the inside.
Every site gets outside checks the moment you add it. Add the connector and you also get what only the site knows: versions, advisories in composer.lock and package-lock, schedulers, queues and backups.
porro/laravel-connector
Laravel connector adds
read-only · open source02 · In the app
Site health at /porro.
The connector adds a /porro page to the app, closed to everyone outside local development unless a gate lets them in. It works on its own, and keeps what it sees on the site.
- +Advisories, support dates, failed jobs and the scheduler
- +Scanner probes, failed logins and fake Googlebots, ranked by IP
- +Block in the app, at Cloudflare or in nginx, with each block confirmed first
03 · Updates
Updates you can merge,
not just a list.
Porro checks laravel/framework and every Composer package, and opens a pull request for the patch and minor updates you pick. A major upgrade, like Laravel 12 to 13, is flagged with the upgrade guide and never bundled in.
Updates · harbour-arts.org
4 waitingPull request
opened by Porro04 · Advisories
A critical Laravel advisory, published 6 days ago.
Porro matches every advisory for laravel/framework, and every other Composer and npm package your apps use, against each composer.lock and package-lock within the hour it’s published, and the fix arrives as a pull request. The latest:
05 · Support dates
Laravel 11 is out of security fixes.
Porro tracks support dates for Laravel and PHP, and flags every app on a version that’s running out, weeks ahead. The same data powers our free end-of-life pages.
Cycle
Status
Released
Active until
Security until
Latest
Questions
Something else? Email [email protected]. It goes straight to the people building it.
Which Laravel versions does it support?
Laravel 11 to 13, on PHP 8.2 to 8.5. Outside checks (uptime, SSL, domain) work on any site, with or without the connector.
Does the connector change my site?
No. It’s read-only. It sends one signed report on a schedule and after each deploy, and never accepts commands: Porro never connects in. Every line is open source on GitHub.
Do I need a Porro account for the /porro page?
No. Site Health, suspicious activity and blocking work on their own in the /porro page, and keep what they see on the site. Connect Porro to add uptime, SSL, domain and server checks alongside every other site you look after.
Will Porro upgrade Laravel 12 to 13 for me?
No. Porro opens pull requests for the patch and minor updates you choose. A major upgrade like Laravel 12 to 13 changes more than composer.json, so Porro flags it with the upgrade guide and leaves the upgrade to you.
Does it work on Laravel Cloud and Vapor?
Yes. The platform runs the scheduler for you, so there’s no cron line: turn the scheduler on (Cloud) or leave it on (Vapor), and set PORRO_KEY as an environment variable.
Do the connectors cost extra?
No. The connectors are free and MIT-licensed, and their pages work without a Porro account. Porro’s plans are priced by sites, not seats.
Also looking after other stacks?
See your Laravel apps in one place.
Start a free trial and add your first sites in minutes. Outside checks need nothing installed; the connector takes two commands.