Files
supabase/apps/www/_customers/lovable.mdx
Danny White 2e7a8a3362 chore(www): rename customer logo folders to on-dark and on-light (#48962)
## What kind of change does this PR introduce?

Chore: rename customer logo folders and document the theme contract. No
intended visual change, aside from Phoenix Energy whose two marks were
in the wrong folders.

## What is the current behavior?

Customer logos live at:

- `/images/customers/logos/{slug}.png` (`logo`, light mode)
- `/images/customers/logos/light/{slug}.png` (`logo_inverse`, dark mode)

`light/` actually means “use me on a dark background”.

## What is the new behavior?

Same assets, clearer paths:

- `/images/customers/logos/on-light/{slug}.png` → dark/black mark →
`logo` → light mode
- `/images/customers/logos/on-dark/{slug}.png` → light/white mark →
`logo_inverse` → dark mode

Icon chips stay at `/images/customers/logos/{slug}-icon.svg`. Old
`/images/customers/logos/light/*` URLs redirect to `on-dark`. www README
now has the contract.

# To test

Use the [www
preview](https://zone-www-dot-com-git-dnywh-chorecustomer-logo-o-0d7bc1-supabase.vercel.app).
Toggle light/dark from the site header on each page. Logos should stay
readable (no white-on-white or black-on-black).

1. [Customers
grid](https://zone-www-dot-com-git-dnywh-chorecustomer-logo-o-0d7bc1-supabase.vercel.app/customers)
— main `logo` / `logo_inverse` surface. Spot-check Juniver, Phoenix
Energy, and one other card.
2. [Phoenix Energy
story](https://zone-www-dot-com-git-dnywh-chorecustomer-logo-o-0d7bc1-supabase.vercel.app/customers/phoenix-energy)
— story header uses `logo` only (on-light, plus a dark-mode brightness
filter). We swapped this pair.
3.
[Homepage](https://zone-www-dot-com-git-dnywh-chorecustomer-logo-o-0d7bc1-supabase.vercel.app/)
— “How industry leaders…” section. Icon chips only (`*-icon.svg`); the
wordmark `logo` field is unused here.
4. [Solutions /
Agents](https://zone-www-dot-com-git-dnywh-chorecustomer-logo-o-0d7bc1-supabase.vercel.app/solutions/agents)
— Chatbase quote near the top shows both theme variants. Same pattern on
[/healthcare](https://zone-www-dot-com-git-dnywh-chorecustomer-logo-o-0d7bc1-supabase.vercel.app/solutions/healthcare),
[/finserv](https://zone-www-dot-com-git-dnywh-chorecustomer-logo-o-0d7bc1-supabase.vercel.app/solutions/finserv),
and
[/b2b-saas](https://zone-www-dot-com-git-dnywh-chorecustomer-logo-o-0d7bc1-supabase.vercel.app/solutions/b2b-saas).
5. [Contact
sales](https://zone-www-dot-com-git-dnywh-chorecustomer-logo-o-0d7bc1-supabase.vercel.app/contact/sales)
— Good Tape / Xendit / Chatbase wordmarks (`on-light`). Same logos on
the demo form at
[/solutions/enterprise](https://zone-www-dot-com-git-dnywh-chorecustomer-logo-o-0d7bc1-supabase.vercel.app/solutions/enterprise).
6.
[Enterprise](https://zone-www-dot-com-git-dnywh-chorecustomer-logo-o-0d7bc1-supabase.vercel.app/solutions/enterprise)
— Mozilla / Epsilon3 / Pebblely icons in the use-cases section
(`on-dark`).
7.
[Vector](https://zone-www-dot-com-git-dnywh-chorecustomer-logo-o-0d7bc1-supabase.vercel.app/modules/vector)
— customer quotes. This is the only page that builds `on-light` /
`on-dark` paths at runtime from the customer slug.
8. [Mobbin
event](https://zone-www-dot-com-git-dnywh-chorecustomer-logo-o-0d7bc1-supabase.vercel.app/events/migrating-from-firebase-mobbin)
— company logo uses event `logo` / `logo_light` (dark vs light).
Optional second:
[/events/scale-to-millions-goodtape-auth](https://zone-www-dot-com-git-dnywh-chorecustomer-logo-o-0d7bc1-supabase.vercel.app/events/scale-to-millions-goodtape-auth).

Quick extra: hover **Product** in the site nav. The customer story
thumbnail uses `imgUrl` (`on-light`).

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

## Documentation
- Clarified customer logo requirements, including separate light and
dark asset locations, monochrome formats, and dark PNG assets for image
generation.

## Updates
- Standardized customer logos across stories, events, sales pages,
solution pages, testimonials, and generated images.
- Improved logo rendering across light and dark themes with dedicated
variants.
- Added permanent redirects for legacy logo URLs while preserving
filename suffixes.

## Tests
- Added coverage verifying legacy logo redirects resolve correctly,
including supported exceptions.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
2026-08-12 03:49:21 +00:00

131 lines
8.6 KiB
Plaintext

---
name: Lovable
title: How Supabase helps power millions of apps on Lovable
# Use meta_title to add a custom meta title. Otherwise it defaults to '{name} | Supabase Customer Stories':
# meta_title:
description: Lovable lets anyone create software by describing it. Behind many of the one million projects people create on Lovable every week is a Supabase backend, provisioned end to end through the Management API.
# Use meta_description to add a custom meta description. Otherwise it defaults to {description}:
meta_description: How Lovable gives every AI-generated app a complete Supabase backend, database, auth, storage, edge functions, realtime, and cron, all through the Management API, for solo builders and enterprises alike.
author: prashant
author_title: Prashant Sridharan
author_url: https://github.com/CoolAssPuppy
author_image_url: https://avatars.githubusercontent.com/u/914007?v=4
logo: /images/customers/logos/on-light/lovable.png
logo_inverse: /images/customers/logos/on-dark/lovable.png
tags:
- supabase
date: '2026-07-09'
company_url: https://lovable.dev
misc:
- { label: 'Company size', text: 'Fast-growing startup' }
- { label: 'Use case', text: 'Backend infrastructure for AI-generated applications' }
- {
label: 'Products used',
text: 'Postgres, Auth, Storage, Edge Functions, Realtime, Cron, Management API',
}
about: "Lovable is one of the world's fastest-growing startups. Its mission is simple: let anyone create software. You describe what you want, and Lovable builds it, turning ideas into a web app or a real business. People create one million new projects on Lovable every week, and behind many of them is a Supabase backend."
# "healthcare" | "fintech" | "ecommerce" | "education" | "gaming" | "media" | "real-estate" | "saas" | "social" | "analytics" | "ai" | "developer-tools"
industry: ['ai', 'developer-tools']
# "startup" | "enterprise" | "indie_dev"
company_size: 'startup'
# "Asia" | "Europe" | "North America" | "South America" | "Africa" | "Oceania"
region: 'Europe'
# "database" | "auth" | "storage" | "realtime" | "functions" | "vector"
supabase_products: ['database', 'auth', 'storage', 'functions', 'realtime']
---
<Quote img="bryan-byrne-lovable.jpeg" caption="Bryan Byrne, Product Manager, Lovable">
Lovable is about unlocking creativity for anyone. Only 1% of the population knows how to code.
Lovable has unlocked that ability for the other 99%.
</Quote>
[Lovable](https://lovable.dev) is one of the world's fastest-growing startups. Its mission is simple: let anyone create software. People come to Lovable, talk to Lovable, and turn their ideas into a web app or even a real business. You describe what you want. Lovable builds it. [People create one million new projects on Lovable every week](https://thebuildeconomy.lovable.app/). Behind many of these projects is a Supabase backend.
<Quote img="bryan-byrne-lovable.jpeg" caption="Bryan Byrne, Product Manager, Lovable">
Out of the box, Lovable gets a complete backend from Supabase. Everything from the database to
file storage to backend compute. It unlocked the whole suite of backend capabilities our
Lovable-built applications need.
</Quote>
## The challenge: a frontend with no backend
Lovable started by building websites as single-page applications. These run in the user's browser. They are fast to prototype but have limitations. You can build a nice page where everything lives in code. But a real business needs more: a database, file storage, a place to run server code, and a way to keep data safe.
By the end of 2024, Lovable needed all of it. The team was about ten people, so the search began for a partner to bet on.
<Quote img="aleksei-petrov-lovable.jpeg" caption="Aleksei Petrov, Lead Engineer, Lovable">
It was not an option to start building something in-house at the time. So it was all about finding
the right partner and betting on them.
</Quote>
## Why Lovable chose Supabase
Lovable did not go looking for a database. It went looking for a whole backend. In January 2025, it integrated with Supabase. The fit was simple. One vendor gave Lovable everything its apps needed, all through an API. That let a ten-person team ship a full backend without building one, and Supabase has helped power Lovable's growth ever since.
<Quote img="aleksei-petrov-lovable.jpeg" caption="Aleksei Petrov, Lead Engineer, Lovable">
Why Supabase? It's not just about Postgres. It's about the whole package. It powers your app with
the backend functionality you need: storage, a database, and the runtime where you run your
backend.
</Quote>
## The solution: one API for millions of projects
When someone builds on Lovable, they never ask for a database. They describe their idea. Lovable decides what the app needs and creates it. It spins up the project, builds the tables and storage buckets, writes the security policies, and deploys edge functions. Even the logs flow back the same way. All of it runs through the Supabase Management API.
Lovable uses nearly every Supabase service on top of it: Postgres, Auth, Storage, Edge Functions, Realtime for live updates, and Cron for scheduled jobs. Because each piece is modular and API-first, Lovable can combine them in any way a project requires.
<Quote img="aleksei-petrov-lovable.jpeg" caption="Aleksei Petrov, Lead Engineer, Lovable">
The Management API is the core of everything. We use it for about 90% of our interactions with
Supabase.
</Quote>
## Enterprise, handled
Lovable serves enterprises as well as solo builders. Enterprises bring stricter rules: where data lives, who can see it, and how it is audited. Data residency is one example. An enterprise admin can require that every project their team creates lives in a specific region, and Supabase makes that a single setting. The same foundation supports audit logging, user provisioning, and single sign-on. Enterprise teams use Lovable to build internal tools, connect to their own data warehouses, and run analysis on their own systems.
<Quote img="bryan-byrne-lovable.jpeg" caption="Bryan Byrne, Product Manager, Lovable">
Some enterprises have compliance requirements that all their data has to live in a specific
region. Supabase made that very straightforward, and it accelerated our enterprise capabilities.
</Quote>
## Boring on purpose
Supabase handles the backend so Lovable can spend its time on the one thing only Lovable can do: help anyone turn an idea into a working app. The team wants infrastructure they never have to think about. A boring product that just works beats an exciting one that wakes you up at night.
<Quote img="bryan-byrne-lovable.jpeg" caption="Bryan Byrne, Product Manager, Lovable">
Infrastructure should be boring. You want infrastructure you never think about, because it just
works.
</Quote>
## Lovable runs Lovable on Supabase
The team builds its own tools on Lovable, and each one runs on a Supabase project. Everything from the org chart to the company roadmap lives there. So does the iPad app at the front desk that checks in office guests.
<Quote img="aleksei-petrov-lovable.jpeg" caption="Aleksei Petrov, Lead Engineer, Lovable">
We never bought software for that. We just used Lovable and Supabase to create it, and it's used
daily here.
</Quote>
## Security as a first principle
Lovable and Supabase think about security on behalf of their users. Supabase Row Level Security gives every project a foundation for keeping data private, so apps are secure by default. On top of that, Lovable recently shipped a security scanner that checks every project, flags issues, and lets users fix them for free.
<Quote img="bryan-byrne-lovable.jpeg" caption="Bryan Byrne, Product Manager, Lovable">
We take security very seriously. It's a first principle. We provide a free security scanner for
every project and users can address any issues the scanner finds for free.
</Quote>
## What's next: build, run, grow
Lovable wants to be there for the whole life of a business, not just the first build. It recently launched SEO and answer engine optimization tooling so the apps people build get found by search engines and AI platforms. More enterprise connectors and controls are on the way. Through all of it, Supabase stays the backend underneath.
<Quote img="bryan-byrne-lovable.jpeg" caption="Bryan Byrne, Product Manager, Lovable">
We want to be your co-founder as you grow your business. You build your project on Lovable, you
run it, and you grow it. Behind the scenes, Supabase is powering that.
</Quote>
<Quote img="bryan-byrne-lovable.jpeg" caption="Bryan Byrne, Product Manager, Lovable">
Supabase is there with the backend we need, enabling Lovable to focus on what we do best: helping
anyone turn an idea into a real business.
</Quote>