mirror of
https://github.com/supabase/supabase.git
synced 2026-10-05 09:25:06 +03:00
## 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 -->
112 lines
6.1 KiB
Plaintext
112 lines
6.1 KiB
Plaintext
---
|
||
name: Euka
|
||
title: 'Euka used Supabase to unlock faster growth'
|
||
# Use meta_title to add a custom meta title. Otherwise it defaults to '{name} | Supabase Customer Stories':
|
||
# meta_title:
|
||
description: Supabase helped Euka accelerate development, simplify AI feature rollout, and scale creator marketing faster than ever. A Postgres-based platform gave them the structure, speed, and flexibility they needed to grow.
|
||
# Use meta_description to add a custom meta description. Otherwise it defaults to {description}:
|
||
meta_description: Discover how Supabase helped Euka accelerate development.
|
||
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/euka.png
|
||
logo_inverse: /images/customers/logos/on-dark/euka.png
|
||
tags:
|
||
- supabase
|
||
date: '2025-04-29'
|
||
company_url: https://www.euka.ai
|
||
stats: [{ stat: '00,000', label: Example stat }]
|
||
misc: [{ label: 'Founded', text: 'Canada' }]
|
||
about: Turning TikTok affiliates into a revenue-generating engine.
|
||
# "healthcare" | "fintech" | "ecommerce" | "education" | "gaming" | "media" | "real-estate" | "saas" | "social" | "analytics" | "ai" | "developer-tools"
|
||
industry: ['media', 'social']
|
||
# "startup" | "enterprise" | "indie_dev"
|
||
company_size: 'startup'
|
||
# "Asia" | "Europe" | "North America" | "South America" | "Africa" | "Oceania"
|
||
region: 'North America'
|
||
# "database" | "auth" | "storage" | "realtime" | "functions" | "vector"
|
||
supabase_products: ['database', 'auth', 'storage', 'functions', 'vector']
|
||
---
|
||
|
||
<Quote img="kevin-wang-euka.jpeg" caption="Kevin Wang, CTO and Co-Founder, Euka">
|
||
Supabase gave us the tools we needed to move fast, scale quickly, and stay flexible as we grow —
|
||
all without the heavy lifting.
|
||
</Quote>
|
||
|
||
Euka is reimagining how brands scale their presence on social media. Their AI-powered platform helps businesses find, manage, and scale creator partnerships, primarily on TikTok Shop. By automating the most time-consuming parts of user-generated content (UGC) campaigns, Euka allows brands to build awareness and drive sales faster than ever before.
|
||
|
||
As they expanded beyond ecommerce into SaaS and consumer software, Euka needed a backend platform that could scale with them without slowing them down.
|
||
|
||
## The challenge
|
||
|
||
Euka’s vision required a backend that could support rapid iteration, structured data analytics, seamless AI integration, and scalable storage. To succeed, Euka needed:
|
||
|
||
- A relational database that supported structured queries.
|
||
- Integrated services like authentication, storage, and AI search.
|
||
- A platform that scaled easily as their business grew.
|
||
- A developer-first experience to enable faster shipping.
|
||
|
||
## Choosing Supabase
|
||
|
||
When it came time to choose a permanent foundation for the business, Kevin recalled a side project where Supabase had impressed him with its simplicity and speed. This time, for Euka, it was not just about familiarity. It was about finding the right platform to unlock their next phase of growth.
|
||
|
||
Supabase provided everything they needed in one place:
|
||
|
||
- A fully managed Postgres database with standard SQL support.
|
||
- Built-in authentication, storage, edge functions, and vector search.
|
||
- Native AI features like pgvector for semantic search.
|
||
- An intuitive dashboard and first-class developer experience.
|
||
|
||
<Quote img="kevin-wang-euka.jpeg" caption="Kevin Wang, CTO and Co-Founder, Euka">
|
||
It just worked. Supabase gave us a zero-to-one experience that let us build quickly without
|
||
worrying about the backend.
|
||
</Quote>
|
||
|
||
Supabase allowed the team to move faster without compromising on performance or scalability. It also future-proofed their stack for AI development without needing costly rewrites later.
|
||
|
||
## How Euka built with Supabase
|
||
|
||
Euka’s architecture focuses on simplicity and rapid iteration. They designed their system to get the most out of Supabase while maintaining flexibility for future growth.
|
||
|
||
Their stack includes:
|
||
|
||
- **Frontend**: Two Next.js apps deployed on Vercel, one for brands and one for creators.
|
||
- **Backend**: Python scripts for data scraping, trend analysis, and creator search, connected directly to Supabase.
|
||
- **Storage**: Supabase Storage for managing creator profile pictures, videos, and ecommerce product images.
|
||
- **Authentication**: Supabase Auth with ongoing fine-tuning around OAuth flows.
|
||
- **AI search**: Supabase’s `pgvector` extension for trending video discovery, using cosine similarity searches.
|
||
|
||
<Quote img="kevin-wang-euka.jpeg" caption="Kevin Wang, CTO and Co-Founder, Euka">
|
||
Setting up the database and storage was one of the easiest parts of building our MVP.
|
||
</Quote>
|
||
|
||
Supabase’s dashboard also became a powerful internal tool. Engineers could debug quickly by inspecting real-time logs and queries. Non-technical teams like marketing and sales used the dashboard to run simple queries, inspect user data, and export reports without needing custom-built admin panels.
|
||
|
||
## The results
|
||
|
||
Since launching on Supabase, Euka has accelerated every part of their development lifecycle. They can build quickly and are able to deliver new AI capabilities faster than expected.
|
||
|
||
<Quote img="kevin-wang-euka.jpeg" caption="Kevin Wang, CTO and Co-Founder, Euka">
|
||
With Supabase, we saw an immediate lift in developer velocity. Engineers can iterate on features
|
||
much faster by writing Postgres SQL queries.
|
||
</Quote>
|
||
|
||
Supabase helped Euka achieve:
|
||
|
||
- Faster developer cycles by standardizing on SQL.
|
||
- Easier scaling through integrated, high-performance services.
|
||
- Simplified AI expansion using `pgvector` and seamless embedding storage.
|
||
- Greater internal collaboration through an intuitive, accessible dashboard.
|
||
|
||
Supabase gave Euka a faster way to ship, a stronger foundation for AI growth, and a platform that can evolve alongside them as they expand into new industries.
|
||
|
||
<Quote img="kevin-wang-euka.jpeg" caption="Kevin Wang, CTO and Co-Founder, Euka">
|
||
Honestly, it’s a no-brainer these days. If you’re starting something new and need structured data,
|
||
Supabase is the obvious choice.
|
||
</Quote>
|
||
|
||
## Ready to build and scale with Supabase?
|
||
|
||
Start your journey today at [www.supabase.com](/)
|