Where Does a Base44 App Actually Run? (Full Infrastructure Breakdown)

"I built my app in Base44 and it works perfectly. But where does it actually run? Is it on AWS? Google Cloud? Can I see the servers? And if I export my code, can I run it somewhere else?"

These questions come up constantly from Base44 users who've built something valuable and suddenly realize they don't understand the infrastructure their app depends on. Base44 positions itself as "fully managed" with "built-in hosting," but what does that actually mean? Where does your code execute? What infrastructure do you control? And what happens if you need to migrate?

This guide breaks down Base44's infrastructure architecture using official documentation, technical verification methods, and real-world implications. Whether you're a developer evaluating Base44 for a project or a founder making infrastructure decisions, you'll understand exactly where your Base44 app runs and what that means for your business. For related guidance, see our Base44 hosting overview and prototype to production migration guide.

🎯 Key Insight: Base44 is Platform-as-a-Service (PaaS), not "your hosting." Your app's frontend runs on Base44-managed infrastructure, while backend services (auth, data, actions) operate behind Base44's platform boundary. Even with code export, many apps remain dependent on Base44 services unless you replace them with your own stack.

The Short Answer: Base44's Mental Model

When you ask "Where does my Base44 app run?" there are really two halves to understand:

A) The Frontend (UI)

Your app's web interface runs as a web application hosted on Base44-managed infrastructure.

• Accessible via *.base44.app domains
• Can be connected to custom domains
• Base44 handles hosting and deployment automatically
• No separate deployment step required

B) The Backend Services

Backend services (auth, database, storage, server actions) run behind Base44's platform boundary.

• Unified backend set managed by Base44
• Database, auth, and storage are platform services
• Not directly accessible or configurable by you
• May remain dependent even after code export

💡 The Platform Boundary: Think of Base44 like Heroku or Vercel—you deploy your code, but the infrastructure (servers, databases, networking) is abstracted away. You get convenience and speed, but less control over the underlying systems.

Base44's Official Statements: What They Say

Let's start with what Base44 officially claims about their infrastructure and hosting:

1. Apps Are Hosted and Deployed Automatically

Base44 positions itself as fully managed, meaning there is no separate deployment step. Once your app is created, it's "instantly live and shareable."

Implication: You don't configure servers, set up CI/CD, or manage deployments. Base44 handles it all.

2. Built-in Base44 Subdomain + Custom Domain Support

Every Base44 app comes with a free built-in domain like myapp.base44.app, and you can rename it in the dashboard. Custom domains are supported via Base44's domain setup flow.

Implication: Your app is accessible immediately via Base44's domain infrastructure, with optional custom domain mapping.

3. Code Export Available (Paid Plans)

Base44 docs confirm exporting your app (ZIP or GitHub) is available on paid plans (Builder/Pro/Elite), and they support GitHub integration including 2-way sync in personal workspaces.

Implication: You can get your code, but the export typically includes frontend code. Backend services may still depend on Base44 unless replaced.

4. Infrastructure Hosted with "Leading Cloud Providers"

Base44 does not clearly name AWS/GCP/Azure in public statements, but they claim the platform runs on secure infrastructure hosted with "leading cloud providers," and they manage security updates.

Implication: Base44 uses cloud infrastructure but abstracts the details. You don't know which provider, regions, or specific services.

