<response />
Jump into office hours. Tuesdays are beginner sessions with a 15-minute presentation followed by 45 minutes of Q&A. All sessions are recorded as VODs. Ask anything — the community will help.
AMA archive
Complete AMA archive
Every question, in context.
Search the full record by question, response, or topic, then expand any row to keep reading in place.
106 questions in view
<response />
Yes. Switching models retains all project context. The new model picks up the full history and understands the app.
<response />
Build a new app — custom login is only for new apps. Go to Settings > Authentication. If you have access, there will be a blue banner at the top. Then prompt: Please implement custom login with the theme of this app.
<response />
Sam could not give a date. He has access internally and loves it, but has seen nothing about a public release timeline.
<response />
Not natively. Best workaround: load as much context as you want into view, then use Ctrl+F in the browser to search within it.
<response />
Base44 is a no-code builder first. SEO and GEO tooling has improved massively in 2 months and keeps improving. Open graph customisation is coming soon. But it will not replace marketing specialists — people specialise in these fields for good reason. Use Base44 as a strong baseline, not a substitute.
<response />
Not possible. Even if it were technically feasible, the token cost of applying that contextual rule internally would make it completely unviable. It is not on the roadmap.
<response />
Yes. The app belongs to you. Base44 does not own it. The legal wording is in the Terms of Service. This is how businesses can be built and operated on the platform.
<response />
Base44 secures data at the infrastructure level and adheres to relevant legislation. But app-level security is entirely your responsibility. If you misconfigure access controls or leave your app open, your data is exposed. Build security properly and it is secure.
<response />
No — one account per person. It is in the Terms of Service. If you are hitting a limit or getting told to create another account, open a support ticket and ask for technical help rather than creating a second account.
<response />
You are in the right place. Office hours run every Tuesday, Wednesday, and Thursday at the same time. All past sessions are available as VODs. Jump into any session and ask anything — the community and staff will help. Just start.
<response />
Yes. Switching models retains all context. The new model picks up the full history of your project and previous conversation.
<response />
In the prompt window, click the cog icon in the bottom left next to the plus. Select AI Model, switch from Automatic to Manual, and choose your model from the list.
<response />
AI hallucinations happen — the model selected by Automatic may not be the right one for your use case. Fix it by switching off Automatic and manually picking a model. Opus 4.7 is the best overall. GPT-5.5 is a strong second. Pick one and stick with it.
<response />
Effectively infinite. There is no overall storage cap. The only limit is 50MB per individual file upload at one time.
<response />
Probably yes — similar rules likely apply.
<response />
Wait for the Lily and Tom UX special coming next week. Sam has done design sessions in the past and they are available as VODs, but the dedicated UX session will walk you through it properly.
<response />
Not confirmed as public at the time of this session. It is live at least for staff. Sam urged not to assume it is available to all users yet.
<response />
Use sprite sheets or external asset libraries for visuals. Discuss improvements with your chat in discuss mode. Once Super Agents building apps is public, you will be able to connect an agent to your game and have it run the improvement prompts for you.
<response />
Use an NPM library to convert the PDF to a flat image first, then use an LLM to look at that image, identify the photograph within it, and crop it out. That approach avoids the heavy token cost of parsing PDFs directly.
<response />
Sam confirmed there is a method they have gone over in past sessions. For now, the best path is to wait for the Lily and Tom UX special which covers this in depth.
<response />
Stop re-entering the same prompt. Change your LLM, switch from text to screenshots — circle the element, draw an arrow, explain it visually. Send a picture of the device you are designing for and its resolution. If needed, step away for two hours and come back fresh with a different angle.
<response />
A basic CRM is so one-shotable with Plan Mode that a live demo would not show anything new. Just drop the idea into Plan Mode and it builds itself. Not worth a dedicated walkthrough.
<response />
Nothing, actually — one of the few days at Base44 where Sam had not built anything. The session was last-minute with no prepared demo.
<response />
Effectively infinite. There is no overall storage cap. The only limit is 50MB per individual file upload at one time.
<response />
Yes. Use ElevenLabs or any voice interpretation API. Prompt your app to integrate it for voice input and command handling.
<response />
Ionos cold-calls customers using domain registration contact details. Their opt-in checkboxes are reversed by default — easy to accidentally subscribe. They will call repeatedly until you explicitly ask them to stop. Just hang up.
<response />
Yes, at least in staff and beta. You can connect a Super Agent to your app and describe the improvements you want — the agent runs the build prompts for you, acting as a coding co-pilot.
<response />
Yes. Plan Mode already exists in the Superagent. It is coming to the app builder soon and will be the same cost as discuss mode — very cheap to use. You chat through the feature plan with the AI before any build starts.
<response />
Not currently with a keyboard shortcut. The split-screen code editor exists but text wrapping is not built in. You could build the interface yourself within an app, but it is not a native feature.
<response />
Gemini 3.1 Pro: best for games and Google integrations. Sonnet 4.6: cheap all-rounder. GPT-5.4: fast, cheap, good coder. Opus 4.7: best overall, most expensive. GPT-5.5: near-Opus quality at similar cost. Avoid Opus 4.6 — no meaningful advantage over 4.7 at a lower price. Automatic AI selection will route you sensibly, but manual selection gives you control.
<response />
You are asking it to do too much at once. LLMs have token and context limits, and most critically, poor short-term memory. By step three of a 20-step plan, it has likely forgotten five of the earlier steps. Chunk your build into smaller focused prompts instead.
<response />
Right-click anywhere on the page > Inspect. Go to the Network tab — ignore the HTML. Refresh the page. Do the broken thing. You will see red lines. Click one and read the error. Paste it directly into Base44 chat. That error tells the AI exactly what is failing.
<response />
Always debug with the network console open. F12 on Windows, or right-click > Inspect > Network. Reproduce the broken action. You will get red or purple error lines with the exact failure reason. Paste that error into your prompt — not a vague description. That is the only reliable debugging method.
<response />
Yes, fully supported. Publish each app to a different subdomain of the same root domain.
<response />
Custom login lets you build fully customised login and sign-up screens. No more plain white rectangle with a Google sign-in button — you design it to match your app entirely.
<response />
Build a new app (custom login is new-apps only). Then go to Settings > Authentication. If you have access, there will be a blue banner at the top telling you. Then just prompt: Please implement custom login with the theme of this app.
<response />
Very likely not one that ticks all your boxes. The beauty of Base44 is that trial-and-learning is easy and fun. You can probably make a working version in one prompt. Search for game generation videos on Base44 on YouTube as a starting point.
<response />
Zlatan. The only acceptable answer.
<response />
Everything is possible with Base44. Use sprite sheets for visual quality or implement a 3D library via external API. Out of the box, definitely doable — Sam has built many games on Base44.
<response />
Use the Google Maps API. Start with: I want to integrate the Google Maps API — in your prompt window. Base44 handles the implementation from there.
<response />
Yes — it will be on YouTube.
<response />
A Herman Miller. He showed it on camera.
<response />
Yes — this was the first session recorded live on YouTube. All sessions going forward will be available there.
<response />
A programmable human being in a chair. Example: a Super Agent that checks your portfolio every 15 minutes, sends WhatsApp updates, and tells you where to diversify. Think of it as a schedulable employee. A full session on this ran the previous Thursday.
<response />
As a Base44 employee, Sam cannot recommend specific partners. Partners are listed in the Discord with light blue names. Multiple price points — find one that suits your budget.
<response />
Do not ask it to directly send a PDF — it breaks around 80% of the time. Instead: generate a fancy HTML page, convert that to PDF, then send the resulting file. More reliable and looks far better.
<response />
Yes, if hooked up to a live portfolio API. Sam demonstrated creating a scheduled hourly automation that emails a PDF report on portfolio ups and downs. Set an end date to cap it.
<response />
It does not — the data is seeded and fake. The agent was lying when it claimed prices came from NASDAQ. If you have not connected a live API, the data is not real.
<response />
You are not limited to on or off. Multiple states can coexist — just add different state fields to your entity and handle the logic from there. No more complicated than two states.
<response />
Apps with login required can be gated behind a Stripe subscription page. When a user hits the gate, they see a subscribe button that takes them to Stripe. Post-subscription, they are redirected back into the app. One or two prompts to implement end-to-end.
<response />
Go to Publish then Mobile App. Steps: scan the app, build the app files, correct any build errors, then submit. There's a full walkthrough guide linked from that screen.
<response />
Personal design vision. When Sam heard stock control app with agent interface, he pictured a crypto tracker with a hackery terminal feel. The original requester wanted a warehouse system. Both are valid interpretations.
<response />
Something with a green and black logo — not Whisper Flow, which Sam had used in the past. He could not remember the name live.
<response />
No — it's optional. Plan mode or direct prompting works fine. The tool just gives you the best shot at a non-AI-looking design out of the box.
<response />
Not in this session — Base44 has guardrails against crypto and financial instruments. Could be done with a real external API on a separate project.
<response />
It's doable but was voted out this session. It'll likely come back in a future Build With Us session.
<response />
Duolingo for prompting, a Base44 chess app, and a stock control app with an agent interface. The stock control app won the community vote.
<response />
It was already at max on Sam's end. Likely a local mute issue on the viewer's side.
<response />
Base44 is moving to multi-streaming across YouTube, Twitch, X, and Discord simultaneously. Audiences on different platforms can all tune in.
<response />
That's a good question touching on the limits of AI. As your app grows so does the complexity of the code. We are working on teaching the AI how to best manage the codebase, and as models get smarter they get much better at it (Opus has been doing a great job). It might be a good idea to once in a while nudge the AI to perform maintenance on the codebase, allowing it to remain leaner and simpler.
<response />
The RAM we use changes by the hour - we have automatic scaling.
<response />
Base44 isn't HIPAA Compliant at the moment.
<response />
We are planning to introduce data residency in a few weeks, which will allow apps to store their data at a specific Geo location (we will start with EU). We currently do not have a concrete plan to have our app servers in multiple locations because it introduces a new level of complexity. In the future we will decide based on demand.
<response />
Yes, we have backups in place for all of our datastores
<response />
You should be able to build a great POS interface in Base44 today. I don't see any issue in creating a desktop POS with Base44. You can use Stripe or any other payment provider under the hood.
<response />
Yes - you should be able to achieve this by connecting X to B44. Not using our connectors - but as a developer on X - and listen to events there - connect it to a Backend Function on B44.
<response />
Not planned at the moment. The idea is to get you from 0 to a working app very fast. We are looking at expanding the backend offering more - but currently we're focused on higher level value points like more integrations.
<response />
We plan to introduce data storage in EU soon, but hosting and processing is still far because having hosting spread across continents is a new complexity dimension we plan to tackle much later.
<response />
Yes! It might require some prompting - but you can surely do it.
<response />
We expect our mobile app interface to be as stable as the desktop one, though we might need a little time to mature it. Regarding backend - it is the same one, so we expect the same performance and stability.
<response />
We hear your feedback. There might be good changes in this area soon.
<response />
We already have a strong RLS mechanism today that will not allow unauthorized access. We are planning to introduce app multi-tenancy as part of the platform in the future with in-app accounts management and complete segregation between accounts to build commercial SaaS solutions easily. But RLS is the current good answer.
<response />
I'm really sorry to hear about the damage done to your business by our outage. We're now really focused on stability - dealing with the root causes of every incident. We have a team of strong senior developers from companies that built applications at the highest scale. Our Entities store had shared infrastructure with the platform database - this led to many incidents. We've dealt with it by separating apps from the platform and from one another.
<response />
The Base44 CLI is going to be the best companion for your Claude Code. When working with Claude Code, you enjoy all its benefits. But the Base44 CLI gives Claude the best building blocks on the backend: data storage, backend functions, cron jobs, AI agents, connectors, analytics, authentication. All with no setup at all! Just run 'npx skills add base44/skills' and ask Claude to build whatever app you want on top of Base44!
<response />
We are aware of incidents, but the infrastructure separation will help prevent such cases. We will introduce data residency in a few weeks that will allow to store the data of your users in specific locations.
<response />
We are always experimenting and trying to give the best models for the job.
<response />
Custom login is coming really soon, me and another team member are actively working on it. You can already ask Base44 to implement custom login and signup and it will implement your own login/signup form, but only if you configure your app's visibility to Public and turn off Require Login. That way the AI can implement its own login UI and logic. We are working on more improvements in that area.
<response />
There definitely was an Aha moment, maybe even more than one. When the product started with a very small team moving extremely fast, managing all of the core platform and the applications in the same architecture made things easy. But once we started to see that growing usage caused one area of the system to affect other unrelated areas, we understood we created a coupling that wasn't required and was causing operational pains. So from that moment we started focusing on better separation between our platform components.
<response />
We consider introducing a bring your own DB in the near future but have not decided yet. It will not allow frontend only, just control over your DB.
<response />
Yes! It might require some prompting - but you can surely do it.
<response />
Yes you can! We have our security solution for apps data also known as RLS. This allows the AI agent to define access rules so that each user/customer data is separate and cannot be accessed between users. There's no known issue to get to tens of thousands users and more.
<response />
We are always experimenting and trying to give the best models for the job.
<response />
We at Base44 are constantly improving stability and performance. I do think that you can rely on Base44 for business workloads today more than ever, and in a couple of weeks even more. We are now in the process of separating user data from operational data, and we did various improvements while upgrading our infrastructure.
<response />
You can do it in 2 ways: 1. Gmail integration 2. There was a recent feature released in this area letting you send from your email domain.
<response />
Base44 is an independent platform from Wix. Harmony is Wix's flagship product for website building with AI - while Base44 is the state of the art way to build apps. We are planning integrations for Base44 with Wix - so you will be able to use more Wix capabilities within Base44 - but these will stay completely optional as we want Base44 and Wix to continue to run separately.
<response />
We are SOC2 compliant, but it is your responsibility to verify our compliance to your customers' regulation needs.
<response />
With great power comes great responsibility. We have our AI agents working in 'Sandbox' environments, ensuring our builder agents can only perform work we allow it to do, and that any malicious user cannot affect our platform as the AI agent is sandboxed (least privileges principle). For in-app agents, they are also guardrailed to only be able to do what you as the app owner allows them to do.
<response />
We support many integrations already - and the outages of any of them won't affect Base44. It may affect specific apps that rely on the integration in order to work. Wix will be another such integration. In terms of stability - it's very similar to any of the other integrations we're doing.
<response />
You will hear about it soon! Stay tuned. In about 2 weeks.
<response />
For desktop apps - you can use Electron or any other platform together with the Base44's server infrastructure that was released yesterday.
<response />
One of the biggest challenges is handling higher and higher complexity apps. We want to allow you to build any software on Base44, from personal home management apps to complex internal processes management apps for enterprises. These have different requirements, but we want to be the best solution for both. We have to keep improving our AI and infra while making sure work on one end doesn't hurt the other.
<response />
In about 2 weeks - but I'll let the R&D team explain its plans.
<response />
There is currently no additional cost for this. As it is a new feature we will need to monitor how it affects apps and the platform and tackle scalability issues, but we do not foresee such issues.
<response />
Rest assured that we are not going anywhere, but in any case there are features of code and data export you can use.
<response />
We are already working on a lot of new integrations, one of them is Figma. The platform is getting richer every week.
<response />
If you mean scalable backend servers for apps you build on Base44, we are fully focused on serverless solutions like Backend Functions. For our own servers, we auto scale based on traffic and resource usage. If you're using the Github Integration with Base44, you get that by pushing and pulling from your repo. If using the CLI, you'll need to setup your CI/CD workflow yourself.
<response />
Yes - we're dealing with our bottlenecks in a scale out manner - so we can be very scalable without central bottlenecks. Every app gets the full power of the Base44 platform compute. We are already handling an enormous amount of concurrent users, and we are improving our power to support more complex apps and more users all the time.
<response />
We're investigating this direction. It won't be in the next few weeks.
<response />
There are two aspects of stability: 1. New features breaking the platform - we are working hard to prevent this by automatic safeguards, intense manual QA and automated E2E tests which grow every day. We will not slow down in releasing new features - this is our power. 2. General platform stability under load - here we invest a lot of efforts in improvements. We are focused on making Base44 a lot more resilient.
<response />
Not planned at the moment. Maybe if/when AI prices drop significantly.
<response />
This is a great idea - we'll follow up on it internally. No plan for this yet.
<response />
Can you share more about your pain points? We have introduced the 'dev mode' for your apps data so you can easily separate your test data from your production data. You can import data from CSV files, what else can we do to improve that experience?
<response />
Technically you could achieve this today. By connecting multiple domains to the same Base44 app (each a subdomain associated with a customer) and telling the AI that each customer has its own subdomain which acts as the tenant id (and configure security rules accordingly), you can get each customer using their own subdomain with data isolated. But if you need SSO per customer or different auth configs, we don't have solutions for that yet.
<response />
If you mean clone app, it is for cloning the app code and settings, not its data. If you need to copy the data you will need to export from the origin app.
<response />
We consider introducing a bring your own DB in the near future but have not decided yet. It will not allow frontend only, just control over your DB.