Serverpod 4 introduces a revolutionary full-stack development experience featuring hot reload capabilities that extend beyond code changes to include database schema modifications and migrations, enabling developers to modify both backend and Flutter applications simultaneously without server restarts. The framework integrates with AI coding agents through MCP (Model Context Protocol) servers, allowing agents to interact with Serverpod commands, apply migrations, read logs, and manage the development environment autonomously. Serverpod 4 embeds PostgreSQL directly, eliminating the need for Docker installation during development, and introduces offline synchronization with SQLite databases that share the same API and data models as the server-side database. The framework provides built-in authentication, authorization, and endpoint generation, significantly reducing the boilerplate code developers need to write. Serverpod Cloud is also being developed to enable seamless deployment of applications to production environments with minimal configuration.
Deep Dive
Prerequisite Knowledge
- No data available.
Where to go next
- No data available.
Deep Dive
Serverpod Live Coding & AMA Jun 18, 2026
Added:Hi everyone. I'm Victor. I'm the founder of Serve Pod and today I am joined by two members of our team and that's Isak and Christ. So I'm bringing them on screen now.
>> Hello.
I'm Isaac.
>> Hello, I'm Christo.
>> So, Isak and Chris is mainly working on serot cloud. Isak is the CTO for server cloud and sister is a principal engineer and uh today we are going to take some time to show off what's coming in the next version of serod and that is serverod 4. It's uh still a little bit ways from a public beta, but in a few weeks you'll all be able to try it out.
Uh but we'll give a pretty cool demo today, I think, because uh we've done a lot of work in Cerapod 4. It's a uh almost like a whole new framework.
>> For sure. For sure. We have a lot of new cool features and I think uh we're going to showcase some really nice vibes today. I'm very excited for seeing what you can cook up Victor.
>> Yeah. So the biggest new things in server pod 4 is that we have made server pod completely sort of made for aentic coding. So we added skills, we added an MCP server uh and we have tried tried this out make sure it's a really smooth experience to do a coding with server pod. We're also adding a feature called like hot reload but that you will know from the flutter side but now we have it for the full stack and it's not just like server pod that you can replace the code like you do in flatter you can actually uh even modify the database schemas and apply database migrations.
Uh if you build a website with server pod that will also be hot loaded. So it's a really really cool sort of deep tech feature we're adding and together with a coding this brings so to a whole new level.
So, um, we're going to show this off a little bit today by VIP coding an app from scratch, showcasing this new workflow. And, uh, feel free to comment on anything. And if you have questions on server, uh, or anything we're building here, uh, just write a message in the chat and we'll sure to pick it up. As you know, working with agents take takes a little while sometime while it's working. So, we'll have some time for chats as well.
So, I'm going to bring up my screen here so we can get started on some cool vibe coding.
>> Okay. Excited. Uh, so what are you going to build today, Victor?
>> I um I'm a little bit of a fitness nerd as my co-workers know. Take off.
>> You don't you don't say you don't say >> every lunch to go for my workouts. But, uh, And I should say like Victor actually interrupts meetings and says that I now I need to go because I have a schedule at the gym and uh that's that's usually what happens around 10 o'clock in the morning over here.
Yeah, that happens. But we are going to do a sort of a food tracking fitness app. I was thinking we can call it yum sum like yum is in yummy and we can sum up our calories. That'd be pretty cool showcase of stuff we can build. So um I'm bringing up my terminal here.
Server pod comes now in version 4 with a quick start command. So you can actually do a server pod quick start and we just do a yum sum app and we we're building a new interface for for both the so-alled create and the quick start command. So you can actually in the you can click on things. So it it it'll first just ask you what development environment you're using. I'm using cursor. So I'm just going to click that.
And then we are going to create the projects.
>> So when you're selecting those ids, what actually happens?
>> Yeah. So when when when we select the ids, uh it will install skills and rules and MCP servers for those different agents. Uh so that is um actually uh pretty neat because they all the for some reason they haven't agreed upon the standard which kind of sucks.
So, uh, yeah, depending on which agent you're working with, you things are named different and placed in different places, but we take all of all of that, make sure it works for every popular, uh, coding agent. So, right off the box, this should work with cursor now. So, I'm going to open up cursor uh, yum.
Um, let's hope so. Maybe install a new version of cursor. I was blinking. Who knows?
Go. All right. So, I'm bringing cursor over on the screen here. See, it's maybe a little bit of a challenge with the screen size, but uh hopefully it'll also be readable for you guys. Um so um there's in cursor one thing we need to set up for this to work and we need to go into the cursor settings and there's a tab for MCPS here.
We need to enable the server MCP and the Dart MCP. So they're installed but cursory don't unfortunately enable them by default. So >> and what do they do? So um the Dart um MCP server can do things like uh uh it can do flop run, it can do Dart format, it can uh check um Dart um errors and stuff like that. H and the server MCP can uh interact with the server start command that we're going to try out now.
Uh so uh I'm going to open up the code window here. We can actually don't need to look at the files. We're going to be vibe coding today.
>> Yeah, it's it's the old way to do coding. We we don't we don't look at code anymore.
>> What instead we're going to do is do server pod start here.
So server pod start will uh start server pod and it also actually starts and manages our flutter app which is pretty cool. Uh by default it's going to open up our app in Chrome. Um but yeah to jump back to the question you had there about the MCP server what it actually does. So the server pod MCP server allows the agent to interact with the server pod start command. So it can actually do hot restart of the server.
It can apply migrations. It can create migrations. It can read the logs from the server. It can read the logs from the flutter app. Um >> so you you don't need to use the server CLI anymore. Is that what you're saying?
>> Yeah. Yep. That's exactly what I'm saying. Everything you do in the server CLI can now be done. Oh, this is flickering like nothing else. Uh, let's make this windows as small as it can be, right? Yeah. But that's that's very very interesting. So, we can actually now build everything with an agent without having to do any manual interactions ourselves.
>> Exactly. That's the idea. So when we do server start, it will start up a flutter app with uh it's just a demo here. So I'll type my name in here. Send it to the server. We can see we calling the greeting hello method here on the server.
Uh so um everything is up and running now. Uh the next step is to build our app and we can just uh uh type whatever we want to build in here with flatter and server and the agent will usually figure it out. I'm using the composer model which is the sort of cheapest model you can run on cursor I think. Uh so even this will work even with lower tier models which is pretty neat. Um, maybe I can move it a little bit so we can actually see what's happening in the app in the background here. Um, and uh I can yeah, we we'll review a little bit what some of the files it will modify when we build something. But let's get going. So, I'm going to build a an app called Yum that counts the um the calories. Um, and while you're right, I can I see that we have a question in the chat actually.
So, the question is, I'm waiting for server chat. I'm still using the old 2.9.2 version of chat. Should I wait for an update to this module or start building everything manually from scratch?
Yes. You want to take that one?
>> Yeah. So, I I don't believe we right now have a plan for doing the updates. Uh correct me if I'm wrong, Victor, but uh right right now that is on the back burner on our side. Uh we don't have that many users on on that module. So, we have so far kind of pushed that um and and not really dealt with the that module. Um but um >> yeah, it would be really nice to get in there actually. I mean most many many >> many apps have a chat. So >> for sure >> uh yeah I don't think we can give an exact t timeline as there may be things that are a little bit more important >> but if you are in the community and want to fix it up we actually have quite a few models now written by sort of other developers and almost 100 contributors to server itself. So >> yeah, >> it's not too hard to build, but um yeah, if you do, please share it with everyone else.
>> And and I I I believe like the update we would need is like the new streaming methods and stuff for it if I remember correctly.
>> All right. So I'm just going to use this uh prompt here for Yamsum. Build an app called Yamsam that counts the calories I'm eating throughout the day. We need a calendar to keep track of days, too.
Yeah. Let's see what it comes up with.
>> All right.
So the reason a prompt like this works is because we added in a bunch of skills and also uh an agents.md file that has a set of rules that tells uh the agent how it should interact with server pod and with the MCP server because out of the box it will be a little bit confused.
Um uh so we can see now as it writes the code it actually hot reloads the server uh and some of the changes may not compile but that's not the problem. We will just hot reload the next time we have compilable code.
>> Victor, we still have the question on screen. So you >> All right, we have um another question here. Let's show that instead. there's a new streaming method coming up. Um I I would say probably yes. I I mean the this the streams we have for server pod are really really easy and great to work with. What we will build though um that we made sort of met the halfway mark if you will is uh offline sync and uh uh sort of automatic syncing with the database. So in server 4 you actually get a um uh SQLite database that works on the client side with the exact same API as you use on the server server and the same data models. So that's pretty neat.
So the next step there is make them automatically sync. So that I guess that would be sort of a new streaming method.
>> Yeah, you you're basically not going to write need to write your own crowd endpoints anymore when when we have that. That's >> quite amazing.
>> Yeah, that was because of the previous answer. We mentioned that a new chat would perhaps use the new streaming methods and those streaming methods were introduced in server pod 3 actually. So the chat module has not been updated for the streaming methods we have 3. So those are already available.
>> Yeah.
>> Yeah.
>> So we got a message here in the chat.
Amazing. We think so too. Well, let's see if this >> when it runs live code with server pod in this manner. You see the agent looping, you see some error message coming up while the agent is halfway done, but then it completes and server pod generate just runs again and again and uh recompiles and updates both the back end and the flutter app that we see here >> and the database >> and the database. Uh so you get the full stack uh thing which is it is something different I would say like I've never experienced that >> it's like it's taking shape in front of you.
>> Yeah for sure.
>> Yeah. So this is uh something why this is still a beta version. Sometimes it gets stuck on the analyze files ind. I'm not sure why that is is I think it may be an issue with the Dartm server actually uh because I get I didn't get that before but now I get it every time.
So we can just say hey do line for just do uh command line for dot analyze instead and then we will push that in.
>> Yeah and I think the analysis sometimes can be slow. Uh >> yeah, but it shouldn't take minutes.
>> No, that that is true.
>> Um so something is going on there. But u we'll figure it out that out before the release for sure. If we have to rules >> for server pod itself, then we can do that. So uh I think it's crunching away here.
>> Uh all right, we have another question here. So what was the recent um sorry I can't Victor can you bring you thank you what was the reason such problems solved by embedding posress in version 4 so uh the the benefit of actually embedding it is that we've completely removed the requirement to install Docker you can still use Docker if you want to there's no limitation really but you're not you're no longer required to have Docker on your computer and that's going to make it much easier to get you for you to get started and you don't need to install as much tools basically and that's >> that's why we we did that.
>> Yeah, it's been one of the most common reported pain points we've had that people think it's painful to work with your docky files on on server. So we just made it not be a thing anymore if you don't want to. And you can still use Docker or run your own Postgress server on your computer. But now just works as you saw.
I didn't have to start Docker or anything to run so now, which is pretty neat.
>> But obviously when you do it in production, it's a different story.
>> Exactly. And we like internally we still use a lot of Docker containers and we kind of like that workflow. But um it is a a big requirement on your stack if you absolutely need to install it. So I think it's a really nice thing uh that we can get rid of that requirement.
>> All right.
>> Okay. So we have something here.
>> We have something. I'm going to hide the bookmark bar. We get a few more pixels of app on the screen. Yeah. Let's try to sign in.
Um, so this is something we're still working on improving, but right now it prints the code on the console here. So we can copy paste the code. Uh, this will be much easier in the future.
You'll just be able to hit the C key to copy it and it will be a bit more prominent so you see what's happening.
Uh, but we allow it to paste that in.
Then we need to create a password. So, we're basically setting up our account account.
Uh, sign up. All right, we have our >> amazing.
>> Yeah. And the way we actually I I don't know how many of you guys out there have tried to vibe code flutter, but usually you don't get like really nice results visually from your flutter app out of the box. So we created a a skill for doing the UI design as well.
So you get a little bit neater results that is not just the default material design kind of pink boxes that you otherwise get. So this actually looks pretty neat. Uh >> it does. Does it work? Can you add stuff?
>> Let's see. So, um, add to log. Oh, no. No one want save the password. Okay, looks like we did.
>> Nice.
>> But we probably want to have the um uh the macros, too.
So prompt the AI to fix this for us. So this will require a change to the database as well. So it actually created a database migration, applied the migration already for this without us even restarting the server or prompting the AI. While that is working, maybe we can have a little bit of a look on how things work behind the scenes here.
Yes.
>> So something that is pretty cool is that we have the agents file.
So we were pretty clever in Can I hide? Is this where I hide the No, this is the screen is so tiny.
>> I think that at least >> Oh, there we go. Uh all right. So if we look at the the rules the original rules rules are in red. So we said say that this is like a newly created flatter and serot project and it should always use build a back end with server pod since it's a server pod project uh and and use flutter and then we give it a bit of instructions for how to work with MCP server and at the end we added a rule that is like after building the first version of the app update this agents file with information about the app we're building and then to keep the information about MCP server but remove this paragraph. So now it has a little bit more information that's useful for the agent about what it's actually building with that this is like a calorie tracking app and the user sign in with email and what is actually built. So, this setup gives you um uh a pretty neat way to yeah get set up quickly and uh get an environment that really works.
So, let's see.
>> Yeah. And in in my experience, I think those like agents file and context files give a lot of value and and they really help the agent to guided in the correct direction and it it kind of serves like a memory uh for what you're doing.
>> All right.
So, >> but we have a few questions actually in the chat, right?
>> Oh, yeah. Um that >> uh speak speaking of release, any idea when we will get the next beta uh available? So >> yeah, uh definitely a question I can answer. So uh we'll we may have a new beta already tomorrow out of that would be like we still call it a 3.5 beta, but on we're aiming for 1 of July for a release of 7.4 for like the beta version. Uh that would be a more public release with uh everything all the guides updated and uh the whole workflow flow working. Uh so that's about two weeks out and then we'll do the full release right after the summer with it be the stable release. So we have a little bit of time to fix up all the things that may uh or may not be uh super polished in this release. you know, everything I'm doing now is working out of the box.
Uh, and yeah, let's check if we got any update here.
>> Yeah.
>> And, and you are using the public version right now, right?
>> Yeah. Yeah. This is uh 3.5 bet. 10 that we are using.
>> So, so everyone can actually go to PubDev and download this if they want to.
>> Yeah, they can. But be prepared. It's a little bit rough around the ages. So if something doesn't work perfectly, it will uh soon. But great if you try it out and give us feedback on things you run Intel so can fix it.
>> Okay. So something happened here. Uh we added macros.
>> Yeah. In app. So that looks good now.
Yeah. So, let's do the Greek yogurt.
300 g of That's probably is it like 20 grams of protein or 10? H 30.
Protein is everything that matters. All right.
>> Again, Victor talks a lot about how much protein he eats lunch, so it's he really keeps a track of that.
>> Well, all right. That actually looks like it worked, which is pretty cool.
Um, but uh I thought we'd take this to the next level and add some AI stuff for this.
>> Nice. So, I'm going to drag the window out of the that screen so I can add a key for Gemini. I don't want to show that.
>> Could lead to a bad day. Uh yeah.
>> So basically what we have is um in the config file there is a password file where you can add uh passwords. In production, you put the passwords in um um environment variables typically, but >> yes, >> this is for things that are sort of semi secure.
All right, let's try to add it back in here.
uh now with a password. So uh we can ask it to use the package to do um to query Gemini.
Um, >> okay. And while you type, I can I'm looking at the chat here. I see a bunch of questions actually. So, um, can take the one with relic. So, with relic, would it be possible for some of our endpoints to use get, put, and delete request rather than all post? And I'm assuming that you mean the server endpoints here and not actually the relic ones.
>> Relic definitely can already.
>> Exactly. So relic that is fully supported and you can do any type of rest setup that you would imagine. So yeah you can define everything you want there. uh for our endpoints today we are still uh focus basically focusing on on the the post setup and and we see it more as an RPC where you shouldn't really need to care about the details of uh the requests themselves and we kind of want to make that very simple uh to use and it's really more stuff under the hood >> RPC as in remote procedure call which is not the same convention as REST >> yeah exactly and if you do need a like uh to actually define the the endpoints properly where that is important for you uh then relic is the way to go for those type of calls. Uh but typically if you like build an app it's not really that important and then you would just use our normal client and that's going to work very very nicely >> and this ties in a little bit to the second last question there is autogenerating rest API on the road map >> right >> which we've discussed quite a bit >> yeah this is a heavily debated qu question internally and we're going back and forth on this one um I I do think this makes sense uh for relic and we have discussed that quite a lot. I don't think we have a specific timeline right now but it's something we have have discussed quite a bit in the team.
>> Yeah. Something we also want to do is to build code generation for other languages.
>> Yeah. for languages other than Dart that would sort of solve the same issue which in a I mean if we can do it is maybe it's possible with AI now to to to make that into many languages quite easy uh but it would be if you can do seral generate and generate JavaScript or cotlin and uh basically any language having a rest api wouldn't really be that interesting anymore So that's potentially another way to go about it. It's not like giving you a faster horse, giving you a car.
>> Yeah.
>> Right. Let's see.
And then we have someone here suggesting that we should create a skill for uh making the authentication setup easier.
Um, >> as you saw, we have a skill for that.
>> Yes, exactly. Uh, so that is uh actually included in the next release.
>> Yeah, we have this app we're building now has authentication and that just worked on a single prompt. We didn't even ask it for adding it. It just knows how to do it. All right, let's see. Try this out. Log food. What did you eat?
Okay. uh with the inuse um estimate with AI. Uh that >> maybe the API key failed.
>> Yeah.
Try again.
Yeah. Uh that failed. Blaming the AI.
Yeah, >> convenient.
Uh, >> or maybe you can ask to debug the problem.
>> Yeah.
So what did it say there? Uh could not estimate nutrition.
>> Try again or enter values manually.
>> Think it will pick it up with just that.
>> You are a Victor. you are a please kind of guy adding these uh nice words to our friends I guess >> I usually do the same honestly but uh I I know it's a debated topic right like do you want to spend tokens on being nice or do you just want to be short and and sweet >> it's hard not to I always right like that's great let's do this now >> influence today.
>> Oh, good job.
>> Yeah. Yeah.
>> We need to keep the AI happy, you know.
>> Yeah. In the AI uprising, we want to have a nice track record with them. It's like Gilfoil from Silicon Valley, right? Like he he had a scene where where he um he basically said, "I'm all in. I want the AIS to to know I help them in the future."
So we have a question here that we skipped and that's like will you share this project or is there an existing similar demo repo? Well, I mean, you can just, I guess, try out the same prompts with with Server Pod and especially when we get a beta out, it will be uh we'll have like a complete guide of how to set everything up, which is actually quite simple, but um so I think that's the way to do it.
>> I mean, I mean, you more or less need to just install the serot, right? and then create a new project and uh >> you are good to go.
>> So what you need is fluster installed and that's basically the only dependency you need.
>> See if the demo gods are with us.
>> Yeah. But I I mean we have done quite a bit already honestly.
>> Yeah.
Yeah. I it's it's pretty cool that you can do stuff like this with just a few prompts I would say.
>> Yeah.
>> And uh and what I think what's really neat with server pod and the combination of server pod and flatter is that it's both works super well with code generation vibe coding or if you're building something serious that will work too. This is not just like a toy.
If you build something with many of the other by codable tools, you get pretty much a tool and it would be very hard to scale this up to production one day.
While with server pod, you can build real stuff. We have like we have banks, we have even governments using server pods to serve hundreds of thousands of users. It's like a super solid um product that way and system.
>> Yeah. Yeah. and you do get like the full back end and and I think one one more thing that is really nice with server pod is that you're gonna get a lot of scaffolding around it and and security parts of it like we have authentication built in we have authorization built in and we even the endpoints are generated right so there's a lot of stuff that the AI doesn't need to do uh that we just get for free more or less so it's going to you're going to end up with a more secure system and more like really good fundamentals uh which is very nice when you work with these type of systems.
>> Yeah.
>> With a full stack and backend structure to start with, not something we tack on at the end.
>> Yeah. Exactly.
>> Yeah. And we the when while we've been developing this, we also really been eating our own dog food. So like the server pod website is built with server pod. We have actually an administration app for it that we built with server pod and like the hot restart and all that.
So it's um um >> and and our cloud service is built on server pod as well. Of course, >> of course, not just server pod.
>> There's a lot of I'm sure black magic and configurations and cubernetes.
>> Sure.
>> Yeah. Do you want to say a few words about that? I second where we are heading.
>> Yes. So yeah, cloud cloud is coming along. It's uh it is available actually to sign up if you if you want to. We haven't really gone hard on it, but uh so we have a bunch of users uh on it and uh it's a it's getting to be a really solid product honestly and uh you we are in fact also hosting a lot of our own services on our own hosting platform uh including our website and other stuff.
So, uh, it's it's super exciting and I and I think we're going to have in the end a extremely nice experience with the hot reload here where you can go from an idea and you can create a product locally and then with just a single command uh more or less you're going to go out and and be live and and able to serve real customers in production. Uh, so that that loop is going to be extremely tight and very very short. uh which is super super cool.
>> Yeah. And when we release the Sod 4 beta, we'll also have a beta of SOC cloud available. So you can we'll be able to uh take like what we building today and just type so cloud deploy and everything will just work.
>> Yeah.
>> So we are getting there very fast. Okay.
Now let's see if it's any better. Two eggs. Estimate with AI estimating.
>> Okay, here we go.
>> Nice.
>> Add to log. It figured it out for us.
>> Yeah, for sure. I have I have no idea if if the numbers were even remotely accurate, actually.
>> Okay. Okay. Yeah, you know this better than me.
>> Yeah. Let's try the Greek yogurt, though.
300 grams of Greek.
Um, this is um an interesting one because uh there are some Greek yogurts that have very little protein and there's the good Greek yogurt that has a lot of protein. So, picked the good one.
>> Of course, that's the one I eat.
>> Who asked for it, right?
>> This is apparently not original Greek yogurt, which has 10% fat.
>> Oh, really?
>> Clearly not.
Uh, so yeah, that's pretty cool that managed to figure it out when I I sort of tried to code this. Just took half an hour before the live stream to see if it would work and what we could figure out for you guys.
uh and then it just got it working immediately. But uh it figured out it out eventually. But I thought it would be cool to add another feature. Um say we want to be able to upload pictures too.
>> Ah very nice. And that's that's something I always dreamt of having and building actually. Even back when I was in uni, I wanted to build that type of thing. Uh, but I never um I figured it's too annoying, you know, and but today you have like really nice tooling like it's actually not that hard.
>> Yeah.
>> Post on Instagram with a food picture.
>> Yeah.
>> And to your app.
>> That's that's amazing. Uh we do have a new question here actually.
>> All right.
So is it worth for flutter developers to switch to server pod and then using existing mature frameworks for backends like laral fast API and NodeJS um all right I mean you're you're watching a server stream so of course we're gonna say yes uh but but uh I do think the the big benefit for for you if you all is already using flutter is that you are going to have a full stack experience in the same language So you don't have to have that context switching. Uh it's going to be much much simpler and you can reuse a lot of code across the stack. That's really the big benefit. Uh compared to using another language because if you use like NodeJS or or PHP like Lar you are going to have to write a lot of stuff twice and you are going to have to like reinvent that logic multiple times and and here you're going to get that for free. And with sero you also get the entire client for free. So you don't have to write that code at all. you guys can generate that not even the agent need to write that.
So I think there's a lot of very nice benefits of going with server pod especially if you are building a flatter app >> and I mean if you flatter developer you already know dark >> so that's also a pretty big benefit if you use something like go looks quite different from uh from dark so that context switch and you also having to learn a lot of new stuff with server pod you will understand everything happens on the back end even if you are a flat developer which is pretty cool. Uh and of course yeah the code sharing is huge depending a little on what type of app you build obviously but for many apps it's uh uh a lot of logic that can benefit from being on both sides.
And the feedback we get from quite a few server pod users is that they often write code like in the flatter app that should really be on the back end and if you're using server you can just do copy paste and it's in the back end. So that can be like verification of data and stuff like that. It's easy to do on the flutter side but then becomes a hassle on the back end. But if you can just copy paste it, you do it. Um, and uh, yeah, you get this super cool hot reload rule hot reloadable stack too with 7.4 which I think like is unparalleled in any other language.
>> Yeah, that's going to be much tougher to uh that experience is going to be tougher to have in if you use a different back end. That's for sure.
All right, we got a pretty good comment there. So, server pot is a beast. Thanks for making it. I'm using it to build a message messaging app and it's been so simple and super fast. Well, thank you.
We really appreciate that. I mean, we we're putting our hearts and souls into this project. So, it's really great to hear that people are enjoying what we're building >> and also some praise for our OM I see as well.
>> Yeah.
>> Yeah.
>> Yeah. And uh I think it's really neat in seroton you'll be able to use the ORM on the client side as well and that even works with like database migrations on SQL light automatically in your app when you update versions. So that is a pretty sweet feature.
>> Yeah. And something I've personally looked forward to for quite a while, I must say. So yeah, super excited about that one.
>> I personally can't wait for getting it all the way to the sort of offline first and automatic sync. Yeah, >> that will be a very very powerful feature that will save a lot of time if you um uh build something with real-time communication. Okay, is it done?
>> Looks like it.
>> Uh shall we try it out?
>> Sure.
Okay. So, here is something we are working on that is not quite working yet. Um, and uh this is it will work in the final release. It sometime sometimes work but it's still a little bit buggy.
Uh and when we add external um packages we can do uh add packages but if they are using native code like picking an image is typically native code and plugins in flatter we need to restart serverbot but we actually build the app we just need to hook it up with a correct port and reload that browser window.
>> Yeah. Yeah. But you still have this problem with normal flatter starch as well, right?
>> Yeah.
>> If you do flutter run, you have the same thing. Basically, >> we are we're taking it to the next level with server. So, it will actually you won't need to um even oops this it's this chrome that is a little bit buggy with the green. Um but uh you will be able to do this uh without restarting server pot in the future.
>> I believe you already have an account, right?
>> Yep.
>> I hope you remember the password though.
>> Yeah, me too. Me too.
There we go. Look. And the data is still there.
>> Yeah.
>> So there you go. We have persistence.
>> Okay.
Food photo. Choose from library.
Uh let's see. I created some on the desktop here. Let's try this one.
>> A looks nice.
>> Is that BB pop?
unclear. Yeah.
>> Not really. It does. No, it's more of a salad, I think.
>> All right.
Estimating nutrition for food photo.
>> So, I I guess that can take some time.
>> Oh, there we go.
>> Salmon and lentil power bowl.
>> There we go. Nice.
>> Nice. 950 calories.
>> Yeah. Lots of sun though.
>> Well, we we'll try another photo here and see how that works. What do you think of this one? Show it. Have a guess.
>> It looks tasty.
>> It does look good.
>> But it doesn't look like something you would eat, Victor.
>> Yeah. really. I do have a sweet tooth though.
>> All right.
>> So, less calories than another one according to our AI.
>> Yeah. And less protein as well.
>> Quite a bit less.
I think it's probably healthier to eat the salmon lentil power bowl. Either way, >> I would I would imagine so. Yeah. So I think I mean this still shows how easy it is to work with a new server 4 and um yeah getting things done really fast. I think I mean say we spent about half an hour or 35 minutes building this now but imagine we spent a week on this.
>> That would be like a an app that we could release on app store.
Yeah. Yeah. I mean, imagine what we built here today, right? Like in in 30 minutes or or so 40, we have built an entire app that can get input from the user, save it to a database in the back end with authentication with like user accounts and with an AI integration to actually look at an image and extract information from it and then store that in the in the database as well.
>> Yeah. and file uploads and you know this >> right >> we run we can easily run this on an >> on an iPhone and it will just work.
>> Yeah.
And uh the back end in uh very soon with the release of Serot 4 beta, you'll just be able to say serot cloud deploy and boom, you'd have it running as a web app in the cloud and also like you could use it with your uh on your phone if you upload it to app store. So that that's pretty amazing with like zero configuration basically.
>> Yeah. Uh we have um a few more questions.
>> We do.
>> Uh we have one about Jasper. Uh and uh I would say this is something that's on our road map. I'm not sure we'll make it to the beta 4, but uh definitely going to happen.
>> I believe Kian has actually made an integration if I'm not wrong. Yeah, but it's only for serod 2, I think.
>> Okay.
>> Needs to be updated for serod 4. And I think we he made um a pull request for it, but uh it's uh not great how it works with like the hot reload of server pot and stuff like that. So, we want to make it right and make it good. But it's definitely something we want to do. Uh I think that'll be really cool. That being said, server pod comes with um templating system that is pretty nice for building if you're building a landing page or something that is perfect and that works with the hotter load. It works with cash busting stuff like that are typically a little bit tricky to things to build. So that's something we made with a integration of relic. Relic is our sort of underlying web server to make sure all that works really gracefully.
Um, >> yeah.
>> All right. Here's a a pretty cool message. We used to pitch uh Flutter to clients that just wanted an app.
Nowadays, we're doing the same with server for back end. Flutterflow like certified partners or job board would be nice. Yeah, I think that's a great idea.
We are also ramping up both sort of the marketing side of server pod but also uh we added a set of uh server pod developer experts in a program called sort of voyager. So that's going to come to our website very soon. Uh but also I think a job board and agents we we know quite a few agencies that work with server and flatter. So, >> we even we even actually made these type of badges for these type of voyagers.
So, this is a physical badge that you can sue on your backpack or something.
>> Yeah, >> looks pretty good.
>> It's super cool. We're about to mail them out to all the voyers. There are about 10ish of them.
>> Yeah, >> that's also something that we are ramping up. Um, all right. I think uh we sort of uh may uh conclude the sort of app here unless there's something more you think we will build. We have 10 more minutes. If there's some other question you guys want to ask now is the time. Um but we are I think all of us really really excited to get serod out of the door and obviously serot cloud we've been working on this for a very long time >> and it's been quite a journey. It's uh uh I mean server pod has been a solid framework for a while but uh building a great cloud service for it is quite a bit of a technical challenge. Uh maybe Isaac you want to say a few words on on the status and some some of the hurdles you overcame in building server pods. What's been the most challenging parts of it >> for for the cloud platform? like I what's been the most challenging I I think that like hosting in general has a lot of different challenges uh but uh when it comes to kind of scaling that up and managing the amount of workloads and making sure that uh we can really deliver all the hard parts for you. So we can manage the the scaling of the application and scaling up and down and managing the traffic coming in and load balance all of that that traffic and doing that in a way where you don't have to know anything yourself and you don't need to configure anything and we can just take care of that like it's really a devops as a service and you as a developer don't need to have any knowledge of how it actually works or you know all of these very specific things that you need to take care of and and benchmark and and tweak and we can do that automatically for you. I think that is really the challenge and and balancing the UX part and uh the the functionality and making that very nice and seamless and that has been definitely a huge challenge but also very rewarding I think for us uh in the team. It's been uh fun to work with. What do you say?
>> For sure. Yeah, it's very broad the functionalities that we need to work with and deliver over all this period that we've done this thing. Uh we moved from various various areas of functionality that we done. Some of them have been turned out to be easier than we thought but usually they've turned out to be more tricky than we thought.
>> Yeah, very true.
>> Yeah, it has been quite a challenge. Uh but it's uh I mean you can actually use it already. It is in a public beta but um uh it'll be a bit of a smoother process in just a few weeks when it comes to authentication with email and stuff like that.
>> And just over the last two weeks, we've released a bunch of uh usability improvements both on the web console and the command line interface S-Cloud. So we're very happy about that. Made an announcement of that today actually. So uh um try it out. It's hopefully a fairly smooth experience even though we're in beta.
>> Yeah. Yeah. And it's getting better every day. Yeah. Proving every day.
>> Uh we have a few more questions here. I know AI is all the rage now, but it's getting expensive since you're generating client database and endpoints from spy files. Wouldn't it be better to generate crude clients for Flutter 2? I think I mean the the client we're generating for Flutter is kind of like a crude client in a way. So uh from the code generation point it's very good for the AIS if you want to conserve tokens basically working with serverbot because it understands how it like utilize the code generation and just need to generate the same calls on the client side as on the back end side. So >> uh that really stays bad.
>> With that said, like you said before, uh we have the this the streaming and and syncing between the client and server um in in our target as well. And that will actually make that even easier and and require even less tokens to generate the code, right? Because we can manage that for you.
>> All right, here's another question for you cloud guys. Can you please support mini and serot cloud? I can say so because I'm using MongoDB with server pod and I don't want to pay the 29 bucks.
>> Okay, I see interesting to use MongoDB.
I would be very curious to hear more about that honestly. But uh yes, you can absolutely do that. Uh it's possible to just toggle off u the database and then you will won't pay for that and then you get a cheaper price.
>> Yeah, >> that is supported today.
And I think we have a few more questions here.
>> Yeah, I'm looking at the questions here.
Um, uh, let's see here. Are you guys thinking about building something like Django REST API UI for Serverod?
Uh I'm not exactly sure what that looks like, but uh on serot cloud and you can run it too. We have at least serot insights which is great for reading logs and seeing how much CPU and stuff you're using. Uh, I think we have some ideas on how we can extend that to be for the database users potentially sort of an admin interface for your app that just comes out of the box. That would be pretty cool. That being said, like generating that with AI specifically for your app is actually pretty quick to do nowadays.
>> Yeah, I believe we also had some community members building uh admin dashboards as well. Yeah, there are some some of these out there already. Yeah.
>> Yeah.
>> Um, all right. Next question here. Will we see the automatic generation of swagger and open API included in the sero road map at some point? I imagine it can be easy to prioritize efforts uh with so many standards on the web. Well, yeah, we I I don't think we want to say yes or no here exactly how we want to do that. It's we're still debating but maybe uh or maybe not and maybe not would be generating clients for other languages like swagger. So would be sort of swagger uh functionality. The the issue with server pod versus swagger is that server pod has a bunch of features that are not supported by swagger. Uh for instance uh we can throw exceptions on the server catch them in the client. We have dot records, we have streams and all those things are not supported by swagger. So you would get sort of a subset of the features you add to your server which is not a great experience. But if we generate a client in say JavaScript that you can call from your web page, we can support all those things.
Uh so we we're debating there will be the um best way to do it. Uh not a yes or no at this point, but we'll see. We we'll do something that would be great for you guys in that department. That's for sure. Here's a pretty fun question. If uh SQLite support landing this release and the answer is kind of.
So uh it's we we have built um uh SQLite for server pod even on the server both like server and client side. Uh the thing with SQLite support is it doesn't have support in server cloud. So that's uh uh one thing and we don't have support for authentication and future calls and there are a few of those that use more advanced uh uh postgquest features. So therefore it's sort of experimental. You can toggle it on if you want to use it. Uh but we may fix that in the future. All of those I would say and it's the exact same warm for SQLite as for postcripts. But obviously some things is it like concurrent transactions or something like that that doesn't work?
>> I think I think so. Yeah.
>> Yeah. Uh so that's why we haven't uh uh made it like a a feature you see in the setup of the server.
Uh all right, I think we've been an hour. So that's what we plan for you guys today. So, thanks a lot for tuning in and for all the great questions and we'll be we really really pumped to get server 4 out of the door and serot cloud and the whole package to you as fast as possible.
>> So, it's a it's quite a capable package now.
>> Yeah. And it's always exciting to uh to speak with uh people and hear what you're building and what you're doing.
Uh and like yeah inter interact with the community. I think that's uh always very nice.
>> Yeah.
>> A shout out for our discord. If you're not on our discord, please join.
>> Yes. So if you go to so.devisord or you can go to the web page and there would be a link even on the front page I think. So uh that's great. Uh we'll we'll post more updates there. Uh and I think well that's all we had for you guys today unless there's anything else from you guys.
Well, thanks for tuning in and we'll make a stream like this soon again.
>> Yeah. Thank you very much. Have a good one.
Related Videos
I’M COVERED, NOT CONDEMNED | R&B Gospel Soul Music
JesusHeals247
388 views•2026-06-14
One Year Later: The Small Habits That Helped Me Lose 40+ Pounds
Rkted1234
273 views•2026-06-18
The smoothest Tsk Tsk Tsk I have ever heard
VELVETFLY
1K views•2026-06-16
Bugfixes For Chaos Reign! - Mechwarrior 5 Mercenaries
TTBprime
2K views•2026-06-16
Engineer to Government Bank Officer|FREE SBI & IBPS Webinar| Bank Exam Strategy 2026 | Learn On-Line
learnonlineBengaluru
2K views•2026-06-14
Simucube 3 Ultimate | The Pinnacle of Direct Drive Force Feedback
simucube
314 views•2026-06-16
That Vegan Teacher is live!
ThatVeganTeacherYouTube
66K views•2026-06-16
HINT: Panthers unlikely to trade their 2026 first round pick before the draft
LockedOnPanthersNHL
417 views•2026-06-15