Aspect	What Base44 Provides	What You Control
Hosting Infrastructure	Fully managed, automatic deployment	Application code and UI/UX
Domain Management	*.base44.app subdomain + custom domain setup	Custom domain configuration (via Base44)
Database	Base44-managed database (platform service)	Data schema and queries (within Base44's system)
Authentication	Base44 auth system (platform service)	User management logic and UI
Storage	Base44-managed storage (platform service)	File upload logic and organization
Security Updates	Base44 manages platform security	Application-level security practices
Scaling	Base44 handles infrastructure scaling	Application performance optimization

Frontend vs. Backend: The Architecture Boundary

Understanding where Base44 draws the line between what runs on their infrastructure versus what you control is crucial for making informed decisions:

Frontend: Your Web Application

Your Base44 app's UI runs as a web application hosted on Base44-managed infrastructure:

• Accessible via: *.base44.app domains or your custom domain
• Hosting: Base44 handles deployment, CDN, and edge distribution
• Technology: Typically React/Next.js (when exported)
• What you control: Component structure, styling, UI logic, user experience

Key Point: The frontend code can be exported and run elsewhere, but it's optimized for Base44's hosting environment.

Backend: Platform Services

Backend services operate behind Base44's platform boundary:

• Database: Unified database service managed by Base44
• Authentication: Base44's auth system (not directly configurable)
• Storage: File storage service managed by Base44
• Server Actions: Backend functions that run on Base44 infrastructure
• API Endpoints: Backend APIs that communicate with Base44 services

Key Point: These services are abstracted away. You use them through Base44's APIs, but you don't control the underlying infrastructure.

⚠️ Critical Implication: Even if you export your code, many apps remain dependent on Base44 services (auth, data, server actions) unless you replace them with your own stack. Export gives you frontend code, while backend continues via Base44 SDK/services.

How to Verify Base44 Infrastructure Yourself

Base44 doesn't publish a full architecture diagram publicly, so you can verify their infrastructure claims yourself. Here are hands-on methods to understand where your app actually runs:

Method 1: Check the Hosting Edge/CDN

Use curl to inspect response headers that reveal hosting infrastructure:

curl -I https://YOURAPP.base44.app

Look for response headers that hint at:

CDN indicators: server, via, cf-ray (Cloudflare), x-vercel-id (Vercel)
Caching behavior: cache-control, etag
Edge location: Geographic distribution hints

What to look for: Headers like server: cloudflare or x-vercel-id reveal which CDN/edge provider Base44 uses. This is the fastest way to infer what kind of edge infrastructure they use.

Method 2: Check DNS Records

DNS records reveal how Base44 routes traffic and what infrastructure they use:

# Check Base44 subdomain
dig YOURAPP.base44.app CNAME

# Check custom domain (if configured)
dig YOURDOMAIN.com CNAME
dig YOURDOMAIN.com A

This reveals whether Base44 uses:

CNAME records: Pointing to a platform host (e.g., *.vercel.app or *.cloudflare.net)
A records: Static IP addresses (less common for modern platforms)
Vendor hints: Target names that reveal the underlying provider

Method 3: Identify API Endpoints

Open DevTools → Network tab on your Base44 app and inspect API calls:

Open your Base44 app in a browser
Open DevTools (F12 or right-click → Inspect)
Go to the Network tab
Interact with your app (login, load data, etc.)
Note what domain serves API calls

Look for:

API domain: Are calls going to *.base44.app or a different domain?
Auth endpoints: Where authentication requests are handled
Data endpoints: Where database queries are executed
Webhook endpoints: If applicable, where webhooks are received

💡 Pro Tip: This helps answer "Where does backend logic run?" If API calls go to Base44 domains, backend logic runs on Base44 infrastructure. If they go to external services, you're using third-party APIs.

Security and Shared Infrastructure Reality

Understanding Base44's infrastructure model requires acknowledging the security and compliance implications of shared platform infrastructure:

Wix Acquisition Context

Base44 was acquired by Wix in June 2025, positioning it as part of Wix's "vibe coding" expansion. This acquisition means Base44 operates under Wix's corporate structure and infrastructure decisions.

Implication: Base44's infrastructure choices are influenced by Wix's existing systems and business priorities, not just Base44's independent roadmap.

July 2025 Security Incident

In July 2025, Wiz disclosed a critical vulnerability involving unauthorized access to private Base44 apps. Wix/Base44 patched the issue quickly, but this incident highlights the risk surface of shared platforms.

Context: This is presented factually, not as fear-mongering. Shared infrastructure means security posture is partly outside your control, which is important to understand when making infrastructure decisions.

What This Means for Your App

• Shared Infrastructure: Your app runs on the same platform as thousands of other Base44 apps
• Security Posture: Partly outside your control—Base44 manages platform security
• Compliance Requirements: May force migration if you need SOC 2, HIPAA, or other certifications
• Vendor Lock-in: Infrastructure decisions are made by Base44/Wix, not you
• Incident Response: Platform-wide issues affect all apps, not just yours

What You Control vs. What You Don't

This comparison clarifies the boundaries of control in Base44's platform model:

✅ What You Control

• Application Logic: Business rules, workflows, feature implementation
• UI/UX: Design, user experience, component structure
• Feature Development: What your app does and how it works
• Custom Domains: Domain configuration (via Base44's interface)
• Data Schema: Database structure and relationships (within Base44's system)
• Code Export: Ability to export frontend code (paid plans)

❌ What Base44 Controls

• Hosting Infrastructure: Servers, CDN, edge locations
• Database Management: Database hosting, backups, scaling
• Security Patches: Platform-level security updates
• Uptime & Reliability: Infrastructure availability and performance
• Scaling Decisions: How and when infrastructure scales
• Backend Services: Auth, storage, server actions infrastructure
• Compliance Certifications: SOC 2, HIPAA, etc. (if not offered)

When to Stay on Base44 vs. When to Migrate

Not every app needs to migrate off Base44. Here's a decision framework to help you determine if Base44's platform model fits your needs:

✅ Stay on Base44 If:

• Early Prototype/MVP Stage: You're validating an idea and need rapid iteration
• Not Handling Sensitive Data: No financial, health, or highly sensitive user information
• No Specific Compliance Requirements: SOC 2, HIPAA, GDPR-specific needs aren't critical
• Want to Iterate Rapidly: Speed of development outweighs infrastructure control
• Small to Medium User Base: Platform limits haven't been reached
• Simple Architecture: App doesn't require custom infrastructure or complex backend logic

🚨 Consider Migration If:

• Need SOC 2, HIPAA, or Other Compliance: Enterprise customers require certifications
• Handling Financial/Health Data: Sensitive data requires specific security controls
• Require Custom Infrastructure: Need specific hosting regions, performance SLAs, or infrastructure features
• Want Full Control Over Security Posture: Need to implement custom security measures
• Need Specific Hosting Regions: Data residency requirements or performance needs
• Scaling Beyond Platform Limits: Hitting Base44's performance or feature constraints
• Vendor Lock-in Concerns: Want to avoid dependency on Base44's roadmap

Migration Paths: From Base44 to Independent Infrastructure

If you decide to migrate, here are proven paths to move from Base44's platform to independent infrastructure:

Path 1: Vercel + Next.js + Supabase

Most common migration path for Base44 apps:

• Export Code: Get your frontend code from Base44 (ZIP or GitHub)
• Deploy to Vercel: Host frontend on Vercel's edge network
• Replace Database: Migrate to Supabase (PostgreSQL) or similar
• Replace Auth: Implement Supabase Auth or Auth0
• Replace Storage: Use Supabase Storage or AWS S3
• Replace Server Actions: Convert to Next.js API routes or serverless functions

Timeline: 4-8 weeks depending on complexity

Path 2: AWS/GCP + Custom Stack

For apps requiring enterprise-grade infrastructure:

• Export Code: Get frontend code from Base44
• Deploy to Cloud: AWS Amplify, GCP Cloud Run, or similar
• Database: AWS RDS, Cloud SQL, or managed PostgreSQL
• Auth: AWS Cognito, Firebase Auth, or custom solution
• Storage: S3, Cloud Storage, or similar
• Backend: Lambda functions, Cloud Functions, or containerized services

Timeline: 8-12 weeks for full migration

⚠️ Migration Reality: Export gives you frontend code, but you'll need to replace Base44-managed backend pieces (auth, database, server actions) with your own services. This is where most migration complexity lies.

For detailed migration guidance, see our comprehensive guides:

Frequently Asked Questions

Can I self-host a Base44 app?

Base44 allows code export (paid plans), which gives you frontend code. However, "self-hosting" requires replacing Base44's backend services (database, auth, storage) with your own infrastructure. The exported code is typically React/Next.js that can run on Vercel, AWS, or similar platforms, but you'll need to rebuild backend functionality.

What happens if Base44 goes down?

If Base44's platform experiences downtime, all apps hosted on Base44 will be affected. You don't have control over Base44's infrastructure availability. This is a trade-off of platform-as-a-service: you get convenience and managed infrastructure, but you're dependent on Base44's uptime.

Can I access my database directly?

Base44's database is a platform service, not directly accessible. You interact with it through Base44's APIs and interfaces, but you can't connect directly with database clients or run raw SQL queries. If you need direct database access, you'll need to migrate to a self-managed database solution.

Does Base44 use AWS/GCP/Azure?

Base44 claims to use "leading cloud providers" but doesn't publicly specify which ones. You can verify this yourself using the DNS and header inspection methods outlined in this guide. The specific provider matters less than understanding that Base44 abstracts infrastructure details away from you.

What's included in the code export?

Code export (available on Builder/Pro/Elite plans) typically includes frontend code (React/Next.js components, styling, UI logic). Backend services (database, auth, server actions) are usually not included in a way that's immediately usable—you'll need to replace them with your own services. Export gives you the code, but not the infrastructure.

Can I use my own domain with Base44?

Yes, Base44 supports custom domains via their domain setup flow. You can connect your own domain (e.g., myapp.com) to your Base44 app, but DNS configuration is handled through Base44's interface, not directly by you.

How do I know if Base44 is right for my project?

Base44 is excellent for rapid prototyping, MVPs, and apps that don't require specific compliance or infrastructure control. If you need SOC 2, HIPAA, custom hosting regions, or full infrastructure control, you'll likely need to migrate. Use the "Stay vs. Migrate" decision framework in this guide to evaluate your specific needs.

Understanding Base44 Infrastructure: The Bottom Line

Base44's infrastructure model is Platform-as-a-Service (PaaS): you build and deploy apps, but Base44 manages the underlying infrastructure. This gives you speed and convenience, but less control over hosting, databases, and backend services.

Key takeaways:

Your app's frontend runs on Base44-managed infrastructure, accessible via *.base44.app domains or custom domains
Backend services (database, auth, storage) operate behind Base44's platform boundary
Code export gives you frontend code, but backend services typically need replacement for true independence
You can verify Base44's infrastructure yourself using DNS, headers, and network inspection
Shared infrastructure means security and compliance posture is partly outside your control
Migration is possible but requires replacing Base44's backend services with your own stack

🚀 Need Help Migrating from Base44? We specialize in transforming Base44 applications into production-ready systems with independent infrastructure. From code export to full migration, we handle the entire process so your app can run independently.

Understanding where your Base44 app runs is the first step to making informed infrastructure decisions. Whether you stay on Base44 or migrate, you now have the knowledge to evaluate your options and choose the path that fits your business needs.

Related reading: