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 -->
108 lines
6.4 KiB
Plaintext
108 lines
6.4 KiB
Plaintext
---
|
|
name: Epsilon3
|
|
title: Epsilon3 digitize paper-based procedures in the space industry using telemetry data, simplifying testing and operations.
|
|
# Use meta_title to add a custom meta title. Otherwise it defaults to '{name} | Supabase Customer Stories':
|
|
# meta_title:
|
|
description: Epsilon3 uses Supabase to help teams execute secure and reliable operations in an industry where project spend runs into the billions.
|
|
# Use meta_description to add a custom meta description. Otherwise it defaults to {description}:
|
|
meta_description: Epsilon3 uses Supabase to help teams execute secure and reliable operations in an industry where project spend runs into the billions.
|
|
author: rory_wilding
|
|
author_title: Supabase
|
|
author_url: https://github.com/kiwicopple
|
|
author_image_url: https://avatars2.githubusercontent.com/u/10214025?s=400&u=c6775be2ae667e2acae3ccd347fed62bb3f5b3e7&v=4
|
|
logo: /images/customers/logos/on-light/epsilon3.png
|
|
logo_inverse: /images/customers/logos/on-dark/epsilon3.png
|
|
tags:
|
|
- supabase
|
|
date: '2023-02-14'
|
|
company_url: 'https://epsilon3.io'
|
|
stats:
|
|
[
|
|
{ stat: '00,000', label: Example stat },
|
|
{ stat: '00,000', label: Example stat },
|
|
{ stat: '00,000', label: Example stat },
|
|
]
|
|
misc: [{ label: 'Founded', text: Los Angeles, California }]
|
|
about: Epsilon3 is the OS for spacecraft and complex operations. Epsilon3's software platform manages complex operational procedures, saving operators time and reducing errors.
|
|
# "healthcare" | "fintech" | "ecommerce" | "education" | "gaming" | "media" | "real-estate" | "saas" | "social" | "analytics" | "ai" | "developer-tools"
|
|
industry: ['saas', 'developer-tools']
|
|
# "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', 'realtime', 'auth']
|
|
---
|
|
|
|
Epsilon3 is a USA-based Y Combinator startup. They digitize paper-based procedures in the space industry using telemetry data,
|
|
simplifying testing and operations. Their product is rapidly becoming the OS for space projects and complex operations.
|
|
|
|
## Space Operations
|
|
|
|
Epsilon3's customers run testing and operational procedures in real-time. Epsilon3's solution allows online collaboration as a team,
|
|
instead of being siloed and separated which is an increasingly important requirement in a post-pandemic working world.
|
|
Epsilon3 is powering an industry where reliability is paramount. In the space industry, missions cost billions and need to run reliably.
|
|
|
|

|
|
|
|
Epsilon3's software saves operators time and reduces errors to improve complex operations. Their customers are using their software and
|
|
successfully sending satellites into space and are about to use Epsilon3's software for an operational Rocket Launch. As a result, their
|
|
reputation for improving the quality standard for complex operations has led to demand from other industries. The team is receiving
|
|
enquiries from clients in the robotics, logistics and medical equipment sectors who need a structured and standardized way of running
|
|
procedures and keeping audit trails.
|
|
|
|
## Moving fast in regulated markets
|
|
|
|
As a startup, Epsilon3 needs to move fast and scale. They require security, reliability, and performance.
|
|
|
|
The team has a background in engineering from Northrop, Google, and SpaceX and understands the technical benefits Postgres offers as a
|
|
battle-tested open-source relational database.
|
|
|
|
Real-time functionality is also a key for their customers to see how running procedures are progressing as the changes occur.
|
|
|
|
The space industry is highly regulated, adding complexity. For example, in the USA, deployments must be in an ITAR-compliant way
|
|
(for instance AWS GovCloud supports ITAR compliance) while customers in countries outside the USA may need to host their data within their own
|
|
country. These customer requirements mean Epsilon3 must be able to offer flexible hosting options, including on-premises deployment.
|
|
|
|
<Quote
|
|
img="aaron-epsilon3.png"
|
|
caption="Aaron Sullivan, ex-Google engineer, Stanford University Alumni, Principal Software Engineer Epsilon3."
|
|
>
|
|
<p>Billion dollar missions need to run reliably and securely.</p>
|
|
<p>
|
|
We didn't just want something that works, we wanted a solution implementing best practices. We
|
|
also needed a setup that we could self-host to meet compliance needs and allow on-premises
|
|
deployment options for our customers.
|
|
</p>
|
|
<p>
|
|
We use Supabase because they give us an open-source scalable back-end built by database experts
|
|
that we can self-host.
|
|
</p>
|
|
<p>
|
|
Supabase takes out the mental effort from our back-end infrastructure so we can focus on our
|
|
customers needs.
|
|
</p>
|
|
</Quote>
|
|
|
|
## Supabase gives Postgres users superpowers
|
|
|
|
The team implemented a self-hosted Supabase setup. They use AWS with a self-hosted Supabase API powering an RDS Postgres instance.
|
|
This setup gives a balance of rapid development, reduced DevOps, and flexible hosting options. As Supabase uniquely offers [real-time](https://supabase.com/realtime) for
|
|
Postgres, it allows their customers to see updates from running procedures. Supabase offers well-supported client libraries that make
|
|
Postgres Row Level Security easy to use, which is a critical item on the Epsilon3 roadmap.
|
|
|
|
All this was easy for the team to set up, even with self-hosting, so the team was able to focus on what they do best—helping their customers
|
|
run complex operations smoothly. With this implementation, Epsilon3 gets all the benefits of Postgres, plus the smooth developer experience and
|
|
support that Supabase is known for, without compromising their compliance needs.
|
|
|
|

|
|
|
|
## Self-hosted Supabase, a superpower
|
|
|
|
Self-hosting Supabase allows the crew at Epsilon3 to move fast. They are revolutionizing space operations securely and reliably in real-time whilst
|
|
staying compliant. The team is now seeing demand from other industries and is confident in their scaling capability because they know it's
|
|
just Postgres under the hood.
|
|
|
|
Check out the [Epsilon3 website](https://www.epsilon3.io/) to learn more about the team and their OS for space operations. If you are interested
|
|
in self-hosting Supabase then you can **[contact us](https://forms.supabase.com/enterprise)** to learn more.
|