Name: SupERPower Hour Session 2 — App Building with Replit
Uploaded: 2026-04-03T18:30:04.441Z
Duration: 1 h 24 s
Description: SupERPower Hour Session 2 — App Building with Replit

Transcript for "SupERPower Hour Session 2 — App Building with Replit": Hello. Hello. Thanks all for joining today. We're just gonna give her give give everybody a minute or two to join us. And while we are waiting, if you wanna drop in the chat, if you've vibe coded something before or if you're looking forward to vibe coding, for today's session, is there something you'd wanna learn? Go ahead and and share it with us. Alright. So this is session two of our four part session that we have called superpower hour. If you don't catch the green in the ERP there, this is all about giving finance and accounting teams superpowers, and it's a series we're building on all the sessions. And this session, I'm honored to have two amazing guests I'll talk to in a second. This is about app building with Replit. And if you're not familiar with Replit, it is the leading tool for and I'll I'll let the Replit team introduce it. But just to kick things off, my in my own words, the leading tool for building your own apps for those that really often have no account or sorry, no technical background at all. So myself included, know nothing about engineering and have been building apps, and we'll talk through that today. So last time and it's recorded, and you should have all received the recorded session if you missed it. Prompting and vibe coding for finance. We went through some use cases, how to set up an MCP. Again, today is gonna be, with Replit. And then we've got two more sessions after this. And it's every Friday at 10AM Pacific, 1PM eastern, for this four part series. So speakers today, I am honored to have, Mo Alsabawi joining, and he's gonna share how Replit's own accounting team uses Replit to build apps for internal use. He's a CPA and senior director and controller at Replit where he leads accounting and financial operations. And Moe brings over a decade of accounting experience, including roles as the controller at Bloomreach, Red Panda, and accounting at other places like Amplitude, and began his career as in public accounting at BDO. And we will have a live demo of building an app in Replit with Diego Chavez, an enterprise field engineer at Replit specializing in AI and with a background in technical account management at places like Retul and even taught software engineering at App App Academy. So he's the perfect person to to help us, learn how to to build today. Alright. I'm gonna go ahead and stop sharing, and I'm gonna hand it over to Moe. Thanks, John. I won't be sharing right now. I'll just talk about, you know, how Revlon uses five coatings and what AI means for Revlon for for myself. So, you know, in the past, like, currently, you know, AI, people are using it to supplement your work, you know, do better memos, you know, get Excel help, and have faster draft. Lab coding, I feel like, is a different category. It's, like, supplementing your workflow. It's you know, instead of supplementing your workflow, you're actually building point solutions for it, and the output's an actual working application. So that's how we should be we should think about bycoding. It's like, what tool would help me do my job better? And what, you know, prompted me to build my close app, which we'll talk about and potentially will build one in front of you, is, you know, I was the problem I was trying to solve so we we currently use FloQast. It's a it's a great close reporting tool. And, typically, my experience of building close packages is, you know, collaborative spreadsheet or Google Sheets where everyone gets their comments together. You know, you paste your financials, you share it around, you update formulas, you know, roll forward them every month. And as I as I was building that for Replit, I thought to myself, you know, there has to be a better way. Like, you can't you can't just you know, just because it worked in the past doesn't mean it's the way forward. And that's why, you know, I'm using FloQast and, you know, it's a one size tool fits all in terms of, like, they're out there. It works for all the companies, and it's made for, you know, every company to use it how they want you to use it. So I was thinking to myself, like, why not just buy code, my own closed tool and closed package with automated ERP feed? So we're lucky to have Campfire that has, like, really simple integrations, custom reporting, and, you know, the features that I want that I think is valuable for our team and no one else's team. Yeah. In in the past, you know, you view these solutions as, like, an engineer problem. Like, when I first was introduced to a closed tool way back, I thought our engineers can probably build this tool, but I'm not gonna go and waste their time to you know, time away from building our own products to using to building, you know, accounting tools that only really accounting cares about. So that trade off always was there where I was like, I'm not gonna prioritize this internally, so I'm just gonna suffer the manual consequences. But with by coding and what Repli can do, you're essentially not having to do that trade off. You effectively have an engineer, you have a product manager, you have a designer at your fingertips that can build whatever you want. So I assume they have, like, zero accounting knowledge, and I just tell them exactly what's to build and describe it and keep on iterating on that. And, obviously, it's not perfect the first time around, and I'm sure Diego will build it, and there'll be some, you know, areas that we wanna improve on. Right? Like but that's the the point of it. Nothing will be perfect, and you keep on you can keep on iterating it. So, yeah, that's how we what what what that's where I got today in terms of my closed tool where I figured we just build our own. You know, I have you know, any problems I see with it, I can just get it fixed versus having to wait for a vendor to fix it. And, yeah, not to even mention, like, the cost savings of just having your own tool. So, yeah, that's yeah. The closed tools are really important. You know? Roughly a vibe coding app that we built. We use it in other areas in our in our finance teams. Obviously, budgeted actual dashboards because we're able to connect it to different systems. You can have them surface. That's really simple, you know, tool you can build. Even commission calculators, like, you can show have your reps see, you know, how their commissions will be paid out based on, like, the their attainment. Headcount planning tools, we have it integrated with Slack so you can get approvals when you have a headcount change. You know, endless endless possibilities of what we're where you can build. That's awesome, Moe. And it it sounds like one of the best, one of the most valuable pieces is it's, like, truly built for Replen. Right? It's like you if you like your own commission planning tool, it's perfectly built for your own commissions. Like, your own closed tool is perfectly built. for the Replit Clothes. It's like every feature, you kinda put all the buttons exactly where you want them. You want exactly how you want it to work. Is that one of the main I. know you mentioned cost savings and some other things, but when you say. that's, like, the main benefit is, like, this was built for Moe. Yeah. Exactly. So it's funny because as it's kinda fun building it because, you know, you so as as I was building my closed tool, I was like, okay. How would other companies want this? Like, how can I make this generic? But But I was like, why am I trying to solve for other people's problems? Like, this is my closed tool, and only my team is gonna see this. So I'm gonna have it for our use case. So I'm gonna have our financials map exactly to how we map it. I don't need to factor in other companies and how other people would wanna use a closed tool or their reporting. So that's what's great. It's like a customized tool for everybody. So everyone's tool will look different and tell it to you, and that's, like, one of the main benefits. It's just not a one size fits all commission calculator or closed tool. Cool. Awesome. Great. Yeah. That's a lot of talking from me, so I wanna hand it over to Diego who will actually, you know, live build a Close app, and we'll do it real time. Go for. it, Diego. We're excited to see this. Yeah. Well, hello, everyone. My name is Diego Chavez. I'm a field engineer here at Replit. And today, I'm gonna walk you through kind of how to approach Vibe coding and how to use a tool like this to come up with any solutions that you may have. Know, John, you've been building quite a lot with Replit, and I wanna make sure that when people are approaching a tool like Replit, they're, you know, well equipped with specific, like, workflow to be able to actually solve their problems. So we'll be working into that today. John, is there anything else before I dive in that you wanted to show or or speak on? Yeah. I'm happy to quickly show. I know you're gonna walk through an accounting use case on the close. I'll just quickly show something for the finance folks. I know you mentioned budget versus actual, Moe. So I'll just pull up something real quick, on something that I built, and, and then I'll hand it back over to you. Okay. So here here's one in Replit. I built a a thirteen week cash flow app. This is one that, you know, we're doing at Campfire. I had it built into Campfire's APIs. So I just, had it grab the APIs here. So it's kinda fully integrated into our ERP, and then it went through, and it built it out. And so here is kind of a fully working version of it. And, you know, I can go in here and and make edits or, like, all of my budgets. I can have, like, each of my budgets set up, and I can create a new forecast. Or I can go view the details, and it's got a a weekly walk on actually everything coming out of the GL on the casual forecasting that it did, how to build a summary, and then lots of settings. Like, I can resync data, and it's all kinda securely running, with Campfire data. So I'll hand it back over to you, Diego, as I would love for you to share with the group how we can go ahead and build apps like this as you walk through a close. Yeah. Awesome. Okay. I'm gonna go ahead and share my screen and, just dive right in. So, hopefully, everybody can see this. Perfect. Okay. So, right now, what I'm gonna do is walk you through, a couple of different things. So this is basically gonna be a session for those who have never VIBE coded before or never really worked with Replit before. So think of this as like a crash course, right, a one zero one. So, I've broken up today into four different parts. So one, we're gonna talk about what is Replit. Right? Talk about the platform and talk about what it can be used for. Then we're gonna kind of give you a solution framework. Right? So how do you approach a tool like vibe coding? If you've never done that before, it could be a little bit scary. Right? So, I'm gonna give you a little bit of a pattern, a little bit of a thinking pattern so that you can kind of be successful right as you start. And then we're gonna actually get into the nitty gritty. Like, how does it work? We're gonna talk about the different modes, what I recommend, and then we're gonna look at a live demo of me trying to build this application that that Moe had described earlier. Okay. So let's talk about, like, what Replit is. So with Replit, it is a complete software creation platform. That means that anyone can make an app. You don't need to know how to code. Right? All you need to do is be able to use natural language and have an idea and describe what you want. And the reason that Replit is so powerful is that we actually give you everything. Right? We have a native environment. You don't have to set anything up. We take care of all of that. We figure out how to put it on the Internet. You don't have to go make the app and then figure out how to put it on the Internet. We take care of all of the hosting. And the second thing that we do is we give you, AI as a partner. So you'll notice that, yes, the agent that you're interacting with does, in fact, build applications, but it can also answer questions about your applications. So if you don't understand something as you're building, the agent will be able to actually help you. So think of it more as a partner rather than just someone that is just gonna be doing work for you. Right? And then lastly is we do give you the the ability to collaborate. So you can invite people here into an application that you're building so that you can both be working on an application together if you guys wanna collaborate on a on a solution that you have with, like, a teammate. So what is Replit used for? So where we've seen Replit shine, is in a couple of different areas. So one is prototyping. Right? You could make a bunch of mocks. You could make a bunch of designs. This is something that we've seen be really, really powerful. And then the second is internal tools. So just like mobile, that dashboard, you can go ahead and connect to data, build dashboards that specifically solve your problems, and they're gonna be custom solutions that you can build because you understand the problem best. You can also make presentations. Like, this presentation was made with Replit, animations, automations, things of that nature. Okay. So let's get into how we are going to approach a a tool like Replit. So this is a typical framework that I recommend. One is think about what you're trying to build. So for us today, you know, I'm trying to build this closed management tool. Right? Think of this as, like, an upside down triangle approach. So you start with really broad brush strokes, and then you kind of get more specific as you iterate on your solution. So the second thing is think about what data are you trying to bring into this app. Right? So where does this come from? Does someone upload it? Are we connecting to an API? Are we just trying to connect to, like, a a spreadsheet? Think about where the data comes from. And then think about what are we trying to do with that data. So are we trying to filter it? Are we trying to compare it against other data that we have? Calculate any interest, things of that nature. And then lastly, right, the design. Right? This is the fun part. So you get to, you know, incorporate any branding that you want, any stylistic choice that you want. You could iterate on this for for days and days and days and just keep tweaking things till you get them just right. So, let's get into the more, practically speaking, in the way that you would practically use this. So Replit has three different modes that, I'd usually recommend working with. So one is design mode. Usually, I recommend people starting here. So this is basically just describing what you want to see in general. Again, it's that upside down triangle. And then Replit will produce a mock up of that. You could then take this mock up and then make a bunch of tweaks that you'd like to do that you'd that you'd like to see, and then you could transfer into build mode. So once you are in build mode, you are actually gonna be creating an actual app, real code. So with every prompt in build mode, you'll be actually creating code that is actually being created by the agent to produce your application. And then as you can see, we have a plan mode here, and I I like to kind of emphasize that it's best to go from plan mode to build mode, from plan mode to build more mode, because, essentially, this is the idea of that collaborative AI agent. Right? So you can ask questions against your agent about your app. And because your agent made your app, it knows it best. So if you ever get stuck, if you need recommendations on where to go, this is what I would recommend switching into is is plan mode. Okay. So I'm gonna go ahead and just hop right into the platform now. Give me one second here. Okay. Now I'm gonna be sharing this tab instead. So when anyone kind of hops into Replit for the first time, this is what they're gonna see. This is gonna be your entry point. And there's a couple of things that I wanna point out. So one, here, we have this, like, input box. This is where we're actually gonna be interacting with the agent. So this is where we're gonna describe our our idea, talk about what we wanna make. And then down here is essentially all the things that we can make. So we can make a website. We can make a mobile app. We could go, and just make a design, which is, like, just a mock up, slides, animations. Everything that you see here, is something that you can make, with Replit. So we're gonna make a website here or an app. This is where you could also look at your various projects that you have, any integrations that you might wanna incorporate, and then your settings and things of that nature. So I'm just gonna go ahead and get started. And, given what Moe was describing, I'm going to try and recreate it. So I'm gonna say, build me a an accounting close tool, a close management tool, with three pages. So I want three pages. And those three pages are gonna be a closed checklist. And that essentially is gonna be a task list, where I can assign owners. I can assign owners. I can assign due dates. And let me think about this. I wanna mark my tasks. Right? So I wanna be able to mark my tasks, and I wanna segment them, right, as either maybe they're prepared, maybe they've been reviewed, and I want to have some feedback, like a progress bar. So I'm gonna say, I wanna mark my tasks, as, either prepared, reviewed, and I want a progress bar a progress bar, and I want a progress bar. That's the first page. I also wanna, kind of manage, reconciliations here. So I also want can't spell today. Ciliations. And this is gonna be a list, of a balance sheet, a list of balance sheets, balance sheet accounts, where I can enter a work paper a work paper balance, and it shows whether it tries, the geo balance or not. So I'm gonna say, okay. Whether it and show whether it ties, the general ledger balance or not. And then lastly, I just want flux analysis here. So flux analysis. So, a period and it's totally okay if you misspell to agent. I do it all the time. It's pretty smart. It'll figure it out. So, okay. A period over period period over period, variance report variance report for the PNL with commentary boxes on each line. And, you know, I wanna make sure that this looks good. So I'm just gonna say, you know, preload, preload realistic mock data, and give me a clean professional design. And then I'm gonna go ahead and just hit enter. So this is pretty specific because I really thought about what I wanted to build, thanks to Moe. And, you know, I'm not in accounting. So to me, this to me is a little bit a little bit of a mystery. But when you're when you're approaching the tool, I want you to really think about, you know, what you wanna build as broadly as you want, and then you can always whittle it down even further as you continue to go. So I could have just started off with, like, build me an account, you know, closing management tool and then added these three, panes or the three views separately. But now that I've done this, what agent is gonna do is create a plan and then actually act on that plan to create an application. And I kinda wanna walk you through, what we're looking at here, while this takes the time to build. So this will take about two to three minutes to build depending on the complexity of what we're building. That could also vary. But here what we see in the center is what we call, like, the canvas. So this is essentially everything that you build essentially will end up here. This is where you'll be able to iterate on designs, kind of create small tweaks here and there, and you'll be able to see everything here on the Canvas. As you can see, this is currently being built out here. On the left is where we have the interactive portion where we're actually, like, speaking with the agent. So this is where I would continue to build. I can also upload files, attach Figma designs. I could go into plan mode. So this is that collaborative aspect that I talked about last time where I was saying, hey. You know, if you have a question, go ahead and go into plan mode. What this does essentially is that this is basically, like, not producing code. So if I switch out of plan mode, I'm producing code. So, I wanna make sure that, you know, I just want my questions answered or I want a recommendation, I would switch into plan mode, and I just wanna be chatting with the agent, not necessarily actually producing code. Here, we have a couple of different agent modes. So these are something that you can toggle between depending on the task that you're doing. You can go into, light mode if you're just gonna make a quick change to, like, let's say, button, or you could go into autonomous mode, either economy or power, depending on, the the speed that you want. And you can change, whether or not you want app testing on or off. If you have it on, it takes a little bit longer. For the purposes of this demo, I'm gonna turn it off just so it's a little bit quicker. And here we have some things happening. Hey, Okay. Diego. We got a couple of questions in the chat. If. you're okay, we'll just cover a few. And then, really excited to see what you built here. The first one is, why Replit and not directly use Clawd, ChatGPT, or another tool? Yeah. It's a good question. So with Replit, Replit is really designed for, like, a nontechnical user. So a lot of the times, Claude, Cloud Code or, you know, something like Cursor is great for someone who is very, very technically adept. Right? And they can go into an IDE, and then they can build a tool. But if you don't have a lot of experience in coding but you still wanna be able to create solutions, Replit is gonna be the best answer for that because you can actually make these things using natural language. That being said, we do have the power of using, you know, all those frontier models. So we really invest a lot of our a a lot of our we we we invest a lot in essentially deciding which models are best at what. So, you know, if Gemini is better at front ends, we'll use Gemini to do our front ends. We'll do something like Opus to do our back ends. Right? So the agent is a really powerful, think of it as, an orchestration system, kind of firing models off here and there. So we're actually getting, like, really, really solid performance and getting to take advantage of, what each model does best and not just being kind of, like, siloed with, you know, just Anthropix, Claude. Super helpful. And just also personally, like, I really like Replit because it hosts the app for me, where. when I'm using the other ones, I have to go, like, find a third party system to host it. Replit also, I found to be the best in building into APIs. So an MCP, a model context protocol, I found is great for, like, having it pull, like, a generic question, but, like, a deeper integration, like what I did for my cash flow forecast. I think Replit does a really good job at building on top of the Campfire APIs. So I think it's just, like, better for, like, large volumes of of data back and forth. It's just in my own use case in addition to what you said. One other quick question is and and I think I might have heard it in there, but just for the group, is a code of apps created in Repli downloadable. Yeah. So you could actually go ahead and download this entire thing. So here, we kinda have a finished version of this application, kind of the first iteration. But if you click on this button here and you look at your file tree, you can actually see this is creating real code. This is with the React front end and Express back end, but we can work with any language. But if you go to these three dots here, you could download this as a ZIP, or you could go ahead and just hook this up to, like, you know, like, a GitHub or something like that if you if you're familiar with that kind of tooling. Cool. Amazing. I'll turn it back over to you. Really excited to see what you built. Awesome. Okay. So one thing that we recently launched which has made Replit really, really powerful is, the idea that you can work at you can work on multiple things at the same time. So before our agent four launch, we would essentially have to write one of these things at a time. So I would write something, and then I would wait. And then I would write something, and then I would wait for it to complete. We have really recently launched something called parallelism where we can actually work on multiple things at once. So if we look here, I can actually create, like, an entirely new task that can be working in parallel with something that I have going on with this main version without affecting it until I want to to actually merge. And what's great about this tooling is that, essentially, I can actually go ahead and create different artifacts. So let's say that in an entirely new thread, I wanna create this same app but a mobile version of it. So I'm gonna say something like, create, also create a mobile version of this app, And I'm gonna go ahead and send that. So that's gonna be happening in this separate thread, but here I have my main version here. And, again, I don't know much about accounting, but this looks pretty good to me. It looks like I can look at some reconciliations, some flux analysis. But if I wanted to take this a step further from the things that Moe was describing, what if I wanted to, you know, add, some customizations, right, to try to customize for my specific problems? I'm gonna go ahead and, you know, add a settings page add a settings page, where you can where you can manage, team members manage team members, the fluctuations thresholds either in percents, or dollars. K. And I'm gonna go ahead and send that off. So if you notice, this is working, and also this is working. So we have two of these things happening in parallel. I'm gonna be creating a mobile app in the background, and I'm going to be actually working on my main application here that I have. If I wanted to actually invite someone to this workspace, I'd be able to do that. I'd be able to actually hit invite, and I can axe I can add a a coworker. It's gonna let random coworkers here. Go ahead and invite this person and invite a couple of other field engineers to this workspace, and I would actually be able to see them working here in real time. And we'll be able to actually create some collaborative, a collaborative workflow here. So it's really, really great for that. I also wanted to kinda showcase that we do actually allow for publishing. Right? So we take care of everything. And I know this was a question in the chat. So let's say that I'm happy with the way that this looks. I can actually go ahead and publish this by clicking on publish. I can choose, you know, what I want the domain to be called. And then depending on the plan that I have, I can actually change who I want to show this to. So either just people in my workspace, I wanna publish this to the entire world, or I wanna put it behind, a password. So we take care of all of this for you. You don't have to figure out how you're gonna actually, like, host something like this. We take care of that for you. I'm here in Canvas. I think you. just covered one in the chat, but it's about when multiple folks are coding together. We. obviously saw you show that. There was kind of a a deeper question on that, which, like, can you can you see which code came from which user? Sounds like yes, but I just wanna confirm. Yeah. So if someone were to open up, like, a, a task here, you'd be able to see planned by so and so here. So you'd be able to actually see, like, who's doing what. And then you can actually, kind of approve things this way. So if I say, like, okay. Start building. It didn't just go and build it. I have to go in and kind of, like, approve it first, before it actually just jumps right into, like, creating the actual feature. And. then I can take a look at everything that's happening with the task board here. So I can see, you know, what's actually active, what's done, what's, like, been archived, all that from this, task board here. So this main version is still working. Another great thing that has recently launched with agent four is this Canvas. So before, we didn't have this, like, workspace that we have here. This is great for design. So let's say that you are trying to work on a, you know, maybe a different view of an application like this. Like, let's say I didn't like this or I wanted a dark mode. If I click reimagine here and I say, also add a dark mode to the canvas, I can actually create multiple iterations of the same thing and just compare them side by side to see what I like best, and then I can go ahead and commit to that or integrate it into my main application once I'm finished there. So we'll actually see another one pop up here on the side for for for comparison here. So it's going to also add a toggle. Looks like it's going to give me the ability to switch back and forth between dark mode and light mode. Let's take a look at mobile. So, it looks like mobile is working. yeah, we've got one question around, can it pull from multiple data sources to build the app? So maybe it's not just Campfire's ERP, but also, like, a CRM or another tool. Yeah. It's a good question. So let's say right now, I'm just working with, kinda like dummy data. Right? But let's say that I actually wanted to connect to some real resources. I have an integrations tab that I could go to here, and these are some of, like, the native connectors. So depending on the plan that you have, you can connect to different data sources, different resources here. So I can connect to Google Sheets. I can connect to something like Snowflake, Databricks. All of that kind of exists here on this page. But if you wanna connect to something that you don't see here, it's not like a native connector. One thing that I have found to be very, very successful is if I have an API to, like you know, this if I if I have an API, I would need an API key. Then, essentially, all I would have to do is, you know, put that into my secrets manager. So I can go into my secrets manager, store my key here, and then give the replet agent the docs. I can just go to the website of, you know, who or whosoever API I'm using, copy and paste the docs to the agent, and the agent will be able to figure out exactly how to connect to, to that endpoint. So you can pull from a bunch of different places, to create, like a like a supercenter, like a hub essentially, dashboard. Yeah. And just to chime in here, yeah, I I don't know all the different tabs. I literally just talked to agent, and I'm like, what do I do? Like, teach me, like, on five, and it tells me what to do. So it's doesn't you don't need to be technical on going to different tabs and. figuring out how it'll tell you what to. do. And and instead of going in that's a good point. Instead of going here into, like, this, you know, g g sheet, tab here, if because I maybe I just don't know what I don't know. Right? I don't know, like, to to look here. This is a really great place to just start talking to the agent and asking the agent to do things for you. So I can say something like, can you establish, a Google Sheet a Google Sheet connection so, people can link their reconciliations and balance from the linked sheet and compare to the balance from, like, let's say, the e ERP. Okay. So let's say that I'm just throwing this at the agent. Right? Because it's just essentially, like, a a broad overview of what I wanna do, but I don't know if I can connect to something. As you can see, like, it's checking for a Google Sheets integration. So it's actually gonna be able to do a a lot of this work for you without having you to without having the user be too knowledgeable about what's available and what's not available. It'll definitely guide you in that direction. So it's working through this. It looks like it says that, hey. You're already authorized to do this because, I am, but, it's gonna go ahead and actually set that up for me, and then we can kinda take a look at that in a second. Let's check on our mobile app for now. Cool. Looks like this is still working. We get this nice, pretty bezel. And then the great thing about working with this, the the mobile application is that we can actually test it with ExpoGo. So if you have that app and you were to, like, scan this, would actually be able to see this on your phone right now. So if, you know, you're working from from, you know, your phone, you'd be able to actually work through this app because if you're using the same database, essentially. So gives you a of flexibility there, and, you know, you can kind of create whatever workflow you want, either mobile or, either on the desktop or both. This is still work. cool. Moe's going through the close while he's, on the road, on the. mobile app there. We got one question about security, particularly for those on the enterprise. And, of course, it's very sensitive data. It's financial data or your comment earlier about the sales commission tool. Then you've got maybe some employee, salary data. How do we, you know, ensure the data is not available on the web? Can you put Okta in front of it for SSO? Do you have any you wanna share from a security standpoint? Yeah. There's a couple of things that we do to kind of address this. So so one is how you publish. Right? So if you publish, someone who is, you know, on an enterprise plan, their admin or, like, their IT team can basically ban public application public apps. So we can't deploy to the worldwide web. We could only deploy, to our workspace. That means that anyone who is basically behind our SSO will be able to access this application and its information. So, that's kind of like our first line of defense there. Right? We actually can toggle these on or off so your information is protected. And then the second one is we do have a security scanner that can be enforced to be turned on. So every time someone publishes, this security scanner will run, and it looks for a couple of things. So one, it's gonna look for vulnerabilities, like package vulnerabilities, and it's going to fail any deployment until those are fixed. And then it's gonna look for sensitive data, like, you have, like, an API key, if you have something, you know, that shouldn't be in the code, it'll go ahead and and fail the the publishing here. And it'll this will also be reported back to, like, any admin here. So this is another way that we kind of address that issue. Yeah. And for my app, I I set a password so that no one only counting personnel can actually access the closed app. So even if a rep lead user rep lead employees had access to my own website, they wouldn't be able to get in. Yeah. And you've got very large enterprises using Repli. Right? So there's. been some, like, intense security reviews and, you know, operating in very large companies today. Yeah. We have, we work with some of, like, the biggest companies ever, and we're making sure that we're setting up kind of their their instance in a way that'll scale so that they can kinda roll this out more broadly without having to worry too much about, you know, any sensitive data that they may have or putting data in the wrong hands. We also have, you know, role based access controls. So people who should be seeing things are the right people, and we kind of break people out into groups that way too as well, and giving them access to specific things while others not. And we've got another question about, how the team can access it. So if I create an app for my team to use, would they also need a Replit license to. use the functionality of the app? Or can I just be a builder and just have my one license and then publish the app for the team, and then they don't need to have a Replit license? So maybe just clarify, like, who needs a Replit license and and who doesn't, as, like, a user of. the app versus, like, an actual builder of the app? So licensing works, kind of in in in a general, like, way where we break people out into different types of roles. So we'll have, like, a member, which is kinda like a builder, someone who can create, edit applications, and that would require a license. But then we also give out, like, viewer seats essentially. So people who and and people who kind of, like, come in to just kind of consume the application. So maybe someone on accounting doesn't wanna, like, actually build this tool, but, like, that's gonna be very, very useful, and I built it for that team. Right? And they're gonna be kind of, like, on the front end of it, and they're not gonna kind of, like, look at what's happening here on the screen with the agent. It's it'll it'll just look like an app to them, and that's, like, kinda like a viewer license. And that, that is definitely a little bit different, than than the member license. Perfect. Thank you. Okay. Looks like we're working hard over here. We're working hard on the mobile side as well. Yeah. We have a lot going on here. Let's take. a look at our Canvas. Yeah. Let's let's poke through let's poke through the app and see what we can do better. Alright. So looks like this part just finished. That's perfect timing. So it looks like we have, a closed checklist. Looks like we have an overall progress bar. Let's go to my settings page. So this is something that I added just recently. If you remember, I can add a member, give a full name, say, like, Moe, Moe at Moe dot com, and I can just say something like this. Go ahead and add this person. I can change a flux thresholds, percentage only, dollar amount. Let's do percentage. On a moment, you tell me what's, what's a good percentage threshold here since you're in a like, Good time. is that 10 in? time is good. Let's do 10. Okay. And then, we kinda can leave it that way. And then if we go back to maybe our closed checklist, we can kinda take a look at, everything at, like, a high level. So this is just basically, like, how I'm progressing through, this kind of, like, month end close. Yeah. But because something I learned as I was building Mhmm. was the difference between development mode and, like, published mode because I think a lot of changes that you do, that you see that you're working towards, and then you actually publish those changes, and the end user will see them. So if you can walk through that kind of difference because you'll see some sometimes something different on the preview versus what's actually published. The published version is, like, what you're actually using and deploying. Right? Yeah. So, basically, once I publish this, if I go ahead and publish this and let's say that I wanna publish this maybe I'll just do it, like, to my workspace only. And I'm gonna go ahead and publish it. A couple of things are gonna happening are gonna happen. So one, it's gonna provision. It'll do my security scan. It'll do the build. And then I'll be able to actually see kind of, like, a website essentially, and I won't be able to see, like, any of the canvas. I won't be able to see any of the chat. It's just for those people who are gonna be using the tool, and consuming the application or or think of it as, like, someone just going to a website and using a software, but they're not have they're not influencing the build of it at all of it at all. Looks like it's kinda finishing up here. So I think by publishing it here, all that data will be gone. Right? Because it'll just be a clean slate. Like, there will be no demo or dummy data. Yeah. So, we do give you a we give you a development database that you'll see here, and then we give you a production, database. You are given the option to, like, copy your dev into your prod database if you would like to do that. But, yes, essentially, the normal, like, by default, like, workflow that you'll see is you'll have a development work database, but then you'll have, like, a production database, and then that one will be more of a of a clean start if you if you do not select to, like, copy one to the other. And you can kinda take a look. This also doesn't have any tables here. There's, like, no data here, but this will normally give you, like, a high level overview. It'll kinda look like an an Excel spreadsheets, but it'll be a Postgres database. Let's take a look at we got a a few questions coming in around, like, cost. And so I know you've got pricing on the website, but anything you wanna share about, like, as is it, like, usage based? Is it, like, a fixed, like, daily reset? I know in an AI world, there's, like, lots of pricing models. Just at a very high level for the group, like, how does it work? Yeah. So, it depends kind of, like, how you approach it. Like, if you approach it from an enterprise perspective, you'd get in contact with our team, and then kind of have that discussion. When it comes to, like, how to manage costs in terms of, like, using the application, it's all effort based. So if I have a very complex task, I will essentially, it 'll be more of an expensive operation. Right? So as opposed to, like, changing the color of a button versus, you know, doing an entirely new feature, it'll be it'll be a little bit more expensive that way. The things that kind of, like, increase cost too are, like, app testing. You know, basically, the more time and more effort that the agent has to be spent doing something, it'll, like, run up the the credit cost essentially. Okay. Super helpful. Yeah. And for those, like, you can check out on the website. I know there's there's a lot of detail there about how it works as well. I know there's, you know, more questions around, like, security and confidential data and PII and one from Crina. You know, if you're not on an enterprise plan, you know, if you wanna talk through a little bit, it sounds like the enterprise plan is gonna provide more more security or more kinda maybe single sign on. But, Mhmm. how do you draw the line between using, like, public API tools as opposed to enterprise plans or paid production API keys? Anything you wanna share about like, for for those using work data, of. course, go to your Intosec team and, like, get approval and and get the get Replic Blast. But then, like, I guess, question of it's do you recommend, like, a certain tier for folks from a security standpoint if it's work financial. if it's into the financial data at work? Yeah. So, if your company requires something like SSO, it would have to be enterprise. It's only offered on the enterprise plan. So, that's, like, a pretty, straightforward kind of, like, threshold right there. And then on the enterprise plan, we also we have, like, a no training policy. So, like, nothing that you put into, like, the agent. Like, we're like, we're partnered with, you know, all of these models. Nothing is going to be used to train on your actual data and on on the enterprise plan. And then the other things that I mentioned also was, like, the, like, the security scanning, kind of, like, toggling on and off all of the publishing. You could really lock down, the environment, so that, you know, you and your, like, you know, IT team can kinda, like, rest easily. Super helpful. Mhmm. Where is the database stored? Maybe folks are joining from around the world. Is. there, like, data sovereignty? Is there it's kind of a single spawn. Maybe that's a a certain tier as well or anything you wanna share. Yeah. Yeah. So, I mean, we do have options, like, again, depending on the plan. But in general, it'll just be like, we'll host it. All USA, we host, you know, Replit will host, like, your database. Okay. Cool. Oh, right. And then I guess question for Moe. Are you, like, automating journal like, are you pushing anything back? It sounds like it's more of in a read only state where you're doing all of the closed workflows and approvals today. Or the there was a question earlier that maybe more broadly for either of you, like, what's, a very complicated app or kinda how far should you should you take it? I know in the beginning, you talked through here is, like, internal apps and certain use cases. Do. you see folks building very sophisticated apps or anything you wanna acknowledge there for Rose, but most specifically is what you've done and then Diego more broadly. Yeah. So for now, I'm just using it as one way, you know, getting Campfire data and using it internally and not pushing using it as an agent to help us with journal entries. We're lucky to be on Campfire, which is a more AI focused ERP that has functionality that, otherwise, I would build if I was on a NetSuite where, you know, I'm suggesting accruals and such like, having kind of parsing the transaction level data and making recommendations based on that. So, yeah, if we were on a NetSuite, I definitely would be looking to leverage something more modern. And yeah. So I haven't had the need to. do that just. yet. And then, Diego, more broadly, is there, like, a you know, the question was, like, is there a limit or, like, how far can I go? I mean, it looks like if we built this in twenty minutes, it sounds like twenty hours is there's a lot you can do here. so much you can do. I would I would challenge you to push this as far as you can. Sometimes, I think, like, the agent can't do something, and then it, like, completely blows me away. If you wanted to write back to a certain data source, you certainly could. You just have to make sure you have the permission to do it. So these can go far beyond just, like, read only dashboards. They can go back to, like, writing back to certain data sources, doing very, very complex automations and tasks. It's just basically, like, what your kind of, like, IT team or your your company would allow you to do. But, like, even if you're working on a personal project, I've seen people take push this really, really far and then even start, like, side businesses with with Replit. I recently went to an event where I an event where I saw a lot of people kind of creating, like, their versions of, like, you know, opened OpenTable or something like that for, like, their own hometowns, like, in Brazil or something like that where maybe, you know, that that that type of service isn't as popular, but it is a really big need for it. You know, small versions of this, basically, I would say that's that's what I've seen, like, on a personal use. People are really pushing it, but it also it also just depends, like, what your company lets you do. Amazing. And, yeah, if you are if you are building, like, a side commission role or anything on the side, probably check your employment agreement. Maybe don't use your workplace Replen. account or use your work machine. If you're if you're building apps on the side, just obviously be very careful of of all of that. And there was a question for for Campfire. Is Campfire automating accounting entries for approval to shore up accruals? Yeah. We actually have our own accrual subledger. Campfire AI can auto draft, accruals for you. It'll, you know, look through, approved POs that haven't had AP. It'll look through contracts that maybe, renewed, but no invoice has been issued yet. All sorts of accruals, full fully automated, or you can put it into an approval state, within Campfire. There was a specific question. Could you clarify the workspace only deployment? Where exactly does it get deployed if it's a workspace only? Basically, what that refers to is, like, who is gonna be able to access this application. So anyone who is basically, invited to the Replit workspace. So anyone who is, like, getting behind SSO or has, been invited to your app your your Replit kind of, like, instance will be able to use the application, but nobody outside of the organization would be able to. K. Amazing. Mhmm. And then more more broadly, like, build versus buy, you know, I guess maybe this is for Moe. Obviously, you're on Campfire, but you've kinda built some apps on top of Campfire. Is there, like, a maybe you you looked at some tools in the market for some of the things you mentioned, but, like, you're like, hey. We we want a version of of it that's, like, very specific to us. Or I'm happy to to give my answer after you, but I'd love to hear your thoughts. Yeah. Like, was it a cost savings? You guys are obviously very well funded. Is it was it cost savings? Was it was it more about, just we want this built for Moe? We have a very specific needs. Like, anything you wanna share on. build versus buy framework without me maybe without naming specific vendors you looked at or will be, Yeah. For sure. but, just just broad. context. That's the question everyone probably should be asking is, like, why isn't Replink build Replink building their own ERP? Like, why are we using Campfire? And it obviously comes down to the priorities and the time and what we wanna focus on. I can spend all day building the best closed tool, but but, ultimately, I need to close the books, and the team needs to focus on close the books. So there's definitely that, you know, evaluation of, you know, how much time this is gonna take us. Is it better to better use of our time and money to just purchase a point solution that will help us get what we need to, you know, do our objectives. And why I built the the closed checklist app is that I felt that there was nothing there in the market that met my needs from a full closed solution, and it was a relatively simple build that I couldn't maintain. So, yeah, we're we're always evaluating time, resources, costs, priorities, and then how we what we buy code versus what we purchase that's already out there. Cool. How much data can it take without breaking? And will it increase in data size we work with impact the speed of the apps we built? So I guess, is there any sort of, like, latent latency or deterioration of performance if it has a lot of data? So we, so there's a couple of things that you can do to kind of tackle this issue if it if it arises. So so one is we do give you the ability to when you publish, you can kind of configure the machine that you're using, or is it just setting this. Let me actually republish here. Or wait. Hold on. So I can actually take a look at, like, the usage that I'm having. Maybe it's best if I actually go here and shut down the deployment and then show you from the beginning how this would work. So I would go here to settings, and then I'd be able to actually, like, configure my machine, to kind of make up for any, you know, power that may be lacking, so to speak, and actually be able to, like, actually configure this to what I'm expecting. And then also too, if you really wanna take it to, like, this level, like this like, take it to, like, the Galaxy if you'd like to, you can always take this out of Replit and, like, self host it yourself if you'd like to. We make that pretty easy. We don't lock you into Replit. You can create something in Replit and completely take it outside of Replit to create it through GitHub or download the the the zip file. But we give you multiple options. So you can keep it in Replit, and we can certainly handle tons of traffic. And then we give you the ability to configure to configure the machine, or you can take it out of Replit if you decide. And it sounds like people have, like, huge datasets in mind that they're gonna. that they're gonna load into. Replit, Yeah. which is which is awesome. It sounds like folks are thinking big. I love it. This one, I guess, more for Campfire. How is Campfire managing API permissions and the Replit integration? Maybe one accountant should be allowed to only read vendor tables in Replit, but two accounts should be allowed to update. So I guess read versus write and how we think of and I think just just more broadly, when you're creating an API key or when you like, you, of course, have to authorize Replit access, and so you need to, like, have the the proper permissioning to do so. In Campfire, in the settings, there's a way of creating an API key, and we can, we can restrict, users to so they in this case, each of the accountants would probably have their own API key, and we would set, is it a read only key, is it a write key? And then as they build, maybe they're restricted to their respective key, and their key has its own, permissions. And then maybe one accountant should no longer have any, access at all, then you would kinda revoke or update their their API access at a at a user level. That would be my approach. But, Diego, anything you wanna add from kinda managing, I guess, data data pipelines in and out of Replit? One thing that I will say is that we're always we're working on ways to kind of lock this down, you know, more and more every single day. So the way that we have it right now is, you know, if if an admin doesn't really want you to have access to, like, a specific connector, right, we we can actually do that. But right now, what the way that it works is that with Replit, if you try to use, like, a a a connector, right, like an integration, we will honor whatever rules, I guess, so to speak, or guidelines are on that side. Right? So if you, let's say, are trying to connect to, a database, right, like a vendor database, and then in that system, you only have read access to certain tables that will be honored. Okay. Amazing. And I know we got some great we got we got five minutes left, or just under that. We got, a few few more questions, but keep the questions coming, folks. I mean, it seems like there's lot of enthusiasm. Maybe. it's getting a little quieter because folks are vibing in Replit. They they took that QR code, and they're building. I I think going circling back to the beginning, I know, Max, you had said you wanna build a simple inventory landing tool with an interface for factory users to search for POs, book against goods not invoiced, and raw material accounts. Max, hopefully, hopefully, we're feeling inspired. Hopefully, we're ready. to just go go, fire up our Replit account, probably drop that query literally into Replit, and then and then start going. I am going to look at any unanswered questions at this time. Yeah. I think we've covered a lot of these, though. I see one that I that I I I kinda. wanna touch on. It's can I can I explain how I was able to achieve this build? Like, what connections they already have? I didn't have anything. So that's the great part is I really truly started from scratch. There was nothing really that I had set up. I just kind of went with it. I don't even know much about accounting. So a lot of it really felt like, like, really strange to me, like, like, the flux analysis, all of that. But the agent is so powerful, and and it knows what it needs to know when I say, you know, flux analysis. So, I just kind of started really broad, and then I just started to whittle down my problem, slowly, you know, as I started to give more and more prompts. So nothing was set up until I added that Google thing towards the end there, but that wasn't, like, pre pre setup. Granted, you would have to, like, you would probably see, like, a hey. Like, do you want Google you wanna be able to connect to Google? And it'll you'll just say, like, you'll you'll just click, like, yes, and then that's kind of it. Yeah. Awesome. One from Morgan. Are the app connectors in the integration tab API connections or MCP servers? It's a great one. Yeah. So they're API connections, but we do have so I guess it's both. Right? So some of them are API connections, but we do have, like, a connection with, like, Figma's MCP server. Right? So it kinda just depends on, like, how you're working with the integration, but we also allow for custom MCP. So, it'll kinda give you a lot of power and flexibility there. Yeah. And I would say if it's, like, a a huge amount of data going back and forth consistently and it's structured data, I I actually prefer to to build on the API. If it's like if you think this vendor is a is a law firm, then, you know, do axe, and it's more, like, contextual and human, then I think the MCP is a little better. But MCPs do consume a lot of tokens. There's kind of a lot of consumption there. Right? And and they're not as great for, like, huge volumes of data. So the version that I that showed earlier that was built on top of Replen, it was pulling Campfire data in via API. And I think that's the way it can pull in just large volumes of data in a more kind of streamlined data structure that it's a bit more deterministic where, like, kind of kind of having the MCP go wander in the Campfire environment and look for stuff is a bit more probabilistic. So it just that's that's my mental model for each of the two tasks. I know we have just under a minute. I wanna send everybody to the chat. In the chat, we put a link for it's a it's just a huge thank you for joining us today. We've got a replic code that, expires at the April. And go in there, click the link, replit.com forward slash sign up, and the coupon is replit camp. And you can get started for a free month of of Replit today. And on next week's session, I would love to kinda hear what everybody built with Replit. Reach out to any of us directly. Just wanna thank any any closing words from Moe and Diego as we wrap up? I just wanna say thanks for having me. This was this was great. And, hopefully, you feel a little bit inspired to be able to actually, you know, create a solution. So think about what's been bothering you, what's been taking up a lot of your day, and, figure out a way to solve it because, that's certainly, like, what we're able to do with Replit now that we have this tool. Amazing. Well, thank you. Thank you. both. For sure. honored to have you as, a customer. guys. We're honored to be a Replit customer, and I know what I'm doing this weekend. I'm gonna be building in Replit. Thanks, everybody. Have a wonderful day. Thank you.