Laravel AI SDK v1 adds tool approvals and new conversation storage. Keep authority in the app, treat state as data and plan the upgrade before you deploy.
Blog
Blog
13 articles
Sharing an app between businesses means following the tenant past the browser: queries, files, caches, queued jobs and notifications, tested with real accounts.
Laravel 13 and its AI SDK make AI features easier to add. Give AI one defined job, keep decisions and permissions in your own code and plan for bad days.
A backup is not a recovery. Set recovery point and time objectives, map what lives outside the database and rehearse bringing a real workflow back.
Use polling when a little delay is fine and push when people are waiting. Publish changes after they are accepted and treat reconnection as part of the feature.
A portal can look fine while background jobs have stopped. Give every alert an owner and a useful question so failed work never goes unnoticed.
Laravel Cloud simplifies deployment. For a real business app, rehearse queues and schedules, compare the operating model and keep an exit route.
Laravel 12 is a deliberately calm upgrade. Use the breathing room to check dependencies, treat the new starter kits as a starting point and plan support.
Inertia 2 gives Laravel portals an interactive frontend without a separate API product. When it fits, when an API earns its place and when simple pages win.
Laravel’s deferred functions, Cache::flexible and queues change when work happens. Choose which kind of later a task can safely tolerate.
A paid order can still miss the kitchen. Set clear cutoffs, separate acceptance from notifications and plan recovery when one step in a Laravel order fails.
Laravel 11 brought a slimmer app structure and Reverb. A smaller skeleton isn’t an architecture: give each business change one coherent path.
Turn reading into results
Like what you’re reading? Let’s put it to work on your brand.