How to Integrate Lovable with Lovable Cloud

The Cloud tab is your dashboard for everything Lovable Cloud provides. To open it, look for the '+' icon at the top of the left sidebar in the Lovable editor — clicking it reveals a panel with several tabs. Click 'Cloud' to see your project's current resource state. You will find the following sections: Database (your PostgreSQL instance with a table editor and SQL runner), Users & Auth (email/password, magic links, and OAuth provider settings), Storage (file buckets with upload/download management), Edge Functions (list of deployed server-side functions), AI (built-in AI feature configuration), Secrets (encrypted environment variable storage), Logs (real-time execution output), and Usage (resource consumption metrics against your monthly balance). At the top of the Usage section you will see your balance — every workspace starts with a $25 monthly Cloud balance. Lovable Cloud also provides a $1 AI balance for testing AI-powered features. Resource alerts fire automatically when disk space drops below 10% of your allocation, IO budget drops below 50%, or CPU load exceeds 80%. These alerts appear as notifications in the editor. Spend a few minutes exploring each section before building — understanding what is available here will inform how you prompt the AI agent throughout the rest of your project. The region your project runs in (Americas, Europe, or Asia Pacific) was selected at creation and is shown here as a read-only field. If you need a different region, you will need to create a new project.

Lovable Cloud's PostgreSQL database is the primary data layer for your app. You do not write SQL to create tables — you describe what you need in plain English and the AI generates the schema, creates the table, and configures Row Level Security policies automatically. This is one of the biggest advantages of using Lovable Cloud over a manually connected external database: the AI understands your full project context and can generate correct, secure schemas without any manual wiring. In the Lovable chat prompt (bottom-left), describe the data your feature needs. Be specific about the fields, their types, and who should be able to read or write the data. For example, if you are building a feedback tool, describe the columns you need and whether feedback should be visible only to admins or to the user who submitted it. Lovable will generate a database migration, apply it to your Lovable Cloud PostgreSQL instance, add appropriate RLS policies, and update your frontend code to query the new table — all in one step. After the change applies, navigate to Cloud tab → Database to verify the table was created with the expected columns. You can also use the SQL editor in that tab to run test queries directly against your database.

When your app needs to call an authenticated external service — a payment processor, an email API, a third-party AI model — the API key must never appear in your frontend code. Lovable Cloud's Secrets panel is where these credentials live, encrypted and accessible only from Edge Functions in the red zone. The client-side blue zone can never read them. To add a secret, go to the Cloud tab and click 'Secrets'. Click 'Add secret', enter the exact name you will reference in code (for example, RESEND_API_KEY), paste the key value, and save. The name is case-sensitive and must match exactly what you use in your Edge Function. Platform secrets like your Supabase URL and the Lovable API key are pre-populated and cannot be edited — leave those alone. Once the secret is stored, describe the backend behavior you need in chat. Lovable will generate an Edge Function that reads the secret using Deno.env.get('RESEND_API_KEY'), makes the server-side API call, and returns a result to the frontend. You should never paste API keys directly into the Lovable chat — on the free plan, chat history is publicly visible, and keys pasted in chat can be recovered from commit history. Always use the Secrets panel or the secure 'Add API Key' form that Lovable prompts you with when it detects a new credential is needed.

Lovable Cloud Storage (built on Supabase Storage) supports files up to 2 GB per upload and organizes files into buckets — containers that each have their own access settings. The most important thing to understand about storage is that the default configuration makes buckets publicly accessible. If you are storing user profile photos, app assets, or public download files, this is fine. If you are storing invoices, personal documents, contracts, or any sensitive content, you must explicitly configure the bucket for authenticated access with signed URLs. To set up storage through chat, describe what files your app will handle and who should be able to access them. Lovable will create the bucket, set the appropriate RLS policies on the storage.objects table, and generate the frontend code to handle upload and download. For public buckets, files are served directly via a stable URL. For private buckets, downloads require generating a short-lived signed URL server-side through an Edge Function — Lovable can scaffold this pattern for you automatically when you specify that access should be restricted. After setup, navigate to Cloud tab → Storage to see your buckets and verify the access settings. You can upload a test file directly from this panel to confirm the configuration is correct before writing frontend upload logic.

Lovable Cloud usage is tracked against your monthly $25 Cloud balance, which resets each billing period. Different resources consume different amounts: database storage, storage bandwidth, Edge Function invocations, and Auth monthly active users all count against the balance. On free plans, you are on a Tiny instance with limited resources. Paid plans allow upgrading to Small, Medium, or Large instances as your app scales. To monitor usage, open Cloud tab → Usage. This view shows your current consumption for each resource category alongside your allocation. Resource alerts are sent automatically — at 10% remaining disk, 50% remaining IO budget, and 80% CPU load — but checking this panel proactively is good practice, especially after launches or traffic spikes. If you see unexpectedly high Edge Function invocation counts, check Cloud tab → Logs to identify which functions are being called and how often. Logs provide real-time output from all Edge Functions and are the first place to check when debugging backend behavior. For paid plan users, if your app consistently exceeds Tiny instance limits, upgrade the instance size from Cloud tab → Database. You cannot change your hosting region after the project is created, but you can upgrade instance size at any time. For complex scaling questions or if you are hitting resource limits unexpectedly, RapidDev's team can help audit your Edge Function architecture and database query patterns to reduce unnecessary resource consumption.