--- title: "Why Keeping an AI-Built App Awake Can Cost $186–$282/mo—And How to Run It 24/7 for a Flat $99–$199 | GreenTree" url: https://www.greentreehosting.com/library/hosting-your-ai-built-app-beyond-lovable-famous-builder/ description: "By Gene Salvatore: Public pricing breakdown of Famous.ai’s 40-hour free allowance (~$186–$282/mo after free hours; Famous.ai lists ~$197–$297/mo) and Lovable’s shared build-and-run database credits, plus how GreenTree runs your app 24/7 for a flat $99–$199/mo." format: text/markdown generated_from: prerendered HTML (build time) --- [Back to Cornerstone Engineering Library](https://www.greentreehosting.com/library) AI APP GRADUATION & SECURITY12 MIN READAUTHORED BY GENE SALVATORE # Why Keeping an AI-Built App Awake Can Cost $186–$282/mo. (Famous.ai Lists ~$197–$297)—And How to Run Yours 24/7 for a Flat $99–$199. You aren’t a "vibe coder"—you are a new-era developer who translated real domain expertise into working software. The challenge comes after the prototype works: keeping a live commercial application online across a full 31-day month without hourly awake bills or paused backends. Here is the public pricing and reliability math for **Famous.ai** and **Lovable**, why shared build-and-run credits can pause your database, and how GreenTree moves your application onto **flat $99–$199/mo Linux & PostgreSQL infrastructure**—monitored around the clock, locked down across **all 4 security doors (including CVE-2025-48757)**, and paired with real [@yourdomain.com enterprise email](https://www.greentreehosting.com/email). FAMOUS.AI AWAKE BILL $186–$282/mo Net After 40 Free Hrs (Famous.ai Lists ~$197–$297/mo for 24/7 Uptime) LOVABLE BACKEND DRIP 8–11 Days 20-Credit Grant Duration Before Drawing From Build Credits 24/7 FLAT RATE $99 or $199/mo Hosting Since 2007 · Core Cloud or Managed Care With Monthly Edits SECURITY & EMAIL 4 Open Doors Secret Key Isolation, PostgreSQL RLS, Webhook Gates & Source Maps EXECUTIVE THESIS // ARCHITECTURAL BRIEF ## Why We Wrote This Playbook—And What It Means for Your Next Platform Thousands of founders, operators, and domain experts are learning to be developers in the new sense of the word—articulating exact business logic, giving sharp iterative feedback, and building real, working software on platforms like Famous.ai, Lovable, Bolt, and Replit. Your work isn’t wrong. You built something real. The challenge is what happens *after* the prototype works: keeping a commercial application online 24/7 without hourly awake bills or paused backends, locking down database and API security, and replacing free `@gmail.com` addresses with authenticated domain email. [Explore Web Application Engineering](https://www.greentreehosting.com/web-applications)[View Growth Retainers](https://www.greentreehosting.com/retainers) PRINCIPAL AUTHORSHIP // IN WEB & CLOUD SINCE 1997 ![Gene & Maureen Salvatore](https://www.greentreehosting.com/images/gene-and-maureen-salvatore-marriott-bonvoy-jfk.webp) Gene Salvatore Co-Founder & Principal Systems Architect, GreenTree Hosting, LLC · Published 2026-10-24 In 1997, Maureen & Gene Salvatore pitched the Rhode Island State-Wide MLS, registered RILiving.com in June 1997, and launched one of the state’s earliest searchable database-driven real estate platforms in January 1998. Following senior roles in commercial hosting and physical data center operations in Boston and Connecticut, they founded GreenTree Hosting, LLC in 2007 to build custom web applications and managed Linux cloud infrastructure. PARTNERSHIP35-Year Commercial Team SOVEREIGN FLEET28 Autonomous Cloud Agents INFRASTRUCTURE3-Region NVMe Linux Mesh ACCOUNTABILITY100% Founder Direct (CT) [Read Our 1997–2026 Story](https://www.greentreehosting.com/story)[Gene Salvatore Bio](https://www.greentreehosting.com/leadership/gene-salvatore)[Scope Your Project](https://www.greentreehosting.com/order) KEY TAKEAWAYS (4 CORE POINTS) TAKEAWAY 01 New-era development is a real skill: turning industry expertise into working software through disciplined iteration is a steep learning curve of its own. TAKEAWAY 02 Famous.ai bills for awake time: after 40 free hours (~1.7 days), an awake app costs about $186–$282/mo (Famous.ai lists ~$197–$297/mo) even with no visitors. TAKEAWAY 03 Lovable shares build and hosting credits: active databases bill hourly, and when your shared credit balance runs out, the backend can pause. TAKEAWAY 04 Flat-rate production on GreenTree: we move your app into a clean client-owned Git repo, lock all 4 security doors, include 1 SmarterMail Enterprise @yourdomain.com account free with hosting (additional accounts $6–$18/mo), and monitor your live app every minute. PRIMARY RESEARCH & SUBSTACK DISPATCHES // GENE SALVATORE ### Companion Essays from AOS Architecture & Truth by Gene Salvatore (Substack) Read Gene Salvatore’s primary research on the Drip Economy, cognitive rent, and why independent builders need deterministic security boundaries around the applications they build. [Read on Substack](https://genesalvatore.substack.com)[RSS Feed](https://genesalvatore.substack.com/feed) [SUBSTACK ESSAY · MARCH 15, 2026The Drip Economy & Cognitive Rent: Why Independent Builders Are Being Priced OutHow continuous compute meters, credit pools, and architectural fragmentation create "cognitive and compute rent" for independent builders—and why owning the underlying infrastructure matters.Read Full Dispatch on Substack →](https://genesalvatore.substack.com/p/the-drip-economy-and-cognitive-rent)[SUBSTACK ESSAY · MARCH 20, 2026Your Work Isn’t Wrong. Your Front Door Is Unlocked.Why the capability layer you worked so hard to build is real and valuable—and why an incomplete security perimeter is an architectural step to finish, not a reason to start over.Read Full Dispatch on Substack →](https://genesalvatore.substack.com/p/your-work-isnt-wrong-your-front-door)[SUBSTACK ESSAY · APRIL 3, 2026The Day the Source Code Leaked: A Eulogy for the Probabilistic Software StackHow a single 59.8 MB source map packaging error exposed 512,000 lines of TypeScript—proving that deployment hardening is an infrastructure discipline even multi-billion-dollar labs get wrong.Read Full Dispatch on Substack →](https://genesalvatore.substack.com/p/the-day-the-source-code-leaked) PART 01 // RESPECT FOR THE NEW-ERA DEVELOPER ## 1. You Aren’t a "Vibe Coder"— You Learned to Be a Developer in the New Sense of the Word There is a lazy, dismissive phrase making the rounds in software circles right now: **"vibe coder."** It is usually thrown around by people who have never watched a small business owner, an industry veteran, or a founder sit at a keyboard for weeks, translating **twenty years of real-world domain knowledge** into a working application. The builders we talk to every week who have created applications on **Famous.ai, Lovable, Bolt, or Replit** aren’t blindly clicking a magic button and hoping for the best. They are **learning the skills to be developers in the new sense of the word**. They are detail-oriented about what they want. They **test every screen, spot where the workflow breaks, give clear and structured feedback to the model**, and lean into an iterative process until the software actually solves the problem in front of them. Learning how to direct an AI system with that level of clarity is a steep learning curve all by itself. At GreenTree, we tested these AI builder platforms firsthand (a broader look at the economics is on Substack in ["The Drip Economy & Cognitive Rent"](https://genesalvatore.substack.com/p/the-drip-economy-and-cognitive-rent)). As I wrote in ["Your Work Isn’t Wrong. Your Front Door Is Unlocked,"](https://genesalvatore.substack.com/p/your-work-isnt-wrong-your-front-door) if you have put in those hours, wrestled with the prompts, and watched your application come alive in the preview window, this article isn’t here to tell you that you did it wrong. **You didn’t. You built something real.** We are here to talk about the **second mountain**—what it takes to keep that application running **24 hours a day, 7 days a week, 30 days a month** without paying an hourly awake tax or having your backend pause, how to close the security shortcuts AI prototypes leave behind, and how to present your business with real domain email. MOUNTAIN 01 // ALREADY CLIMBED ### Architectural Direction & Iterative Feedback You already mastered the hardest creative leap: turning your industry knowledge into working screens, forms, calculators, and workflows through disciplined iteration. Real Software · Not "Just a Prompt" MOUNTAIN 02 // THE PRODUCTION STEP ### Production Security, Uptime & Predictable Hosting Building an app and running it safely in production are two different jobs. Expecting a new builder to automatically know Linux hardening, RLS policies, and DNS cryptography isn’t fair. The Transition From Prototype to Production MOUNTAIN 03 // PERSISTENT OWNERSHIP ### Moving From Metered Sandboxes to Flat-Rate Cloud Once your application works, moving it onto persistent Linux and PostgreSQL servers eliminates hourly sandbox meters and gives you complete code and data ownership. Predictable Monthly Cloud Hosting PART 02 // PUBLIC PRICING & RELIABILITY BREAKDOWN: FAMOUS.AI VS. LOVABLE ## 2. Two Different Models: Famous.ai’s $186–$282/mo Awake Bill vs. Lovable’s Shared-Credit Backend When you look at the public documentation for AI app builders, **Famous.ai** and **Lovable** handle live applications in two very different ways—one is a direct monthly cost issue, and the other is a reliability and credit-structure issue across a **744-hour month** (31 days × 24 hours). PLATFORM 01 // HOURLY AWAKE BILLING MODEL **Platform 1 — Famous.ai (`famous.ai/usage` & Famous Labs Help Center, checked October 24, 2026): About $186–$282/mo After Free Hours (Famous.ai Lists ~$197–$297/mo).** According to Famous.ai’s public usage page ([famous.ai/usage](https://famous.ai/usage), checked October 24, 2026), a plan includes **40 free hosting hours per month**. A live application running around the clock for a 31-day month uses 744 hours, so the 40-hour free allowance covers roughly **1.7 days** (`40 ÷ 24 = 1.67 days`). Once the free hours run out, an awake project is billed by the hour **"even if there is no user activity"** ([Famous Labs Help Center: Credits, Hosting & API Pricing](https://help.famouslabs.com/en/articles/13922207-famous-ai-credits-hosting-api-pricing), checked October 24, 2026). After subtracting the 40 free hours, the remaining **704 billable hours** work out to **about $186 to $282 per app per month**: Famous.ai’s usage page lists **$0.40/hr** for each of your first three projects (`704 billable hrs × $0.40/hr = $281.60/mo`, while Famous.ai’s page lists **~$297/month per project** across the full month), and the Help Center article lists **$0.2648/hr** (`704 billable hrs × $0.2648/hr = $186.42/mo`, or **~$197/mo** before subtracting free hours). Famous.ai offers two ways to avoid hourly billing: putting a project to **sleep for $0**, or buying their **$2,450/year unlimited-hosting plan** (`famous.ai/usage`, checked October 24, 2026), which covers every project on the account. For a single live business app, neither fixes the problem: a sleeping app is offline when a customer visits your link, and **for a single app**, $2,450 a year ($204.17/mo paid upfront) is still more than GreenTree’s managed plan and more than double our Core Cloud plan ($1,188/yr). PLATFORM 02 // SHARED-CREDIT DATABASE MODEL **Platform 2 — Lovable (`docs.lovable.dev`, checked October 24, 2026): Shared Credits, Paused Backends & Storage Limits.** For small apps, Lovable is not a high-dollar hosting bill—publishing a static frontend is free, and Lovable states that small apps usually stay within the included monthly allowance ([docs.lovable.dev/features/project-usage](https://docs.lovable.dev/features/project-usage), checked October 24, 2026). With Lovable, the comparison is about **reliability and operational control**: once an app uses Lovable’s built-in database, it is billed for each hour the database runs (*"A larger instance… costs more credits every hour your app runs,"* and the bill depends partly on *"how long it stays active"* — [docs.lovable.dev/introduction/credits-and-usage](https://docs.lovable.dev/introduction/credits-and-usage) and [docs.lovable.dev/features/advanced-settings](https://docs.lovable.dev/features/advanced-settings), checked October 24, 2026). According to [user-reported measurements on r/lovable](https://www.reddit.com/r/lovable/comments/1ue71w6/update_on_run_cost_problems/) on idle databases with zero traffic, the smallest instance (**Tiny**) uses about **1.86 credits/day** (~56 credits/mo) and the next size up (**Mini**) uses about **2.5 credits/day** (~75 credits/mo). Because Lovable’s **20-credit** monthly hosting grant is labeled **"temporary"** (`docs.lovable.dev/features/project-usage`), that grant runs out in **about 8 to 11 days** (`20 ÷ 2.5 to 1.86`). After that, building and hosting draw from **one shared credit balance**. If you burn through your credits iterating on features—or if a traffic spike hits—the public site stays up, **but Lovable’s docs state that the app’s backend "can pause" until you add credits** (disabling your database, user logins, and file storage, while stored files keep consuming credits even while paused). In addition, documented [Lovable Cloud constraints](https://dev.to/batmanofweb/lovable-cloud-what-you-actually-get-17cm) note that database storage allocations cannot be shrunk once raised, and full exports are capped at 1 per 24 hours and 5 GB. | Hosting & Reliability Dimension | Famous.ai (famous.ai/usage & Help Center, Checked Oct 24, 2026) | Lovable Cloud (docs.lovable.dev, Checked Oct 24, 2026) | GreenTree Core Cloud ($99 or $199/mo Flat) | | --- | --- | --- | --- | | Staying Online 24/7 Around the Clock | Billed hourly after 40 free hours "even if there is no user activity": ~$186–$282/mo net (lists ~$197–$297/mo) | Database billed per hour while it runs; building and hosting share one credit balance | Included in one flat monthly rate, checked every 60 seconds | | Included Monthly Hosting Allowance | 40 free hours/mo — covers ~1.7 days (40 ÷ 24) of a 31-day month | 20-credit "temporary" monthly grant — lasts ~8–11 days at 1.86–2.5 credits/day on Tiny/Mini DBs | Full 24/7/365 uptime included at one flat rate with no credit meter | | What Happens When Credits Run Out | Awake projects accrue hourly hosting charges or must be put to sleep (offline) | Published site stays up, but the backend (database, logins & storage) "can pause"; stored files keep using credits | No credit balance to run out — your frontend and PostgreSQL database stay running 24/7 | | Alternatives to Hourly / Credit Metering | Sleep mode ($0) takes your app offline; $2,450/yr unlimited plan ($204/mo) costs more for a single app than our managed plan | Static frontend alone is free, but any active database shares the same credit pool used for building | No sleep mode and no upfront annual lock-in — flat $99/mo Core Cloud or $199/mo Managed | | Database Storage & Export Control | Runs inside Famous.ai managed sandbox container environment | Database storage cannot be shrunk once raised; full exports capped at 1 per 24 hours and 5 GB | Dedicated single-tenant PostgreSQL database (client-owned) with unrestricted pg_dump exports | PART 03 // ALWAYS ON. NO METER, NO SLEEP, NO SPIN-UP. ## 3. Persistent Servers. No Meter, No Sleep, No Spin-Up— Monitored Around the Clock On builder platforms, staying awake has strings attached. **Famous.ai bills each hour your app is live**, even when nobody visits, and putting it to sleep takes it offline. **Lovable bills the database for every hour it runs** out of the same credit pool you use to build, and can pause your backend when credits run out. On GreenTree, **your app stays on around the clock for one flat monthly rate** (**Core Cloud** or **Core Cloud + Management**), backed by our team **hosting mission-critical applications since 2007**. Your application and its dedicated single-tenant PostgreSQL database run on persistent Linux servers, so your app is **already running when a visitor arrives**—nothing has to spin up from sleep. Our automated probes (`LogBot.app` & `DNSBot.app`) check your application **every 60 seconds**: on a server that is always running, that check confirms the app and database answer cleanly and alerts us if they don’t, usually before customers notice; if your app also uses any on-demand serverless functions, that heartbeat keeps those functions warm. **And running all night doesn’t add to the bill.** - **No Credit Hoarding: Commit Every Change for Instant Breadcrumb Rollbacks:** In AI builder platforms (Lovable, Replit, Bolt, Cursor), developers often develop "commit anxiety"—they hoard and delay commits to avoid burning monthly build credits, deployment quotas, or AI generation tokens. They bundle ten unrelated modifications into one massive commit. The problem? When a breaking bug slips in, you cannot cleanly isolate what failed or roll back five minutes of work. On GreenTree Cloud and Cloud Dedicated, Git deployments are completely unmetered. If your engineering workflow requires committing every single change so you have granular breadcrumb rollbacks at every step, you can commit fifty times a day without spending a single extra dime or burning a token pool. Git becomes the safety net it was meant to be. That same architecture protects you when a post on **LinkedIn, Substack, or X** finally catches fire and sends a few thousand viewers to your site in an afternoon. On a credit-metered platform where uncached database reads or ungated AI calls draw from your credit balance, a traffic spike can exhaust your credits and pause your backend right when prospects are trying to sign up. On GreenTree, we **prerender your public pages into fast HTML at build time** and place **edge caching and rate limits** in front of your backend—so **5,000 or 50,000 visitors** can read your site without burning credits or changing your flat monthly invoice. PERSISTENT SERVERS // FLAT MONTHLY RATE ### Already Running When Visitors Arrive Your application and PostgreSQL database stay running 24/7 for a flat monthly rate. You never have to put a project to sleep or worry about your backend pausing overnight. Hosting Since 2007 · No Hourly Meter AUTOMATED PROBES // LOGBOT & DNSBOT ### Proactive Uptime & DNS Verification Our monitors verify your live application every minute to confirm it answers and alert our desk in Southbury, CT, usually before customers notice—while keeping any on-demand functions warm. Continuous Health & DNS Monitoring TRAFFIC SPIKE SHIELD // SSR + RATE GATES ### Viral Traffic Doesn’t Drain Credits or Pause Logins Build-time HTML prerendering serves public readers without hitting your database on every view, while per-IP rate limits protect any live AI or API routes from bots. Predictable Billing at 50 or 50,000 Views PART 04 // YOUR WORK ISN’T WRONG—YOUR FRONT DOOR IS UNLOCKED ## 4. The 4 Security Doors AI Prototypes Leave Open (Including CVE-2025-48757) If you are a new-era developer—someone who learned how to guide an AI to build your product rather than spending ten years studying Linux system administration—there is **zero shame in not knowing how to audit a production security perimeter**. Even multi-billion-dollar AI labs get deployment packaging wrong: on **March 31, 2026**, Anthropic accidentally left a **59.8 MB `.map` source map file** inside their public npm release, exposing **512,000 lines of internal Claude Code TypeScript** to the internet. Why do AI-built applications so often ship with security gaps? Because **an AI coding assistant is optimized to make your error message go away as fast as possible**. In May 2025, security researchers documented **CVE-2025-48757** after analyzing 1,645 Lovable-built applications in the wild and finding that **170 of them (about 10.3%)** exposed sensitive database records—including customer PII, payment statuses, and API tokens—because Supabase Row-Level Security (RLS) policies were either missing or overly permissive. Lovable disputes the classification, saying RLS setup is the customer’s responsibility. **Either way, someone has to own it.** Similarly, new builders are often confused about which keys belong in the browser. A **Supabase `anon` key is public by design**—it is meant to be shipped in the browser *provided* your database tables are locked down with strict Row-Level Security (RLS). The fatal mistake AI tools make is either leaving RLS wide open behind that public `anon` key, or putting **private secret keys** (like a Supabase `service_role` key, or your secret OpenAI, Anthropic, Stripe, or Resend keys) into client-side `VITE_` or `NEXT_PUBLIC_` variables where anyone who opens Chrome DevTools (`F12`) can read them. Before we launch your app on GreenTree, our founding principals **inspect and close all four open doors**: OPEN DOOR 01 // PRIVATE KEYS IN VITE_ ### Secret API & service_role Keys in Browser Bundles While a Supabase anon key is public by design, AI tools routinely place private OpenAI, Anthropic, Stripe, Resend, or Supabase service_role secret keys into VITE_ or NEXT_PUBLIC_ variables exposed in plain text. Fix: Move All Secret Keys to Server-Side Endpoints OPEN DOOR 02 // CVE-2025-48757 (10.3% EXPOSED) ### Missing or Permissive Supabase Row-Level Security (RLS) CVE-2025-48757 found 170 of 1,645 scanned Lovable apps (~10.3%) left database tables exposed (Lovable disputes the classification, saying RLS setup is the customer’s responsibility). When an AI writes USING (true) to fix an error, your public anon key can read or wipe the table. Fix: Table-by-Table PostgreSQL RLS Lockdown OPEN DOOR 03 // UNPROTECTED WEBHOOKS & FORMS ### Missing Payload Validation, CORS & Bot Throttling AI-generated contact forms, signup routes, and Stripe/webhook listeners rarely verify cryptographic HMAC signatures or enforce per-IP rate limits—inviting spam injection and credit exhaustion. Fix: Edge Rate Limiting & Signature Verification OPEN DOOR 04 // LEAKED .MAP SOURCE MAPS ### Production Build Configurations Shipping Full Source Code Default bundler settings or unhardened deploy scripts can leave .js.map files or .env templates publicly accessible on your domain, letting anyone reconstruct your proprietary TypeScript logic. Fix: Deterministic Build Stripping & Header Locks Real Code Comparison: What the AI Prototyping Tool Generated vs. How GreenTree Hardens Your Production BuildReference Blueprint ``` // Canonical Reference: https://www.greentreehosting.com/library/hosting-your-ai-built-app-beyond-lovable-famous-builder/ // © 2026 GreenTree Hosting, LLC (Gene Salvatore) · 4-Door Security & RLS Hardening Standard // ❌ BEFORE: Typical AI Sandbox Shortcut (What Leads to CVE-2025-48757 & Stolen Keys) // 1. Private secret key placed in a public VITE_ browser variable (visible in DevTools -> Sources): const openai = new OpenAI({ apiKey: import.meta.env.VITE_OPENAI_API_KEY, dangerouslyAllowBrowser: true }); // 2. Permissive Supabase RLS policy generated by the AI just to "make the permission error go away": // (Even though the Supabase anon key is public by design, USING (true) lets anyone dump the table!) CREATE POLICY "Allow all access for prototype" ON public.customer_leads FOR ALL USING (true) WITH CHECK (true); // ============================================================================ // ✅ AFTER: GreenTree Production Hardening (All 4 Doors Locked · greentreehosting.com) // 1. Private secret keys live strictly on the server; sourcemaps disabled in production build. // 2. Strict PostgreSQL Row-Level Security (RLS) enforced on your dedicated single-tenant database: ALTER TABLE public.customer_leads ENABLE ROW LEVEL SECURITY; REVOKE ALL ON public.customer_leads FROM anon; CREATE POLICY "Insert-only validated lead intake" ON public.customer_leads FOR INSERT TO anon WITH CHECK (length(email) <= 254 AND site_id = 'your-verified-site'); ``` PART 05 // THE @GMAIL.COM CREDIBILITY & DELIVERABILITY GAP ## 5. "Wait… You Mean My @gmail.com Address Isn’t Good Enough?"— Why Commercial Apps Need Real Domain Mail There is a moment almost every new builder hits right around launch day. You have spent weeks getting your application’s design, workflows, and pricing pages dialed in. On screen, it looks like a serious, trustworthy company. Then you go to wire up your contact page, your customer support link, or your automated signup emails—and you realize you are still sending from **`yourcompanyname@gmail.com`**, or your app’s automated emails are **landing in your users’ Junk folders**. After 29+ years in commercial hosting, we can tell you firsthand: when a prospective customer, partner, or investor sees a free `@gmail.com` or `@outlook.com` address on a commercial web application, it immediately raises doubts. Worse, if you try to have your new application send **password resets, receipts, or lead notifications** claiming to be from `@yourdomain.com` without properly configured authoritative DNS (`SPF`, `2048-bit DKIM`, `DMARC`, and matching reverse-DNS `PTR` records), **Gmail and Microsoft 365 will quarantine or reject your messages**. While Google Workspace and Microsoft 365 entry plans start around **$6 to $14+ per user per month** (and climb to $18–$26+ as you add storage, archiving, or security add-ons), they still don’t configure your application’s transactional SMTP routing or DMARC alignment for you. Since 2007, GreenTree has run a dedicated, three-tier relay-isolated email architecture: our **Inbound Proxmox Mail Gateway (mx.greentreemail.com)** scrubs all incoming mail at the network edge, our **SmarterMail Enterprise server (east.greentreemail.com)** stays completely isolated from direct public SMTP traffic, and **multiple dedicated outbound relay gateways** handle all outgoing delivery so your domain avoids the IP blacklists that plague standard cloud hosts. Even better, **1 user account on our SmarterMail Enterprise plan is included free** with every GreenTree Cloud Hosting plan (starting at $99/mo), with additional `@yourdomain.com` accounts (Autodiscover, IMAP, SMTP, POP3, Webmail, Mailing Lists & DMARC) at **$6 to $18 per mailbox**. IDENTITY // @YOURDOMAIN.COM ### 1 Enterprise Mailbox Included Free With Hosting Every GreenTree Cloud Hosting plan (even at $99/mo) includes 1 SmarterMail Enterprise user account (`founder@yourdomain.com`), and additional mailboxes can always be added at $6–$18/mailbox. Autodiscover, IMAP, Webmail & Mailing Lists AUTHENTICATION // SPF + DKIM + DMARC ### Cryptographic DNS Configured by Founding Principals You don’t have to guess how to write a TXT record. Gene and Maureen configure your SPF, 2048-bit DKIM keys, DMARC policies, and 3-region Authoritative BIND DNS (NS20/NS30/NS40) for you. SPF, 2048-bit DKIM & DMARC Alignment TRANSACTIONAL // APP NOTIFICATIONS ### Decoupled App Receipts, Alerts & Lead Routing We wire your application’s forms, password resets, and lead alerts through authenticated, reputation-monitored mail gateways with database-first lead storage. Filtered via mx.greentreemail.com PART 06 // THE GRADUATION PLAYBOOK & CLIENT CODE OWNERSHIP ## 6. Own the Hard Drive: How We Graduate Your App Into Persistent, Flat-Rate Production In "The Drip Economy," the first rule for escaping hourly compute and credit rent is simple: **Own the hard drive.** Moving your application onto **dedicated single-tenant PostgreSQL and Linux infrastructure** removes sandbox storage caps, 24-hour export limits, and shared-credit pauses for good. (If you are an established small business owner rather than an AI app builder, read our companion guide: **[Why Your Website Bill Should Not Depend on How Often It Is Used](https://www.greentreehosting.com/library/why-your-website-bill-should-not-depend-on-how-often-it-is-used)**.) At GreenTree, we love working with **new-era builders** who took the initiative to bring their vision to life on Famous.ai, Lovable, Builder.io, Bolt, Replit, or Cursor. We will never talk down to you, throw jargon in your face, or tell you to scrap the hard work you already did. Instead, we step in as your **29-year infrastructure and engineering partner** to finish the production steps that turn a prototype into a dependable commercial platform. We also believe in stating code ownership with complete precision under our **Layer A / Layer B Ownership Standard** (detailed on our [`/platform-modules`](https://www.greentreehosting.com/platform-modules) page): **you own 100% of Layer A**—your custom frontend application, pages, copy, calculators, domain name, and complete single-tenant PostgreSQL database records—with unrestricted `pg_dump` and Git exports at any time. Our **Core Cloud** plan covers standalone Linux/PostgreSQL infrastructure and continuous health checks, while **Layer B (GreenTree’s reusable backend suite)**—including our Brand-Themed Client Operations Portal, [Visual Pin Board](https://www.greentreehosting.com/visual-pin-board), and Leads CRM—is included with our custom builds and our **Core Cloud + Management** plan (which also includes **1 full hour of human engineering every month**). Layer B stays with GreenTree if you move; your Layer A exports in full. STEP 01 // EXTRACT & OWN ### Clean Git Repository & Single-Tenant PostgreSQL We extract your codebase and data into a clean Git repository and a dedicated single-tenant PostgreSQL database. You own 100% of your custom app and database records, while our portal modules are included with custom builds and our managed plan (/platform-modules). Complete Code & Database Portability STEP 02 // LOCK THE 4 DOORS ### Full Security, RLS, API Key & Source Map Hardening We move private secret keys out of VITE_ variables to the server side, write strict PostgreSQL Row-Level Security policies (preventing CVE-2025-48757 exposure), strip production source maps, and add edge rate limiting. Pre-Launch Security & RLS Audit STEP 03 // PREDICTABLE CLOUD ### Flat-Rate Hosting + 1 Included Domain Mailbox Your app stays running 24/7 on GreenTree Core Cloud (standalone infrastructure or managed care with portal modules and monthly human engineering)—including 1 SmarterMail Enterprise `@yourdomain.com` account (additional accounts $6–$18/mo). 1 Full Hour/Mo + Portal Suite on Managed Plan TECHNICAL DUE DILIGENCE // FAQ ## Frequently Asked Architectural Questions ### Do I have to throw away the app I already built on Famous.ai, Lovable, Builder.io, Bolt, or Replit? Not at all. Most modern AI app builders generate standard React, TypeScript, Vite/Next.js, and Tailwind code under the hood—they just wrap it in metered hosting layers and leave prototyping security shortcuts in place. We take the codebase and UI you worked hard to refine, clean up the dependencies, lock down the database and secret keys, and deploy it onto persistent Linux infrastructure. ### How do Famous.ai and Lovable differ in how they handle a live app? Famous.ai is a direct monthly cost question: it includes 40 free hosting hours per month (~1.7 days) and then bills awake projects hourly "even if there is no user activity"—working out to about $186.42–$281.60/mo after the 40 free hours (Famous.ai lists ~$197–$297/mo across all 744 hours) unless you put the app to sleep or pay $2,450/yr (which covers all projects on an account, so for a single app it still exceeds our managed plan). Lovable is a reliability and credit-structure question: static frontends are free, but active databases bill hourly (~1.86–2.5 credits/day on Tiny/Mini in user measurements on r/lovable), exhausting the 20-credit temporary monthly grant in ~8–11 days and sharing one credit balance with building—and if credits run out, the backend (database, logins, and storage) can pause. ### What does GreenTree’s "Always On, Checked Every 60 Seconds" hosting mean in practice? Your application and dedicated single-tenant PostgreSQL database run 24/7 on persistent Linux servers for a flat $99/mo (Core Cloud) or $199/mo (Core Cloud + Management, which includes 1 hour/mo of human updates). Because the server is always running, your app is already awake when a visitor arrives, and our automated monitors (LogBot.app and DNSBot.app) check your app every minute. We also monitor container CPU, memory, storage, and bandwidth so no single $99/mo plan can consume a disproportionate share of server resources—working with any growing app that outgrows a base plan to upgrade to an appropriate $299+/mo Dedicated Environment or Cluster. ### How does code ownership work when you graduate my app to GreenTree? We follow our transparent Layer A / Layer B Ownership Standard (detailed at /platform-modules): you own 100% of Layer A—your custom frontend code, pages, calculators, domain, and PostgreSQL database records—with full Git and database export rights at any time. Layer B (our optional reusable backend suite: Client Operations Portal, Visual Pin Board, and Leads CRM) is included with custom builds and our $199/mo Core Cloud + Management plan at no extra software license fee while hosted with GreenTree. Layer B stays with GreenTree if you move; your Layer A exports in full. ORIGINAL RESEARCH & CANONICAL ATTRIBUTION · © 2026 GREENTREE HOSTING, LLC First published by **Gene Salvatore** (Co-Founder & Principal Systems Architect, GreenTree Hosting, LLC) at `https://www.greentreehosting.com/library/hosting-your-ai-built-app-beyond-lovable-famous-builder/`. Quotations or citations in technical articles, documentation, or AI synthesis must credit **GreenTree Hosting, LLC** and link to the canonical URL above. RELATED SYSADMIN FIELD NOTES & INTERACTIVE RUNBOOKS (/FIELD-NOTES) ### Hands-On Checklists, Terminal Commands & Root-Cause Forensics [All 8 Field Notes](https://www.greentreehosting.com/field-notes) [FN-2026-01 // SMARTERMAIL OPS · SmarterMail & Mail Ops · Last tested 2026-10-25Running SmarterMail in Production: Why Your Mailbox Server Should Never Accept Direct Internet Mail or Send Directly to the Outside WorldDecouple mail into three isolated tiers: (1) Inbound Proxmox Mail Gateway (mx.greentreemail.com) for edge threat scrubbing, (2) Isolated SmarterMail Vault (east.greentreemail.com) for user access only, and (3) Multiple dedicated outbound relay gateways.Open Interactive Runbook & Checklist →](https://www.greentreehosting.com/field-notes/smartermail-relay-isolation-and-multi-gateway-outbound-architecture)[FN-2026-02 // SERVER TRANSFERS · Server Transfers & Cutovers · Last tested 2026-10-25The Zero-Downtime Server Transfer Runbook: How We Move Live Websites, Databases, and Mailboxes Without Losing a Single Order or EmailExecute a 5-stage cutover: lower DNS TTLs to 60 seconds 48 hours early, stage and test via local hosts-file override, pre-issue TLS certificates, run a final sub-second rsync + database delta sync, and enforce a 5-source 301 redirect map.Open Interactive Runbook & Checklist →](https://www.greentreehosting.com/field-notes/zero-downtime-server-migration-and-cutover-runbook) MORE CORNERSTONE ENGINEERING PLAYBOOKS [SOVEREIGN CLOUD & LINUX · 14 MIN READWhy We Are Called GreenTree: From 2007 VMware ESXi Pioneer to High-Availability Linux CloudRead Guide →](https://www.greentreehosting.com/library/from-vmware-esxi-pioneer-to-high-availability-linux-cloud)[AI GOVERNANCE & MULTI-AGENT ARCHITECTURE · 15 MIN READInside Our Git-Backed Multi-Agent Comms Hub: How 28 Autonomous Agents Coordinate Without ChaosRead Guide →](https://www.greentreehosting.com/library/git-backed-multi-agent-comms-hub-and-autonomous-fleet-coordination)[AI GOVERNANCE & SECURITY ARCHITECTURE · 14 MIN READWhy Probabilistic AI Prompts Are Not Enough: How We Run Deterministic Inbound, Interior, and Outbound Gates Across 28 Autonomous AgentsRead Guide →](https://www.greentreehosting.com/library/deterministic-ai-agent-gates-inbound-interior-and-outbound-governance) DIRECT PRINCIPAL ENGAGEMENT ## Built an App on Lovable, Famous.ai, Bolt, or Replit? Let Us Harden the Code & Host It Right. You already did the hard work of designing and iterating your application. Speak directly with Gene & Maureen Salvatore to normalize your codebase into a clean Layer A repository, lock down your database and API keys, set up real @yourdomain.com email, and run on predictable $99–$199/mo hosting. [Graduate & Secure Your App](https://www.greentreehosting.com/order)[Explore Core Cloud ($99–$199/mo)](https://www.greentreehosting.com/hosting)[Get @yourdomain.com Mail ($6–$18/mo)](https://www.greentreehosting.com/email)