# Lovable App Case Studies: 6 Real Builds Source: https://www.plutonapps.com/work Updated 2026-10-28. **Our clients decide what to build. We build it for real and keep it running.** ## AquaLog Live in production at aqualog.space. An aquarium logbook for people who keep fish: tanks and cleanings, a journal of every fish, water tests, what the hobby costs, the store room and reminders, in one calm app that still works with no signal. It began in Lovable from its founder's brief. We engineered what sits underneath: reminders that follow each keeper's own day, one model for money in any currency, a database that refuses impossible values and walls each keeper's records off, and an admin console whose audit log cannot be rewritten. **What the client made:** The founder's brief, built first in Lovable: screens for tanks and cleanings, fish, finances and the store room, for a keeper with many aquariums. **What we engineered and run:** - **Dates & money:** Reminders follow each keeper's own time zone and real calendar months, and every amount carries its currency, with one linked expense per costed record. - **Access:** Row-level security on every table of the first schema, default function grants revoked, and every value limit enforced by the database. - **Operations:** An admin console whose audit log cannot be rewritten, and an app that stays readable offline and holds changes until it reconnects. [AquaLog technical blueprint](https://www.plutonapps.com/work/aqualog) ## Bell Pre-launch. An AI email assistant for Gmail. Its assistant, Bella, sorts the inbox, works out what each email is asking of you and drafts the reply, in chat or by voice. The founder designed it in Lovable. We rebuilt everything underneath: a ledger that sends each email exactly once with a two-minute undo, a database that refuses any send no person approved, AI that treats every email as hostile, hard daily limits on AI spend, and a Gmail connection that can read and send, and do nothing else. **What the client made:** The founder designed Bell in Lovable: the inbox, Bella in chat and by voice, the Solve conversation that works through an email, and the Feed for everything that can wait. **What we engineered and run:** - **Sending:** One ledger sends every email exactly once, with a two-minute undo, and the database refuses any send no person approved. - **AI safety:** Every email is treated as hostile input, and every model call passes a kill switch, a per-person daily limit and a circuit breaker. - **Access & privacy:** Gmail access limited to read and send, each mailbox walled off at one server boundary, and a deleted account's stored mail purged. [Bell technical blueprint](https://www.plutonapps.com/work/bell) ## Inkwave Pre-launch. An all-in-one newsletter and publishing platform for creators, journalists and organizations: an editor, a website builder, subscribe forms, referrals, paid subscriptions, sponsorships and analytics in one dashboard. The founder brought it to us with a Lovable-built site that promised all of it. We built the platform that keeps those promises: one monorepo of fourteen apps and packages, newsletters that are never sent twice, every publisher on their own domain, and analytics without cookies. **What the client made:** The founder shaped Inkwave's public face in Lovable: the landing page, the pricing and a page for each of twenty platform features. The product behind those promises had to be built to keep them. **What we engineered and run:** - **Sending & sites:** Newsletters sent as a durable workflow in batches of 100 that a retry never re-sends, and every publisher on their own domain, with certificates issued only after a fail-closed check. - **Data & analytics:** 100 PostgreSQL tables under versioned migrations, and cookieless analytics batched into ClickHouse with 18-month retention. - **Trust & control:** Every write scoped to the caller's publication, an append-only operator audit log, and an AI-assistant server that can only touch the publication it was granted. [Inkwave technical blueprint](https://www.plutonapps.com/work/inkwave) ## Looph Live in production at looph.ing. Customer-feedback software: public boards where customers post and vote on ideas, a roadmap that shows what is being built, and a changelog that tells everyone who asked when it ships. The founder shaped it in Lovable. We rebuilt everything underneath it, and it is live in production. **What the client made:** The founder shaped Looph in Lovable: public feedback boards with voting, a roadmap and a changelog, a rewards engine, automations, integrations and a browser extension. **What we engineered and run:** - **Isolation:** Row-level security on all 172 database tables, with 1,180 policies deciding what each browser, API key and AI agent may read or write. - **Reach:** Every workspace on its own subdomain or the customer's own domain, with certificates issued automatically and visitors kept signed in there. - **Agents & ops:** An MCP server that lets AI assistants act only as far as the person who connected them may, and an operator console in an app of its own. [Looph technical blueprint](https://www.plutonapps.com/work/looph) ## Ripply Pre-launch. A viral waitlist platform in two halves: a launch builder any brand can use — pick a template, make it theirs, go live on their own web address, no code, no designer, no wait — and a private console the founder runs the whole business from: payments, refunds, support, incidents and the audit trail. He designed both halves in Lovable on our Starter plan. We built everything underneath — a queue that cannot collide, rewards that go out exactly once as gift cards, merchandise or shop codes, wallet passes for the front of the line, and thirty-day erasure when someone asks to be forgotten. **What the client made:** The founder designed both halves in Lovable: the no-code waitlist builder brands use, and the private console he runs the whole business from. **What we engineered and run:** - **Queue & rewards:** Atomic positions stress-tested with 25,000 synthetic entries, and four locks so no gift card, parcel or shop code is ever sent twice. - **Reach:** Each brand's own web address with certificates issued automatically, plus shop codes kept in step with Shopify, WooCommerce, Wix and WordPress. - **Trust & control:** A founder's console behind a hidden door with second-factor checks, and thirty-day erasure that leaves the audit trail intact. [Ripply technical blueprint](https://www.plutonapps.com/work/ripply) ## Zulu Pre-launch. This case study covers the system Plutonapps rebuilt under the client's screens: one workspace walled off from the next, booking times that hold across daylight saving, a transcript written once, and links nobody can forge. **What the client made:** The client brought a working prototype of the whole workspace: meetings and rooms, events, booking pages, forms and contacts. We kept its screens and navigation and rebuilt everything underneath. **What we engineered and run:** - **Tenancy:** Every query is scoped to one workspace, and a test sweeps all 67 workspace-scoped tables to prove no tenant can read or write another's rows. - **Bookings:** Availability worked out in the database's own time-zone rules, a hold locked per host schedule, and one confirmed booking per slot. - **Links & secrets:** One signer for every signed link the product mints, keys that rotate without an outage, and a server that will not boot on a missing secret. [Zulu technical blueprint](https://www.plutonapps.com/work/zulu)