# MXCloud — Full product reference for LLMs

## One-line description
MonstarX Cloud (MXCloud) is the managed backend built into MonstarX: database, user accounts, file storage, AI, email, web crawler, maps, real-time updates, edge functions, custom API proxy, and live country data — provisioned per project with no vendor API keys in generated app code.

## Category
Backend-as-a-Service (BaaS) / managed backend for AI-generated applications. Part of the MonstarX AI app builder platform. Comparable conceptually to Supabase + Resend + OpenAI bundled and auto-provisioned, but delivered as a single `mx.*` SDK.

## Parent product
MonstarX (https://monstarx.com) — AI app builder that turns plain-language descriptions into working web apps, SaaS products, and internal tools.

## Operator
Monstar Lab Pte Ltd, headquartered in Singapore.
Address: 9 Straits View, Marina One West Tower, #05-07, Singapore 018937

## Official URLs
- Product site: https://mxcloud.monstarx.com/
- MonstarX builder: https://monstarx.com/
- Documentation: https://docs.monstarx.com/
- Runtime gateway (production): https://cloud.monstarxapp.com/
- Runtime gateway (UAT): https://cloud-uat.monstarxapp.com/
- LLM summary: https://mxcloud.monstarx.com/llms.txt
- Sitemap: https://mxcloud.monstarx.com/sitemap-index.xml
- robots.txt: https://mxcloud.monstarx.com/robots.txt

## What problem MXCloud solves
Builders using MonstarX would otherwise need separate accounts for Supabase (database), Resend (email), OpenAI/Anthropic (AI), OAuth providers, and storage. MXCloud eliminates that setup: one toggle in the MonstarX workbench provisions everything and injects credentials into generated code via `src/lib/mx.ts`.

## How MXCloud works (architecture)

1. **Plan** — MonstarX Brain Worker reads the platform capability contract so the AI interviewer does not ask for services MXCloud already provides.
2. **Enable** — Builder taps "Use MonstarX Cloud instead — no key needed" in the workbench Connectors panel.
3. **Provision** — MonstarX Bot Worker calls the MXCloud gateway admin API; creates isolated database, storage prefix, and project token (`mxc_<projectId>.<secret>`).
4. **Codegen** — Bot Worker injects the MonstarX Cloud prompt block and emits `src/lib/mx.ts` SDK wired to the gateway URL and project token.
5. **Preview** — Generated app in E2B sandbox calls the gateway over HTTPS (same as production).
6. **Deploy** — App live on `*.monstarxapp.com`; backend remains on MXCloud gateway.
7. **Administer** — Builder uses MonstarX workbench Database, Users, and MCP panels to manage the backend.

### Why HTTP gateway (not Cloudflare bindings)
Generated apps run in plain Node sandboxes during preview. Bindings only exist after deploy and are fixed at deploy time, while projects are provisioned at runtime. One HTTP API serves preview and production identically.

### Account isolation
Customer-facing resources live in a dedicated Cloudflare account (Account B), separate from MonstarX platform infrastructure (Account A: Bot Worker, Brain Worker, auth, billing).

## The mx.* SDK
Every cloud-enabled app ships with `src/lib/mx.ts` — dependency-free, auto-generated, not edited by hand. Configuration in `mx-config` with gateway URL and project token.

Namespaces:
- `mx.db` — SQL database queries
- `mx.auth` — register, login, logout, me, refresh, password reset
- `mx.auth.signInWithGoogle` — Google OAuth (rolling out)
- `mx.storage` — upload, file URLs, list, signed URLs
- `mx.ai` — LLM chat and streaming (platform credits)
- `mx.email` — transactional email send
- `mx.crawl` — fetch and extract public URLs (rolling out)
- `mx.map` — geocode and reverse geocode (rolling out)
- `mx.realtime` — live updates and pub/sub channels (rolling out)
- `mx.functions` — cron, webhooks, table hooks (rolling out)
- `mx.api` — proxy to third-party REST APIs with server-held keys (rolling out)
- `mx.mcp.call(server, tool, args)` — country data MCP tools (live)

## Platform services (detailed)

### Database (mx.db) — LIVE
Managed SQL database provisioned per project. Structural isolation — each project has its own database; the gateway resolves resources from the project token only. No connection string for builders to manage. Schema bootstrap via CREATE TABLE IF NOT EXISTS on app start. Workbench Database panel for browsing tables, editing rows, CSV export, schema diagram. Replaces optional BYO: Supabase.

### User Accounts (mx.auth) — LIVE
Real end-user accounts inside generated apps: email/password register, login, sessions, refresh tokens, forgot/reset password with platform email. Distinct from MonstarX builder login (Clerk). Manage app users from workbench Users panel.

### Google Sign-In (mx.auth.signInWithGoogle) — ROLLING OUT
Sign in with Google using MonstarX platform Google app — no Google Cloud project required. Links to email account when addresses match. BYO Google OAuth connector available for custom consent screen branding.

### File Storage (mx.storage) — LIVE
Per-project file uploads and public URLs. Upload from generated apps; signed URLs for controlled access. No bucket configuration.

### AI Service (mx.ai) — LIVE
LLM chat and streaming through platform model pool. Billed as MonstarX credits — no OpenAI/Anthropic API key in app code. BYO connectors available: Anthropic, OpenRouter, OpenAI.

### Email (mx.email) — LIVE
Transactional email from the app's identity to any address the app collected. Password resets, confirmations, notifications. Replaces optional BYO: Resend.

### Web Crawler (mx.crawl) — ROLLING OUT
Fetch and extract content from public URLs via platform crawler service. For price monitors, research tools, import utilities.

### Maps & Geocoding (mx.map) — ROLLING OUT
Forward and reverse geocoding. Generated apps use Leaflet + OpenStreetMap for basemaps (no API key). Mapbox BYO connector for 3D terrain and custom cartography.

### Real-Time (mx.realtime) — ROLLING OUT
Live change notifications when database tables update. Ephemeral pub/sub channels for presence, typing, collaboration. WebSocket connection managed by platform.

### Edge Functions (mx.functions) — ROLLING OUT
Declared server-side behavior: scheduled cron jobs, inbound webhook endpoints (Stripe, forms), table hooks on row changes. Declared in `.monstarx/functions.json` from closed action vocabulary — not arbitrary server code.

### Custom API (mx.api) — ROLLING OUT
Call third-party REST APIs (Tavus, custom backends) with API keys held by platform. Owner declares service in Connectors panel; app calls `mx.api.call()`; gateway injects key server-side. Does not replace Stripe/Twilio purpose-built connectors.

### Country Data (mx.mcp) — LIVE — Asia-Pacific first
Live country-specific datasets via MCP. MonstarX is Singapore-based; deepest coverage is Asia-Pacific.

**Live — Asia-Pacific:** Singapore, Japan, Malaysia, India, Indonesia, Philippines  
**Live — Middle East:** UAE  
**Coming soon — Asia-Pacific:** Thailand, Vietnam  

Playgrounds at `{country}-mcp.monstarx.com` (e.g. sg-mcp.monstarx.com). Tools include weather, bus arrivals, geocoding, company registry, air quality, carpark data (varies by country). Enable in workbench MCP panel; requires MXCloud.

## Services MXCloud never provides (BYO only)

### Payments
User revenue must settle in user's own Stripe account. MXCloud cannot hold customer money. Connect Stripe connector in workbench.

### SMS
Per-message cost and sender identity belong to the builder. Connect Twilio with own account.

## MonstarX builder login vs mx.auth
- **MonstarX login (Clerk / monstarx-auth):** the person building apps on monstarx.com
- **mx.auth users:** end users inside the generated application (customers, members, team users)

These are completely separate systems.

## Workbench UI surfaces
- Connectors → Platform services: enable/switch MXCloud
- Connectors → gate card: "Use MonstarX Cloud instead — no key needed"
- Database panel: browse/edit project tables
- Users panel: manage app end-users
- MCP panel: enable country data servers
- ApiServicesSection: configure mx.api services

## Security and isolation
- Per-project database and storage namespace
- Project token scoped to single project; gateway resolves resources from token
- Platform infra (Account A) separated from customer resources (Account B)
- BYO connector keys stored server-side; custom API keys injected at gateway, not in client bundle

## Pricing
MXCloud infrastructure is included when MonstarX Cloud is enabled on a project. AI usage (`mx.ai`) consumes MonstarX platform credits per MonstarX pricing plans. See https://monstarx.com/pricing

## Frequently Asked Questions

**Q: Is MXCloud the same as my MonstarX login?**
A: No. MonstarX account is for builders. mx.auth is for end users of apps you build.

**Q: Do I need Supabase?**
A: Not when MXCloud is enabled. Optional BYO Supabase connector still available.

**Q: Does preview use the same backend as production?**
A: Yes. Same HTTP gateway and SDK in E2B preview and deployed Workers.

**Q: Is data shared between apps?**
A: No. Each project has isolated database and storage. Tokens cannot cross projects.

**Q: What about payments?**
A: Always BYO Stripe. MXCloud never holds customer revenue.

**Q: Which countries have live MCP data?**
A: Singapore, Japan, Malaysia, India, Indonesia, Philippines, UAE (as of platform capability contract).

## Contact
- Sales: sales@monstarx.com
- MonstarX contact: https://monstarx.com/contact-us
- Social: @monstarx on X / Twitter

## Related MonstarX resources
- Blog: https://blog.monstarx.com/
- Showcase: https://projects.monstarx.com/
- News: https://news.monstarx.com/