Laravel Cloud Office Hours

Laravel| 01:03:21|Apr 3, 2026
Chapters10
Hosts discuss time zone differences and how they handle live streams across multiple regions.

Laravel Cloud Office Hours showcases scheduled autoscaling, hibernation, and usage insights to optimize costs and handle predictable traffic bursts.

Summary

Leah Thompson hosts a lively Laravel Cloud Office Hours with Devin Garbalosa and Andy Britull, walking through the newest features of Laravel Cloud. The spotlight is on scheduled autoscaling, a capability Andy explains as a way to pre-scale resources for predictable traffic like Black Friday or weekly live events. Devin clarifies the distinction between reactive autoscaling (based on CPU/memory) and the schedule-based approach, which is currently available on business and enterprise plans. Andy demonstrates a practical setup: you can define minimum and maximum replicas, set thresholds, and apply one-time or recurring schedules to pre-empt traffic surges. The team dives into real-world use cases, such as daily evening traffic bursts or weekend hibernation to save costs, and highlights how overlapping schedules are resolved with precedence rules. They also discuss related features: edge path blocking for security, an enhanced usage page that shows cost breakdowns by app and resource, and Slack/email alerts for deployment and autoscaling events. Throughout, they emphasize preview environments, the compute/hardware under the hood (Kubernetes on AWS, with Cloudflare for networking), and ongoing roadmap items like app-level notifications and edge functions. The conversation stays practical with live demos, caveats, and recommended practices like using Nightwatch for load testing and validating autoscaling behavior. If you’re evaluating Laravel Cloud for predictable workloads, this session lays out how scheduled autoscaling, hibernation, and visibility tools can be combined for cost-effective scalability.

Key Takeaways

  • Scheduled autoscaling lets you pre-scale replicas on a defined schedule (one-time or recurring) to handle predictable bursts.
  • Autoscale is governed by a minimum/maximum replica range and memory/CPU thresholds (e.g., 60% threshold).
  • One-time schedules can target specific days/times; recurring schedules can be set for daily, weekly, or weekday patterns.
  • Usage page provides cost visibility by app, environment, databases, caches, and other resources, helping you identify spend; Nightwatch integration offers testing and monitoring support.
  • Edge path blocking at the Cloudflare layer prevents bot traffic from waking hibernating apps, reducing unnecessary compute usage.
  • Alerts via Slack and email are supported for deploys and autoscaling events, with ongoing improvements for granularity and app-level targeting.
  • Preview environments continue to be a core benefit, enabling safe, isolated testing and rapid deployment workflows for Laravel projects.

Who Is This For?

Essential viewing for Laravel developers and DevOps teams who use Laravel Cloud and want to optimize costs, reliability, and visibility during traffic surges. Great for product managers and sales engineers evaluating private cloud options with predictable workload patterns.

Notable Quotes

"Autoscaling lets you set a number of replicas and basically scale on memory."
Andy explains the core idea of autoscaling in Cloud.
"One-time or recurring schedules. So, like the Black Friday sale example would be a one-time autoscaling."
Demonstrates how schedules can be used for specific events.
"Recurring ones must start and end on the same day"
Mentions a practical constraint and workaround for scheduling.
"The usage page… costs across different things."
Points to the new cost-visibility feature in Cloud.
"There are notifications via Slack and email for these scenarios."
Describes alerting capabilities tied to autoscaling and deployments.

Questions This Video Answers

  • How does scheduled autoscaling differ from reactive autoscaling in Laravel Cloud?
  • What is hibernation in Laravel Cloud and how does edge blocking improve security and cost?
  • Can I use Laravel Cloud autoscaling for non-Laravel stacks like Symfony or Spring Boot?
  • What are the prerequisites to enable Slack alerts for Cloud autoscaling events?
  • How do I estimate the right minimum/maximum replicas for my app’s recurring traffic patterns?
Laravel CloudScheduled AutoscalingHibernationEdge Path BlockingCloud Usage PageSlack AlertsPreview EnvironmentsKubernetes on AWSCloudflare NetworkingNightwatch
Full Transcript
Okay. Hi everyone. We should be live. Happy Thursday. We'll give it a few minutes for people to trickle in. Um, as you join, feel free to say where you're joining in from. Uh, I'll do intros once more people are here, but today I'm here with Oh, no. Devin and Andy. I was going to say, did you forget our names? No, I can hear myself in my ears and it made me stop. Oh, looks like your senior engineer joined, too. Oh, yeah, she's here. Of course, Ginger's here with me. Okay, I'm just going to start aggressively closing tabs so I don't hear myself echo, but I promise I did not forget uh your names. Where is it coming from? I hate that. I hate hearing myself. I think I found it. Okay, I think we're good. We're in business. Winner winner chicken dinner. Okay, I think Are we I think we're all on different time zones, though. You might be right. Yeah. I'm on the the good one central. False. Absolutely false. I uh in the middle. It works for everybody. When I used to work in finance, I used to make a strong argument that we should all operate on Eastern time since the NYSC basically ran the industry. But it didn't catch on. It did in finance. It just doesn't catch on in the rest of the world. Yeah. I'm in mountain time, which I feel like is the one the least amount of people are usually in. So, usually I say mountain time and no one like knows what time it actually is. Yeah. Well, then depending on half the year, there's like definitely Arizona, but uh I think there's parts like Montana and stuff too that you're like, so yeah. Yeah, Arizona I know, like you said, does it because right now Josh is on a different time zone than me. Yeah. Yeah. Indiana, I think, does part part of the state also doesn't observe it. Interesting. Yeah. And Arizona gets real funny, too, because it depends on where you are in Arizona whether they observe it or not, too. Really? Yeah. Oh, man. We have Ethan here. Hi, Ethan. He says, "Mountain is the best." He's absolutely wrong. Absolutely wrong. No, he's not. You're wrong. It's two against one so far. I mean, Andy's on my side more than he is on your side at this point. Hey, Taylor's in Central time, so I think that trumps it all. Right. Oh, all right. All right. That feels unfair. Leah, did you meet Ethan this week? Mhm. I did. Nice. Tuesday night at dinner. We have We have like four, five people. A lot. It's all Denver, too. It's not mountain time. It's not Colorado. It's all Denver. There are more Mountain Time people though cuz Hank's also a mountain time. Mhm. Hi everyone. Welcome in. How are you doing? Um, hi Dev C David. How are you? I'm doing pretty well. What about you Devon and Andy? It's a it's a great Thursday. I almost said it's a great Friday. So that'll that'll probably direct you how that's going. April Fools. I kept almost saying happy Friday because Devon and I normally do these on Fridays, but tomorrow's Good Friday, so we we switched it. Um, hi Irwin. Hi Monster Fernandez. Welcome, welcome. Hi Luca. Larl made me love programming. I love to hear that. Same. Yep. And yeah, hi Paul, welcome in. Welcome to your first Laravel cloud office hours and um maybe first live stream in general, but this is part of a reoccurring series of uh cloud office hours that Devon and I normally do. Today we have the lovely Andy as a special guest. Very special. Yeah, very special guest. Even though he's in central time, which he says is the best. Yeah, I was gonna say I was I was hoping you were going to take a stab at his last name. No, even after he's told me it, every time I look at it, I'm just like I'm scared. I think it's a nastier one. Brutal. Or is that okay? Are you just saying that or it was kind? That is close. Yeah. Yep. Brute. It's more of a O instead of a U. Crazy German, you know. I like it. I my husband's last name is kind of German. I didn't change my last name, so my last name still just Thompson, but that's not the German one. Okay, I guess we can go ahead and jump into it. So, today we're doing Laravel Cloud office hours. Let's do um some quick intros before we fully get into it. So, my name is Leah Thompson. I am a deval engineer here at Laravel. If you've been to the channel before or seen any of the recent streams, you've probably seen me on here. I work closely with our online communities and doing streams like this. Uh today I'm here with Devin and Andy. Devon, do you want to do a quick intro? Yeah, absolutely. Devon Garbalosa, solutions engineer at Laravel. I work on our sales team. I do the technical part of the sale uh when clients are moving mostly onto private cloud. Help them to figure out uh when they have bespoke requirements and other things how to get onto Laravel cloud. Andy? Yeah, and I'm Andy Britull, a product manager working on Laravel Cloud. Um, basically across the whole app. So, if you have any uh issues, feature requests, or uh nice things to say, let me know. And who should they reach out to if they don't have nice things to say? Yeah, yeah, we'll only send the nice people to Andy. I'll take the nice people, too. You can you can also reach out for to be clear, I'll take both. But yeah, so today we're here for Local Cloud office hours. Devon normally do these does these with me, but today we have Andy on as our special guest because Andy will be talking about scheduled autoscaling on Laravel Cloud, which launched last week, right? Yep. Yeah. So brand new feature that we'll be talking about for anyone who doesn't know what a Laravel cloud is before we get into more of the questions and stuff. Laravel cloud is a fully managed way to host your Laravel applications and it just makes it easier to bring in certain things for your project such as inertia SSR. You can just hit a toggle to enable that. Um Octane is really easy to do autoscaling. What else am I missing Deon? That cloud makes it easier to do environments SSO envirments environments. Uh dot dot dot everything. And yeah, we do have a slido that I submitted. Um it should be in the description everywhere. So if you have questions, feel free to throw them in the slido or in chat. Uh we are going to be starting out the office hours with Andy talking about the scheduled autoscaling on cloud before we get into questions that pertain to scheduled autoscaling and then general questions that people might have about cloud. So let's get into it. I'm bring Yeah, pull up my screen. So as this is coming up, Andy, I do want to just ask ask the question like why scheduled autoscaling? like what what problem does this aim to solve? Yeah. So I have a demo I'll share a little bit about um the different things but autoscaling in general when we launched cloud basically allows your app to scale. Um it's based on CPU and memory and performance. Um we got some feedback that a lot of times that's predictable for customers. And so I might be having a Black Friday sale and I know that my traffic is going to be 10x what it is on a normal day. And so instead of waiting for the giant um load of traffic coming in, I can schedule it so that it pre-autoscales instead of being a reactive autoscaling. And you could think of that in many different ways. Some of our customers run live events. And so they know every Friday they're running a live stream. So they want Friday from 8:00 a.m. to 10 p or 8 a.m. to 10 a.m. to scale it up. Um they could be running Black Friday sale. It could be um my example is a game and a lot of times games are played at night. So can I schedule my game to scale in the nighttime hours versus the daytime where I don't need as much bandwidth. So there's a lot of different reasons to want to schedule autoscaling and autoscaling is a great feature. Um scheduling just makes it that much better for the customers that have predictable bursts of traffic. Awesome. Sweet. Well, I won't ask you any more questions to take away from the demo. Let's hop in. No, go ahead. Keep it coming. Yeah. So, I was just going to start talking about autoscaling. I kind of just ran through that though. So, nice setup, but uh yeah, autoscaling lets you set a number of replicas um and basically scale on memory. And then scale schedule autoscaling gives you a little bit more um right now this is available for our business and enterprise plans um to do the scheduling. Autoscaling is not uh autoscaling generally available. Um, but the schedule alone allows you to set up one-time or recurring schedules. So, like the Black Friday sale example would be a one-time autoscaling. The every Friday from 8:00 a.m. to 10 a.m. would be a recurring autoscaling uh scenario. And so, you can go see the docs. You can chat with your AI about the docs and see how it might fit your needs. But, um, docs are boring. So, we'll jump into a demo. That wounds my heart a little bit. What's happening? The docs are boring. Everybody likes to see the the demo. So um this is my test app. So this is under my um business organization which gives me that entitlement and we have uh underneath our app cluster here we have this autoscaling tab and I have autoscaling turned on. So, anytime my CPU or memory hits a 60% threshold, I will scale up from one to two replicas. And I do have to cough, so I'm going to mute for one second. Sorry about that. That time of the year. Okay. And then you can see uh underneath the autoscaling, we have some scheduled autoscaling overrides. And so, this overrides the general autoscaling settings I have up here. And so, my app here is a game. And so I think a lot of people are going to be sitting around on their phones on Easter Sunday and I think I might want to give some capacity. Um so I have set up a schedule here to say okay on Sunday one time uh anytime my CPU or memory gets 50 I want to just go ahead and scale up. And so I have it to set to scale from two to five replicas based on those thresholds. And this will run on Sunday and then it will be done. uh it's a one-time thing. Um so if I'm if I'm looking at that real correctly, not only can you schedule this one time, but you can also make it a more sensitive autoscaling during that window. So it gives you kind of more control than just even like hey pre-scale do you know whatever like make it more sensitive. Yeah. Yeah. So, you can go down to to 50% thresholds on both of those. And then, um, I have a game, so I think, you know, looking at my logs and analytics, I see that most of my traffic comes after 4 p.m. in my time zone. Um, so every day I just want to go ahead and scale it. And so on my daily ones, I have it set at 60% thresholds, again, two to five replicas. Um, and I have it for central time, the best time zone from 4 to 11:59 p.m. um, to scale every day. And so that's both of those examples where I know I have this predictable burst of traffic every evening. And then I know that on these specific days, um, I'm going to have potentially these bursts of traffic as well and bursts of compute needs. So that's that is it in a nutshell. Um any any questions or do you guys have any um questions that are coming in? Um I don't see any questions from chat yet. I I like the name somebody gave it there. There's one from Hey, it's Danm and he said autoscaling. Yes, super autoscaling. And I did link the docs. This is the right link for the docs you were showing before, right? Yep, I believe so. Yeah. Yep. That was I linked it specifically to the scheduled autoscaling section. Yeah. Um there are a few limitations that we can walk through just a bit. Um it'll scale between that defined minimum and maximum. So it obviously is not going to go out of bounds. So you can define those and set those. Um recurring ones must start and on the same day. So that's one little that's one weird thing about you know everybody's developer and this audience knows working with time zones is oftent times headaches and so one of our constraints is that it must start and end on the same day um just because of all those potential issues and pro tip workound use a time zone that doesn't matter. Yeah true and then uh yeah one time schedules run once and then they automatically stop applying after that schedule window. So my example for Easter Sunday, it would just stop doing that at the end of that that time frame and then um that autoscaling would turn off. That's awesome. I feel like that we shouldn't call that one a limitation. That's like it's kind of like expected, right? Yeah. Yes. It's actually what you want. Yes. One of those. You should probably say it though. Um Yeah. There's some other kind of gotchas in here like when schedules overlap how that works. So we have a a bit bit of a precedence level in there as well. So one will take precedence over the other. Um yeah and you can do there's uh daily week weekday weekend weekly patterns. So your recurring can be all kinds of different things. It could be every Monday. It could be every Monday all day. It could be um just on the weekends. So, there's different ways to set those up. That's really cool. I could see there's probably like a lot of benefit. You know, I work with customers that have like internal applications for their for like how their c their customers their employees do their their tasks and one thing that they say is like we work Monday through Friday like and then you know whatever. And so this really will give them the ability to say like, hey, every weekday I want it minimum four replicas, ready to go, be able to scale, but on the weekends like shut it down to one replica. Like if somebody's clicking in there and it's a little slow, you probably shouldn't be working on the weekend anyways, right? Yeah. Is it's awesome because you can just have it hibernate on the weekend. You don't pay for it because it's hibernating. And then on the weekdays, if it's that kind of internal office tool app, you can set it for 8 am 5:00 pm in that time zone or you know flex across time zones and just say every weekday I want this to be not hibernating and I want this to be scaled up for max usage and then the rest of the weekdays maybe it scales down to one replica. Maybe someone's working at night and they need to use the tool and then on the weekends hopefully no one's working and it can just kind of go to sleep and you don't pay for it. So that's that's really the beauty of cloud in general is just this flexibility of how your compute is operating. We do have a question from Ethan too. He said, "Does Laravel cloud have autoscaling alerts for when the threshold is passed, etc.?" Yes. So we have um notifications via Slack and email for these scenarios. Um actually a project we're working on is to make those a little bit uh better and more granular um this coming month. So notifications are about to get way better and way more controllable. Um but yes, we do have alerts and uh those go via Slack and email. Do you have to enable them or are they sent by default? You have to install the Slack integration and then you can go in and enable them. Um and then you can toggle which alerts you want. So if you want failed deployments alerts um or all deployments alerts, you have that ability to send those to Slack. Um, the one thing we're working on this month is right now all Slack notifications go to one channel across all of your apps. U, we're working on app level. So, you can say, okay, I have this game and I just want those to go to one Slack channel and then I have my other app and that can go to a different Slack channel. So, that's one of the things we're working on um this month. Um, but yeah, you have to go in install the Slack integration and then go enable it and then you can turn on toggle on which of which one of those alerts you want to send to Slack. similar to email. You can go in and toggle email on or off and you can go pick what things you want to be emailed about. That's I'm so excited for that. I can tell you firsthand a lot of people that work in uh product and sales are really excited for that because I do a lot of internal testing of can I break cloud andbody right now get those alerts. I'm surprised I don't get more. you're the reason I've been pushing for it. Like I I need to quiet all these things Devon's trying to do. I think the other day ones internally, but I get the nightw watch ones and so my email it's always hard to see actual emails because I see all the nightw watch. Yeah, that's we're we're getting much better at those. Yeah, you just got to keep, you know, forcing the issue by making people mad and doing it. But yeah. Yeah, that was a fun one. There was actually one for a for a database where we do a we do like a once a day sync for something and it was spiking during that sync and I literally like pinged Luigi and I was like dude at this point can we just up the database size all the Yeah, just just to avoid the alert. That one. Was it the skills one? There was a skills one where the alerts. Yeah, same problem but this is on the uh the private cloud that we have for the go to market team. Yeah. Yeah. See, we also have other chat. We have Nuno here. Hey, Nuno. What's up? What's up, chat? Oh, it's rules reversed. I feel like we should be like, "What's up, Nuno Nation?" Like, just we said Florian. He said, "I'm here now. Everyone relax again." Thank you, Florian. I'm so relaxed now. Florian I think I think Florian needs to get like a little badge or something for like number one supporter of Laravel streams does I don't actually know how he keeps so many tabs open he keeps all of cloud running all of Laravel running and he's at every stream and active. Yeah I like it's hard for me to keep up with all the streams sometimes and I'm the one who's on almost all of them so I don't know how Florian keeps up with us to be here. We have Dave here. Hi Dave. I always feel better when Florian's around. Same. Same. Yeah. And Dave, too. Dave should be like Florian and Dave should just fight over who's actually number one sport. I don't think they have to fight. I don't think we should. I mean, but I mean guys, you're going to see it here. Laracon US 2026. It's Florida and Dave showdown. Change match. I'm gonna get a message from marketing like, "Leah, what are you promoting on the street?" No fighting, all friends. Good old Laravel PHP fun. No fight. Yeah, exactly. We got to start promoting the the road shows again. That's a good one. Instead of instead of cage fights. So, yeah, that's true. I don't Can we share the Lumo for the next one yet? I don't know if we can. I I I mean, I've I've shared it with people. We could at least tease that there's another one happening. We could talk about the last one, too. So, yeah, that is true. Yeah, I'm jealous of the pictures I saw from the Atlanta one. Yeah, that was that was a pretty cool room. That was Yeah. Oh, yeah. Was that a brewery or a winery or both? It was a restaurant brewery. Okay. I saw the big barrels and was wondering. Yeah. So, it was uh that was kind of like the back room that we had. Yeah. So, for everybody who's like just hearing us talk about this thing and honestly, there was uh there was a road show that we did, first of its kind. We went in, we partnered with a meetup in the area in Atlanta, and we did a road show in Atlanta uh last Friday and which is kind of like a pop-up meetup. Exactly. It was it was a lot of fun. Uh we did some talks, just hung out, drinks, food, apps, things. It was pretty fun. Pretty fun time. Uh went over really well. And we are doing another one April 30th in New York City. So if you're in the New York City area or you want to go to the New York City area, I'm not going to stop you. Uh come check that one out. I will be there. Uh and there will be some super special guests there, too. So definitely worth coming out for that one. I'm really tempted to to be there. It'll be a fun one. I'm excited about Florian, do you know the name of the blog post by Joe um on building cloud? I'm guessing it's something like building Laravel cloud because I'm trying to find the link. Yeah. Oh, we're talking about the question from Ricky there. Yes, there was a question. Let me pin it. What is the infrastructure behind Laravel Cloud? Yeah. So, I'm gonna ask you which part you really care about. Um there's a lot that goes into it. we could do a lot but um basically it's a Kubernetes-based environment runs on AWS as our hyperscaler uh we use cloudflare for our networking um that we do and there's bunch of different parts so we have um we have a partner with neon for our postgress offering we do RDS on private cloud uh we've we've started to do some stuff with planet scale on private cloud there's lots of different stuff that kind of goes into it but the main thing is AWS and Kubernetes I imagine if that didn't answer your question, Ricky, feel free to just ask a clarifier and we'll we'll be happy to talk about it. We also have a question. Um, Dom says, "I know it says Laravel Cloud, but could we use it for other tech stacks, say Symphony or Spring Boot, which I'll let Andy or Devon go more in depth, but I will say we do have Symphfony support for Laravel Cloud now." Yep. Symphony last month. Um, and so you can run Symphony on there. We are evaluating other frameworks all the time, other languages. Um, obviously Symphony was an easy choice because it's a close cousin to Laravel, uh, both being on PHP. Um, but yeah, we're looking at all kinds of different frameworks. Um, pretty agnostic, but yeah, obviously want to we want to build the best Laravel one to start with and then uh, branch out from there. Mhm. Yeah, I think if we go down the list of like order of things, you'll probably see the PHP language get more support before we get to Java uh which is Spring Boot. But yeah, there's definitely appetite for more on that. But to Andy's point, if uh can't call Laravel cloud if we don't do the best Laravel. So start there. I will say though, if we do bring in Java and Spring Boot support, I will whip out my old um Java Spring Boot projects to put on cloud. I will hide. Java has hurt me one too many times in my life. Me, too. I was building a video game using Java, not Spring Boot, but using Java um and GDX, which is a Java I mean, I'm not doing it anymore. I learned about Laravel and I could hear Angel singing. Yeah. like this is I had to take a course in college that was intro to object-oriented programming and the instructor got to choose what language we did the course in and I took it and it was Java and I got a D and I had to take it again and it was in C and I got a hundred so just Java just for and the worst part is Java and C# are basically the same language but for some reason I just could not understand Java I didn't take C I did C++ plus+ and C and ne I never got to C# because C C scarred me it it was a class I was going to say yeah I love C++ that was like my first ever programming language was C++ WowP how old are you I'm just kidding are you calling me old if C++ is your first programming language it's an indicator well My first true programming language and the one I normally tell people is JavaScript because it's the one I actually like went in deaf with got a job with. Um C++ was just in college. I took a course on it and I like could not have built projects using it. Yeah, I'm a I'm a recovering Python developer. So, I did link the blog post that Florian referenced which is um Joe Dixon talking about how Laravel cloud was built and talking about um specifically how it was built on Kubernetes I believe. So, that is laral.com/blog/1 minute or less how we built Laravel cloud's architecture with a dash between all of those words. But I do have it pinned right here. Pushback was your Swift, your first ever programming language. Yeah. Is that his first ever or is he just trying to use other languages to trigger us? I've also been hurt by Swift. Close cousin. That's awesome. Yeah, I thought close cousin was good. Uh, Cypion had a question. Why is there no server for Scandinavian countries, for example, in Stockholm? Uh if you would like one, go and open a support ticket and let us know. We we have heard Stockholm a few times. it's on the it's on the road map. We if we need people asking for it to kind of sell it. So, um we do have that on the list, but the more people that want it, the easier that is to to get us to provision it. There we go. where I sent you the link for the support. Thank you. Yeah. Oh, sorry. I thought the other message was to me and I was like, what is this about? Um, let me link the support one. So, cloud.lar.comdocssupport. Um, and then altoorp pounds signup support. That is the link to go to to contact support and tell them what region you're interested in. Um, like Devon and Andy said, if we don't know you're interested in it, we don't know to prioritize it or put it on the road map. And so that goes for like any region you'd be interested in us adding for cloud. Okay. Do I need to bring your screen back up, Andy? Yeah, if you want to, I'll I'll show a couple more things we've been shipping lately. Yeah, let's jump into it. U, this one's actually live today. Um, you go into your edge network and in your firewall, we now have path blocking, which was a big request from internally and externally. Um, in this day and age, a lot of AI agents and bots are out there probing everything for all these different extensions. And so we have this nice hibernation feature, which is great. My app goes to sleep when no one's using it. But when bots are hitting it, it turns it back on. And so if I want to save some money, I can go ahead and block these paths. So a lot of the common ones are probes trying to hack WordPress. And we don't have WordPress support. So we went ahead and said, "Okay, if you want to block those paths, you can." And so now people will stop hitting, you know, WP config, PHP files and things like that and and trying to find these back doors. So that just dropped today. Um, that should help a lot of people. I know my side projects, I get nightw watch alerts every time because they throw an exception. And so now my nightw watch gets flooded with events because these bots are hitting these pages and they throw exceptions and then my apps have to wake up for that. And so I lose some hibernation. Uh, so we can have those um blocked. We also ship That's a good call out on that one is your nightw watch quota will thank you for turning on. Exactly. So it causes that to go up. Oh yeah. Because if they're hitting that end point, it hits as an unmatched route. But today I learned Andy doesn't use the fallback route in his in his side projects. So I don't I am excited about it. Um, so you said since they're blocked, it won't wake your app from hibernation, right? Yeah, because it blocks it at the edge. So, yeah, it's at the Cloudflare end. So, it never actually hits your app and so your app can stay hibernating even if it has this malicious traffic trying to hit it. So, yeah, it's a nice part of that feature because the other really one time I posted about me like it was when I was working on one of the marketing sites for Laravel. posted that like it was live and someone tried to find it to dodo it but they found my personal portfolio on Laravel cloud and dodo that nice try kept taking it down so I had to like unhost it because I was like I don't want my bill to like go crazy. Yeah. So yeah, the other cool thing that we did in there which is is a really smart thing from a security standpoint is it returns a 404 not found instead of like a 403 forbidden or a block. And so if somebody is actively trying to mine your website or something like that, that 404 not found basically kind of sniffs them off the scent of like, "Oh, I found something. Let me go try and brute force that now." So I think that's another great great ad That's really nice. Yeah. The other one um that's fairly fresh is the usage page. And this is I love this page right now. Um but before and this is not very good because this is on my dab. Let me see if I can find a better guys. You saw it here first. Today Andy has spent zero dollars on his brand new period that started today. Oh yeah, that's difficult. Maybe if I go back. Oh yeah, April 2nd. April 2nd. Okay. Okay. I guess you can stay on the cloud team. You spent I have like 19 different accounts. So this was the one I had set up to demo today, but it doesn't have the best usage. Um, but long story short, uh, before we had a usage page that showed you like hours and things, which unless you're like super into the weeds on how this cloud infrastructure works, hours does not mean anything to you. So, we kind of reoriented usage to show you costs across different things. So, you can see costs at app level, you can see costs at resource level, you can see costs um, for databases, caches, buckets, websockets, and all that. So you can really drill in to see where your costs are and uh where you might be spending money and you can drill into the application. But I'll let me try to find a better example for this. I have already used the usage page to like go through I realized like some of my apps weren't um hibernating or I could have I don't know I've thought of like compiling some of them into using the same database or different things but I've already like optimized my environments and stuff in cloud based on the usage page. So I already love it. Yeah. And like I had a just cuz I have so many accounts. I had a cash that I had set up that I had like maxed out just to test our cashing stuff. And then I kind of went off and did another thing. And I come back I'm like, "Oh, what's why is this bill $500? Oh, it's because I had this cash on. Now I can go I can go look at that." But yeah, I'd maxed out a few of these things just for testing. But you can see I can drill in and see um all of these kind of cost things at different levels. I can drill into the app, different environments. Um, so it really allows you to see across your portfolio on cloud what you're spending and where at various different levels that you might care about. It uh it's a theme here. We talk about preview environments a ton, but I love the fact that you just ran into the same problem that I run into that whenever I'm like, "Oh yeah, you could change your environments." I don't use them anymore because I always use preview environments. It's like, yeah, I got one. Yeah, that's good. A good stat for cloud is almost everybody has like one environment to one app. A lot of people have staging, but most people use our preview environment. So, I can just go ahead and push code to this branch I'm working on locally. It spins up a preview environment. I can go do my testing staging there, make sure everything's cool, and then I can merge it, and it just merges it to main and and deploys it. So, I don't ever have a ton of different environments just because I use that all the time. Yeah, I love that feature so much. It It has made it has literally made an appearance at every single cloud office hours. Yeah. And then the cloud anniversary stream. I promise every single speaker we asked them like what is one um what is it like what is a Laravel cloud feature that doesn't get enough praise basically. Um and it was every single answer was like preview environments. We had almost changed the question. Yeah. because it gets all the praise. Yeah, we kept saying what's not preview environments. That's your favorite. We do have some questions about the autoscaling stuff though. Um, let me jump into there's one from the Slido. It says, "If you're scaling up to 10 replicas and need to release a fix, do you deploy the update to all replicas simultaneously or one by one?" This is a great question. So the all the deployments get done in a rolling manner. Um so they do technically try to push to all 10 at a time, but they don't if one's handling a load, it will be delayed until it finishes. And so it pushes them out um that way. So it's it does auto roll back to whatever the it looks like a failed deployment, but we obviously don't switch the traffic out um to the last successful deployment when it fails. So it's it kind of doesn't matter. But yeah, it does that. Anonymous is what I see on the on the name there. So, whoever that was, hope that answers your question. If you're in stream and that doesn't, let us know. Then there was another one here. Oh god, no. Oh, there it is. Jonathan Jonathan said, "I'm really intrigued by what you said earlier about autoscaling for game servers. Could you give me an example of a game that uses Laravels as backend?" I have two. Right. You say emoji invaders. Yeah. So this one um basically Space Invaders with emojis. Um all built on Laraveville. But yeah, I spent the Christmas break vibe coding games with the kids and shipping in the Laraveville cloud. So I have a couple versions of those. Um mostly just using our cache stuff on the back end and then Reverb to build real-time features. So between Reverb and Cache, you can build a lot of different gaming platforms, multiplayer and all that. Um, which is pretty cool. Um, and yeah, at scale well. So I think we also have some customers running games on the platform as well, not just kind of my my games, but um, Yeah, it's a it's really funny that every demo we do for these live streams is a game. Like I built a whole solitire app for demos. Yeah. Yeah. I don't know this game. Snoogi. Let's check this one out. Hibernating. Yep. Not paying for love. Hibernation. Yeah. So, if you remember Snood, if you're old enough, um this is Snood with emojis. So, again, I'm not, but I know ripoffs of this game. I could tell you right now that Andy's bill for this is about to go up. I know. I would ask, do you want to share the link? I know we're looking at it, but I would ask if you want to share it, but I don't want to like increase your cloud bill. This looks too much fun. We should Oh, I'm gonna have to find the repo to this and PR it to add like cheat modes in. I'm I'm going to start using this for That's pretty cool. Yeah. The next preview environment demo or anything. Yeah. any de dude. Yeah, I literally I I did a demo for for a customer the other day that was a very serious uh ecom business and I literally pulled up solitaire as my demo of how to use cloud and I was just like I know you guys sell like a lot of high-end materials and things but like solitire right awesome is going to be next. I love it. There is a question because we just mentioned hibernation again and we've mentioned it a lot. Um, you mentioned hibernating a couple of times. Is it done at infr level or it's during development? I think the answer is infrar level. Uh, but if you could maybe clarify what you mean by that a little bit more. Um, here's yeah, Andy, as you're going, here's where it kind of shows up in the UI. Basically on the not to get too deep in the infra side, essentially your app kind of hibernates and sits um without being on and waits for an HTTP request to wake itself up. And so you can go in and say if there's no traffic after 5 minutes, go ahead and hibernate. And you can change this. You can say 15. Um and then you can also, this is kind of a newish part is that you can do a wake up interval. So if you have like some jobs or something that you want to run every 10 minutes and you want to wake up your infrastructure um to run scheduled tasks or things like that, you can go ahead and set up frequency. So maybe you have it hibernating after five minutes and then every 30 sec every 30 minutes you want it to wake back up and run a background job or a schedule task or something like that. Um that's kind of how it works. So it's it's at the infro level. Um and it's specifically in your your compute clusters. That wake up interval. Is that new or TM coming soon? I believe it's new, but I am on Yeah, I don't think it's feature flagged. So, that's pretty cool. That's uh I'm I'm excited to try that one out. App edit settings hibernation. I don't know. They uh they recently made a change to not allow my account to have access to feature flag things for admins anymore because I've Tom Holland on his stream one too many times. Like you showed off scheduled autoscaling on accident last one, right? That was two times ago. Yeah. that was a month ago. That was like a month ago. And he's like, "Oops." And it's tried to scroll up. What what was even more funny is we literally had just finished talking about how I accidentally spill beans on things and I'm just going through the demo and was like, "Well, there it is." nice preview for people. Yeah, it's fun to see that what the team's working on and doing stuff. Uh, with the build hype. Yeah, with the hibernation. that is available on the flex instances right now, right? It's not on the pros um because of the the way those work, but it is also available on private cloud for the dedicated compute. and you said it's on compute if you're trying to get to it from the Oh, man. What is that called? The canvas. The canvas. Yes. You would go under your app cluster. Correct. Or your worker cluster because you can apply it different. Oh, no. It's only on the app cluster, right? And then it applies to the rest of them. applies to both to everything in compute. Yeah. Yep. Yeah. It's the autoscaling that is set by the different planes. Um also this was very funny. So you know Pushback said Swift. Florian said I built apps in Objective C. And Pushback instantly said how old are you? Uh that was that was at Laraconic EU last month was when I found out uh that Florine is not as young as I thought he was. So he I'll let him dox himself. He aged himself here when he said the iPhone came out after I finished my university degree if that answers your question. And um if we all want to feel old pushpack then said I was in second grade at the time. That makes me feel old. I was still in school. I was not second grade, but I was still in school when the iPhone came out. When did the first iPhone come out? 2006, sevenish. Yeah, I think the first one was 2006. I think the iPhone 3G or whatever that everybody loved that like made it like ubiquitous was 2008. It says, if Gemini is not lying to me, um, and Wikipedia isn't. It said the first ever iPhone was announced January 9th, 2007 and released June 29th, 2007. That makes sense. Yeah, I was 10. So, I don't know what grade I was in. I was 15. So, okay. Oh, man. I take back letting Florian be our uh number one supporter here. 67. 67. Okay, anyone feel free to drop cloud questions in chat. We don't just have to talk about age iPhones and 67. there looks like there's another question in there actually uh from Jonathan. Yes. What tools can we use to simulate a high frequency of requests to check if autoscaling is working? Uh we just wrote a blog about this. Uh Ksix um is a great one that you could use. Um, there is a a fun part with using KS that you should be aware of is if you are going to try and simulate load on one endpoint, you will probably look like you do yourself and Cloudflare will probably shut you down. I know that from experience. So, but yeah, the DOS migr mitigation on cloud works great just so everybody is aware. Works like a charm. looking for that blog. Yeah, I found it. Sweet. I'm not biased about how great that blog is or anything, but it is here. Devin wrote it. He wrote it. Like he says with a grain of salt, but it is a really good blog post. It's still great. Yeah. Yeah. Shout out shout out Floren and Lewis for helping me with the load test as uh I was breaking things. And shout out Anna too, who is our lovely person on the content side who and marketing side who publishes all these blog posts and also helps like edit them and everything. She's been cooking working with the team to post a lot of technical blog posts recently. Um and I know there was another one that was um Mateos and Jason Begs talking about how they cut Laravel cloud load times by 60%. Yeah, that was a cool one. That's why this dashboard's so snappy. Let me add that one as well. So, we've had a lot of good blog posts recently. We've also had ones by um Pushpack. One was talking about what AI models work best with Laravel. Um so, make sure you're checking out the blog. There's been a lot of really good blog posts. Yeah, lots of good ones. And I'm trying to make sure I didn't miss any questions earlier either or in the side. There's the one from hey it's Dan about config code. Oh yes, we can jump in and Florian had an answer. Um, so I can take a pass at this one. Cloud YAML. Yeah. So we we have some ideas on this. Um, I I expect that we'll do something with that at some point. Um, but in the meantime, Florian's answer is probably the best is we have an API and a CLI um that you can do a lot of this for yourself anyway. Um, and they work really well with agents. So you can literally go tell Claude to in the conext of your app to go set up your cloud environment and it knows you need my SQL. It knows you need a cache based on your environment variables. And so it gets you pretty close to that. But we do have something like that in the road map where you have some sort of config code that lives with your repo that can help facilitate that and and do that in orchestration. Um but it's more it's further down the road for sure. But um definitely definitely on the horizon. We'll use as soon as available. volunteers tribute for testing. I feel like whenever I try to use um AI and sometimes I this was like a few months ago too, but I would tell AI I'm using Laravel Cloud. It would try to write like a YAML file or do something. Yeah. It basically take the vapor YAML and and Yeah. Yep. And then you're like, I don't even think that's supported on cloud. It's not. No. Um, I did link the docs. So, I linked the docs for the API and then for the CLI. Um, and if you're wondering about the Laravel Cloud CLI, how that works. We do have a lovely recording um from the live stream that I did with Joe Tannen Bomb walking through the Laro Cloud CLI tool which is built using the API of course. Yeah. And if you haven't seen it yet, watch Taylor's keynote from Lur Honeyu. Um if you want your mind blown of how all these pieces fit together, merge it. Was on the phone call. My my favorite part of that is that for like eight months prior to that, he has had his like his profile picture on everything of him from the movie with the phone and he just does that and like a bunch of people were like, "Oh, he was teasing it." I was like, "They were not even connected." That's the best part. So, I linked the live stream with Joanna Mom. That's this link here that this is the recording for it. And then I also linked the YouTube short we posted of the Merit demo from Laru. So good. Um gosh it was so good. And then Dan M had another question. Um here's a cool one that I don't think anyone's asked before actually. Any plans for something like edge functions? This is one that comes up on uh some some customer calls that we come up on and um just some internal stuff that we've done. So definitely something we've considered. nothing I would say probably further down the road map than a cloud ammo. But but it is definitely definitely something that we're we've uh we've got our eyes on. Yeah, that's super interesting. And then he said, I guess it's just cued jobs. it sure could be. That's the beauty of it. Have a cued job, have an API endpoint, and just hit it. That's basically what an edge function really is at the end of the day. So with hibernation, boom, done. Yep. Imagine a cute job, but it fires instantly. It's an idea. That'd be perfect. So, I know I was quiet when you were demoing the scheduled autoscaling, Andy, but I do think that is really cool. Yes, definitely. Um, yeah, all kinds of interesting use cases that we'll see come out of that one. I guess the question I have though is like say if someone doesn't know um like obviously for like Black Friday or stuff like that, you would know you're probably getting more traffic, but when you're talking about like daily traffic, maybe they don't realize like they get a burst at like 8:00 p.m. at night or like a certain time in a different time zone. How what is the best way for people to find that to like figure out what times would be the best time to have like a daily scheduled autoscaling for? I'm really interested in Andy's response on this. I don't know how much I need to tease, but um that is coming. Okay. Um so you'll have a little bit more insight about what's happening at the edge of your network um inside of Lal Cloud. So you'll be able to make some of those decisions and have some insights that allow you to kind of customize cloud for the traffic patterns that you see. I love that. I promise without diving too deep, I'll I'll leave it at that one. Yeah. I promise I wasn't trying to set you up. I had nothing. I wasn't setting you up for today. You can kind of get there in metrics. Um metrics is something that we kind of shipped just to because we needed something, but it's something we want to build on for sure and we're going to tell that those stories a lot clearer inside of cloud in the near future. Gotcha. The way that you could start to do that today is plug in Nightw Watch. use the one click to get it going and uh I promise that will pay you dividends in the future. So kind of a combo between metrics through Laravel cloud right now and nightw watch would be kind of the best way to get that insight. for now. Yeah, for more of the infle stuff on cloud currently and then nightw watch. I mean the other thing is the nightw watch will give you what your app is actually happening, right? Because your infra could could be a red herring if there is something wrong with your app, right? So, Nightw Watch is going to tell you what's actually happening and then you could go, "Okay, that is real traffic, not my app blowing up because of something happening or some bad code or bad PR or whatever." Um, so definitely combine the two. Um, but yeah, Nightw Watch can definitely help you tune that in and see those patterns. And if you start to see, you know, over 30 days that you see the same spike on Wednesdays, go set your autoscaling. That's so funny that I asked that and Devon's instantly like, "Yeah, Andy, what what do you have to Andy?" Yeah. Listen, I get told things when they're almost done. Andy dreams up what they're going to be. So, just for what it's worth, if you really want to hear what the the aspirations are, you got to get Andy here. So Devon Devon's like, "Okay, I'm the Tom Holland, but let me let me see if I can get Andy to Andy's uh the what's the director's name of Marvel's the Marvel stuff? Forget it." Anyways, that's like Andy and I'm like Tom Holland. I only get told what I'm allowed to know so that I could tell people and then that's that's there. Plus Andy and I spent a ton of time in Amsterdam because we were the only people from Laravel that decided to stay a day over. So, we uh we slumbed around the city and uh talked about all the cool stuff coming. So, now I have another reason to stay an extra day when I go to conferences. Yeah. Yeah. It's always time to think about all the stuff you learned and all the conversations you had. Yeah. Yeah. Have some have some more good beer in in Amsterdam. That was definitely I I literally like hate beer in the US. I just drink Titos and soda. But in Amsterdam, I was like, "This actually tastes good." So, I bought some Heinekens when I got back last weekend and they don't taste as good as they do in Amsterdam. I'm I'm afraid to try Guinness in the States. I've only had Guinness in Amsterdam. that was a fun one. That made me think of baby Guinnesses. Don't Nope. I'm done. Yeah. Oh, so as we're as we're reminiscing, we have Laran US 2026, Boston July 28th and 29th. If I screwed that up, just know it is my son's first birthday the 28th. yeah, it's the right dates. Yeah. So, if I screwed that up, that would have been really bad. Yeah. So, if you haven't gotten your ticket, they're on sale now. I think CFPs are open. If you want to talk, uh, definitely go check. are open I believe until the end of this month. So definitely go ahead and submit your CFPS if you're wanting to talk at Larcon. Um I would recommend if you are submitting a CFP if you have a video of you giving a talk at another conference to like submit that link when you're submitting the CFP or if you don't then then to sub wait no not then then to submit a video of you pitching the idea for your talk. It helps to have some kind of video to tie to the speaker when people are submitting CFPs. Yes. Yeah. And then July 28th, 29th, we will see everybody in Boston. That'll be a ton of fun. And then I'm just going to plug again, April 30th, New York City, Laravel Road Show, popup meetup. Gonna be a blast. Special guests that we will not tell you before the event, so you'll have to figure out who it is. They might be teased once the Luma and stuff is um shared. I'm sure that will be shared on the Laravel PHP Twitter account. Um so make sure you're following there and staying tuned there. We'll also announce it here so you can um subscribe to us here and catch follow or um our next few live streams that will be shared as a Luma to register for the event. So, make sure as soon as that drops that you're registering if you would like to go cuz we are capping it at a certain amount of people. Like even less than what the registration amount allows. Um, if you do want to go to Laracon US, like Devon said, it's going to be great. It's in Boston this year. Go to laron. us to buy your ticket. I have that pinned right now. We do still have um like early bird ticket prices which will be up for a little bit longer. So, make sure that you are buying your ticket. Devon pushed for the road show in New York City. But another one we should mention is Larvo Live Japan. That's right. Lar that's coming up too fast. Yeah, that's coming up in May. Um that is coming up May 26 to 27th. And this is our first ever Larville Live Japan. It's in Tokyo. The venue looks amazing. One of the um co-organizers is actually Leuda who works on the Nightw Watch team. So, please make sure if you're interested in that that you go and buy your ticket for that as well at larvallive.jp. Oh, we have excited for Japan. Mateo's here. I'm jealous. Welcome in. I'm excited too. I'm going now. I I don't think I am, unfortunately. I want to, but I want to, too. If anybody's listening, they can make that happen. Yeah. No, it's a it's a three-day weekend for Memorial Day, and my wife said that uh I need to be home to take care of my kids. So, there will be no daycare on Memorial Day. That's fair. Like tomorrow. Uh yes, unfortunately. So, yes, childcare is great. I love my kids. Just in the case my wife is watching. she's like writing this down. Um, mom asked, "What what have you guys done?" Um, we show Don't listen to Devon. We have done I I think when I saw this come in, I think this is when you talked about baby Guinness. So, Oh, okay. That makes sense. We We actually showed demos. I'll bring Andy's screen back up. We showed off Laravel Cloud. We talked about scheduled autoscaling in Laravel Cloud. Um, we showed off the new usage page. what else did we show off? It was the thing Jeremy shipped today. Where is it? Oh, the new the new W one. Oh, you lost audio. Okay. See, sorry. Technical difficulties. One second. sorry, Devon jumped cuz they had a meeting and then it brought down audio for for Andy. So, we're trying to fix the technical difficulty real quick, but we are coming up to the end of cloud office hours anyway. So, we'll be wrapping up. If anyone has like a last question you want to throw in, um, you can throw it in. But, we are wrapping up. Um, Angie's going to try to rejoin to see if that fixes his audio. Can you hear? Yes, I'm back. Oh, we're back. Okay. Oh, man. That's so weird that it took your audio when he left. Okay. Yeah. Um I was just saying before you left that Devon had to leave for a meeting. You're rejoining because you lost audio and that we're just here to wrap up. Um I asked if there's any other questions. I don't see any. So, I think we might be good to just um start ending stream. But yeah, thank you everyone for being here for cloud officers. Thank you so much Andy for joining us for the whole stream, jumping in with demos and answering questions. Um do you have any kind of like last words you'd like to say about Laravel Cloud? Any of the things you demoed today? Um I don't think so. Yeah, just if you want to bring this back up. Um, just one more recap. We talked about schedule autoscaling today. We launched it a week or so ago. Um, allows you to time base your autoscaling. So, um, any feedback anybody has would be great. And on this or in cloud in general, let me know. Um, we'll we're always listening. And where would be the best Yeah, go ahead. I'm sorry. I was going to say where would be the best place to provide this feedback? Um, you can ping me on Twitter. I'm in the Discord um support almost everywhere. So um reach out, let us know feedback you have and I'll probably be back on at some point in the future. I hope if you guys invite me again to share um more features as as we release them. Yes. No, you're definitely invited. You can ping me at any time and just be like, "Hey, I have something to show off. I'd like to be on um let me I'm trying to share your Twitter." Oh, that there we go. So, this is where you can find Andy off stream. Um, yeah, off stream. This is his Twitter account. Like he said, he's also in the Discord. Is it the same kind of username? Yep. Yep. So, yeah, hit me up and let me know what you want to see or what issues you have or any other feedback. Yep. And for anyone if you are new to cloud, the place to go to sign up for cloud is cloud. com. Um, we do the office hours every other week, so it is reoccurring. Normally, it's on Fridays at 9:00 a.m. Mountain time, so 11:00 a.m. Eastern time. This week was a special case because Good Friday is tomorrow. Um, so the next cloud office hours will not be next week, but the following one. So if you have any questions about cloud, you can continue to put them in the slidoh that we used today and I will save them for next time. So here is the slido. I will link it here. And yeah, if you have questions, put it in the slido or put it um Reddit, any place like that. I'll try to find it to answer it next stream. And thank you Andy again and thank you all for being here. Bye. Thank you. Bye.

Get daily recaps from
Laravel

AI-powered summaries delivered to your inbox. Save hours every week while staying fully informed.