mirror of
https://github.com/supabase/supabase.git
synced 2026-10-16 14:49:10 +03:00
update placeholder case studies
This commit is contained in:
Jonathan Summers-Muir committed
1 parent
d7e9531ca1
commit
c53fcdaf01
14 files changed
+289
-251
No files matched your search
@@ -0,0 +1,97 @@
|
||||
---
|
||||
title: Epsilon3
|
||||
description: Two months of building
|
||||
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
|
||||
authorURL: https://github.com/kiwicopple
|
||||
logo: /images/case-studies/logos/epsilon3.png
|
||||
tags:
|
||||
- supabase
|
||||
date: '28-10-2020'
|
||||
company_url: 'https://epsilon3.io'
|
||||
stats:
|
||||
[
|
||||
{ stat: '20,000', label: Number of employees },
|
||||
{ stat: '10', label: Number of offices },
|
||||
{ stat: '$1M', label: Annual revenue },
|
||||
]
|
||||
misc: [{ label: 'Founded', text: San Francisco }]
|
||||
about: Vercel combines the best developer experience with an obsessive focus on end-user performance. Our platform enables frontend teams to do their best work.
|
||||
---
|
||||
|
||||
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.
|
||||
|
||||
Learn how the team at Epsilon3 uses Supabase to help teams execute secure and reliable operations in an industry where project
|
||||
spend runs into the billions.
|
||||
|
||||
### 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 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** to learn more.
|
||||
@@ -0,0 +1,91 @@
|
||||
---
|
||||
title: Mobbin
|
||||
description: Two months of building
|
||||
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
|
||||
authorURL: https://github.com/kiwicopple
|
||||
logo: /images/case-studies/logos/mobbin.png
|
||||
tags:
|
||||
- supabase
|
||||
date: '28-10-2020'
|
||||
company_url: 'https://mobbin.design'
|
||||
stats: [{ stat: '30,000', label: Users at launch }, { stat: '200,000', label: Current users }]
|
||||
misc: [{ label: 'Founded', text: San Francisco }]
|
||||
about: Vercel combines the best developer experience with an obsessive focus on end-user performance. Our platform enables frontend teams to do their best work.
|
||||
---
|
||||
|
||||
Learn how Mobbin migrated 200,000 users from Firebase for a better authentication experience.
|
||||
|
||||
Mobbin helps over 200,000 creators globally search and view the latest design patterns from well-known apps.
|
||||
Their platform allows creators to search screenshots of mobile apps to inspire product development.
|
||||
Creators use Mobbin to combine inspiration and develop new experiences.
|
||||
|
||||
## From Idea to 30,000 users in one Product Hunt launch
|
||||
|
||||
The initial concept for Mobbin was just a Dropbox full of screenshots. After sharing with their early users,
|
||||
the team tried organizing them into folders but this quickly became unscalable. Clear interest from users encouraged them to build a full website. They used Firebase for the backend and launched on
|
||||
[Product Hunt](https://www.producthunt.com/posts/mobbin-1).
|
||||
|
||||
Mobbin went viral, and within the first week they had 30,000 users. In just over two years, they have grown to over 200,000
|
||||
registered users through word of mouth. Their curation continues to attract designers and creators globally.
|
||||
|
||||
|
||||
|
||||
## Scaling issues put Mobbin growth at risk
|
||||
|
||||
Firebase helped the team launch quickly, but at scale, they found Firebase lacked the functionality required for a high-quality user experience.
|
||||
|
||||
The first problem was duplicate user logins. Firebase Authentication doesn't automatically merge users with the same email address.
|
||||
For example, users cannot log in with Google and Facebook if they share the same email address.
|
||||
Users struggled to upgrade to a paid account because they couldn't remember which authentication provider they signed up with.
|
||||
|
||||
Next, they had issues with data integrity. While Firebase has 99.95% uptime, application code can (and does) fail.
|
||||
Mobbin didn't want to implement idempotence for every mutative Firebase Function. Between a failed Function execution and a retry,
|
||||
a document state might change without strict validation. The team could never be confident their data had the level of integrity they required.
|
||||
|
||||
Finally, the team grew concerned with their increasing Firebase bill. Because of the document-based data structure,
|
||||
their API requests required several round trips. At one point, they were making 5 million API requests per month.
|
||||
These round trips made their website slow and led to a notable time investment hacking together a fix.
|
||||
|
||||
|
||||
|
||||
## Migrating to Supabase
|
||||
|
||||
Mobbin's initial product gave them a comprehensive understanding of customer requirements. For their second version,
|
||||
they needed a better authentication experience, fairer pricing, and a relational database to deliver a quality
|
||||
application sustainable for their business model.
|
||||
|
||||
The team found Supabase and realized it covered all the bases. Not only that, their team had experience with the
|
||||
tools open source tools that Supabase is built with.
|
||||
|
||||
Auth, built using [GoTrue](https://github.com/supabase/gotrue), instantly solved their users' login issues.
|
||||
Under the hood, Supabase is just Postgres, and Jian Jie (co-founder and CTO of Mobbin) knows this is one of the best battle-tested
|
||||
open source relational databases.
|
||||
|
||||
They decided that moving to Supabase was a no-brainer. The process itself was smooth - the real challenge was validating their
|
||||
data integrity due to historical failures on their serverless functions.
|
||||
|
||||
Mobbin is now successfully running on top of Supabase, with superior performance compared to their old Firebase setup.
|
||||
Because Supabase does not charge based on API requests, Mobbin significantly reduced their monthly spending without maintaining a custom backend.
|
||||
|
||||
<Quote img="jian-mobbin.jpg" caption="Jian Jie Liau, Co-founder and CTO at Mobbin.">
|
||||
<p>Migrating to Supabase meant that we could instantly fix our Auth problems and save money.</p>
|
||||
<p>
|
||||
Just being on Supabase alone gives us confidence we can deliver on whatever users need in the
|
||||
future.
|
||||
</p>
|
||||
<p>
|
||||
The cool thing is now we know under the hood it's just Postgres, it really does feel like
|
||||
anything is possible for the future of our product
|
||||
</p>
|
||||
</Quote>
|
||||
|
||||
## Supabase saves Mobbin time and money
|
||||
|
||||
Migrating to Supabase helped the team at Mobbin instantly improve the end-user experience and save costs.
|
||||
They now add new features with confidence, and they continue to help creators all over the globe find inspiration for their next project.
|
||||
You can [check out Mobbin on their website](https://mobbin.design/browse/ios/apps).
|
||||
|
||||
Sign up to Supabase's free tier and set up a scalable backend in less than 2 minutes.
|
||||
@@ -0,0 +1,84 @@
|
||||
---
|
||||
title: Replenysh
|
||||
description: Two months of building
|
||||
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
|
||||
authorURL: https://github.com/kiwicopple
|
||||
logo: /images/case-studies/logos/replenysh.png
|
||||
tags:
|
||||
- supabase
|
||||
date: '28-10-2020'
|
||||
company_url: https://replenysh.com/
|
||||
stats:
|
||||
[
|
||||
{ stat: '20,000', label: Number of employees },
|
||||
{ stat: '10', label: Number of offices },
|
||||
{ stat: '$1M', label: Annual revenue },
|
||||
]
|
||||
misc: [{ label: 'Founded', text: San Francisco }]
|
||||
about: Vercel combines the best developer experience with an obsessive focus on end-user performance. Our platform enables frontend teams to do their best work.
|
||||
---
|
||||
|
||||
Replenysh connects brands who want to recover their products and packaging with communities looking to monetize used materials.
|
||||
|
||||
Learn how Replenysh uses Supabase to power the circular economy, redefining how brands interact with their customers & products.
|
||||
|
||||
## Material recovery offers brands a new way to connect to their customers
|
||||
|
||||
At the end of a linear economy, products usually end up in landfills or the ocean. Every year, 8 million metric tons of plastics enter our ocean. This is on top of the estimated 150 million metric tons that currently circulate our marine environments. In the USA alone, every year, 139 million tons of waste is sent to landfills.
|
||||
|
||||
The problem is our current waste and recycling infrastructure can't support that demand. With less than 10% of material actually getting recycled, the vast majority just ends up in a landfill or as pollution.
|
||||
|
||||
Replenysh is building a solution to this problem by creating entirely new infrastructure to help brands get their materials back. They're building an ecosystem of tools to enable any community in the world to do the right thing.
|
||||
|
||||
Whenever material is dropped off at a host, brands have the opportunity to engage with that person, resulting in a win-win situation for the planet, the brands, and the individual who all want to make a positive impact. Anyone in the community can take their used products and materials to the hosts — with that material being tracked all the way back to the brands and manufacturers who will reuse it. Brands have the opportunity to engage with that person, resulting in a win-win situation for the planet, the brands, and the individual who all want to make a positive impact. This turns a traditional consumption model into an opportunity for brands and customers to participate in the circular economy.
|
||||
|
||||
Brands are adopting Replenysh to demonstrate their commitment to making a positive environmental impact, while seeking to engage with consumers in a new, authentic way. Replenysh provides the technology to communities that are helping build the future infrastructure where all materials are traceable and reused.
|
||||
|
||||
|
||||
|
||||
## Refactoring code leads to a better way forward
|
||||
|
||||
Historically the team created their own backend infrastructure, setting up APIs and Authentication to run their own OTP system with Twilio and passwords. Postgres is essential to their requirements because Replenysh use Row Level Security for authorization. Before adopting Supabase, the team used a Haskell server with a different Postgres instance deployed on Heroku.
|
||||
|
||||
The team decided to do a large refactor of their codebase and began investigating alternative hosting options to help speed up development time and reduce maintenance.
|
||||
|
||||
Firebase seemed appealing due to its ability to get started quickly, but the team didn't want to migrate away from a relational database. Specifically, Postgres and RLS fit their requirements.
|
||||
|
||||
When the team discovered Supabase on Hacker News they felt excitement. Supabase has a reputation for a smooth developer experience, providing Postgres and Row Level Security as a core feature.
|
||||
|
||||
As a bonus, Supabase provided more than just a database, reducing their DevOps overhead. After reading the [Supabase Auth documentation](https://supabase.io/docs/guides/auth) the team determined they can have the functionality they need, like SMS OTP. When they saw [Mobbin are using Supabase at scale](https://supabase.io/blog/2021/07/28/mobbin-supabase-200000-users), they decided to migrate to Supabase.
|
||||
|
||||
## Globally recognised brands need quality at scale
|
||||
|
||||
Less than a day after beginning development with Supabase, the team completed their SMS OTP implementation, and deployed their app to the app store a few weeks later.
|
||||
|
||||
|
||||
|
||||
Replenysh clients include brands with global recognition and millions of customers. With their reputation at stake, major brands have a high-quality threshold. If a global brand asks its customers to adopt a technology, the user experience must be high quality and reliable. Their customers' primary interaction point is mobile-first. This means a robust and smooth mobile Auth experience is non-negotiable. After switching to Supabase, when they demo, clients are instantly impressed with just how easy it is for users to log in with an SMS OTP and start participating in the circular economy. As a result, some of the world's largest retailers and beverage companies have recently joined Replenysh and the circular economy.
|
||||
|
||||
|
||||
|
||||
## Supabase means faster development and reduced maintenance
|
||||
|
||||
<Quote img="clark-dinnison.jpeg" caption="Clark Dinnison, Head of Product at Replenysh.">
|
||||
<p>
|
||||
We saw the Auth update for launch week we thought it was the perfect time to get going with
|
||||
Supabase.
|
||||
</p>
|
||||
<p>
|
||||
We implemented & pushed live phone (OTP) auth and had something ready to deploy to the app store
|
||||
in less than 24-hours!
|
||||
</p>
|
||||
<p>
|
||||
Supabase's developer experience lived up to its reputation. Our app is ready to launch with
|
||||
major brands to help them reach sustainability goals and connect with their customers in a
|
||||
meaningful way
|
||||
</p>
|
||||
</Quote>
|
||||
|
||||
## Supabase help Replenysh continue to scale
|
||||
|
||||
Supabase turbo-charged Replenysh's development time with a seamless end-user mobile login experience. They are ready to help major brands engage with their users through participation in the circular economy. With Supabase, the team knows they have a slick auth experience, reduced DevOps overhead, and can continue to scale with Postgres. You can test out the Supabase developer experience today by [starting a new project on the free tier!.](https://app.supabase.io/api/login)
|
||||
@@ -1,39 +0,0 @@
|
||||
---
|
||||
title: Xendit
|
||||
description: Two months of building
|
||||
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
|
||||
authorURL: https://github.com/kiwicopple
|
||||
logo: /images/case-studies/logos/xendit.png
|
||||
tags:
|
||||
- supabase
|
||||
date: '28-10-2020'
|
||||
stats:
|
||||
[
|
||||
{ stat: '20,000', label: Number of employees },
|
||||
{ stat: '10', label: Number of offices },
|
||||
{ stat: '$1M', label: Annual revenue },
|
||||
]
|
||||
misc: [{ label: 'Founded', text: San Francisco }]
|
||||
about: Vercel combines the best developer experience with an obsessive focus on end-user performance. Our platform enables frontend teams to do their best work.
|
||||
---
|
||||
|
||||
### Challenge
|
||||
|
||||
As a payment processor, Xendit are responsible for verifying that all transactions are legal. Any transactions which are suspicions must be verified against a strict set of criteria, and the parties involved need to be checked against international sanctions lists. This is a critical anti-money-laundering operation and needs to be performed in realtime to prevent any delays on legitimate payments.
|
||||
|
||||
### Why they chose Supabase
|
||||
|
||||
Xendit needed something fast. Something that was cheaper than using the global players like Worldcheck or Refinitiv. Xendit already uses Postgres for a lot of their critical infrastructure, and so Xendit team are familiar with the technology and comfortable in it's ability to scale.
|
||||
|
||||
### What they built
|
||||
|
||||
Xendit parses international sanctions lists from the UN and the Indonesian government and loads them into Supabase. Since Supabase provides a full Postgres server, they can then use the [Trigram](https://www.postgresql.org/docs/current/pgtrgm.html) extension to perform full-text search on the lists, with a relevance score on every search.
|
||||
|
||||
Supabase was perfect for their use case, as they needed something built fast. The full solution was built and in production in less than one week.
|
||||
|
||||
> The full solution was built and in production in less than one week.
|
||||
|
||||
Xendit created a database function for searching, which they are able to call directly using their Python clients. They have plans to iterate on the current implementation using more advanced techniques, like machine learning, but for now the Supabase system has been in Production for 9 months without a problem.
|
||||
@@ -1,39 +0,0 @@
|
||||
---
|
||||
title: Xendit
|
||||
description: Two months of building
|
||||
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
|
||||
authorURL: https://github.com/kiwicopple
|
||||
logo: /images/case-studies/logos/xendit.png
|
||||
tags:
|
||||
- supabase
|
||||
date: '28-10-2020'
|
||||
stats:
|
||||
[
|
||||
{ stat: '20,000', label: Number of employees },
|
||||
{ stat: '10', label: Number of offices },
|
||||
{ stat: '$1M', label: Annual revenue },
|
||||
]
|
||||
misc: [{ label: 'Founded', text: San Francisco }]
|
||||
about: Vercel combines the best developer experience with an obsessive focus on end-user performance. Our platform enables frontend teams to do their best work.
|
||||
---
|
||||
|
||||
### Challenge
|
||||
|
||||
As a payment processor, Xendit are responsible for verifying that all transactions are legal. Any transactions which are suspicions must be verified against a strict set of criteria, and the parties involved need to be checked against international sanctions lists. This is a critical anti-money-laundering operation and needs to be performed in realtime to prevent any delays on legitimate payments.
|
||||
|
||||
### Why they chose Supabase
|
||||
|
||||
Xendit needed something fast. Something that was cheaper than using the global players like Worldcheck or Refinitiv. Xendit already uses Postgres for a lot of their critical infrastructure, and so Xendit team are familiar with the technology and comfortable in it's ability to scale.
|
||||
|
||||
### What they built
|
||||
|
||||
Xendit parses international sanctions lists from the UN and the Indonesian government and loads them into Supabase. Since Supabase provides a full Postgres server, they can then use the [Trigram](https://www.postgresql.org/docs/current/pgtrgm.html) extension to perform full-text search on the lists, with a relevance score on every search.
|
||||
|
||||
Supabase was perfect for their use case, as they needed something built fast. The full solution was built and in production in less than one week.
|
||||
|
||||
> The full solution was built and in production in less than one week.
|
||||
|
||||
Xendit created a database function for searching, which they are able to call directly using their Python clients. They have plans to iterate on the current implementation using more advanced techniques, like machine learning, but for now the Supabase system has been in Production for 9 months without a problem.
|
||||
@@ -1,39 +0,0 @@
|
||||
---
|
||||
title: Xendit
|
||||
description: Two months of building
|
||||
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
|
||||
authorURL: https://github.com/kiwicopple
|
||||
logo: /images/case-studies/logos/xendit.png
|
||||
tags:
|
||||
- supabase
|
||||
date: '28-10-2020'
|
||||
stats:
|
||||
[
|
||||
{ stat: '20,000', label: Number of employees },
|
||||
{ stat: '10', label: Number of offices },
|
||||
{ stat: '$1M', label: Annual revenue },
|
||||
]
|
||||
misc: [{ label: 'Founded', text: San Francisco }]
|
||||
about: Vercel combines the best developer experience with an obsessive focus on end-user performance. Our platform enables frontend teams to do their best work.
|
||||
---
|
||||
|
||||
### Challenge
|
||||
|
||||
As a payment processor, Xendit are responsible for verifying that all transactions are legal. Any transactions which are suspicions must be verified against a strict set of criteria, and the parties involved need to be checked against international sanctions lists. This is a critical anti-money-laundering operation and needs to be performed in realtime to prevent any delays on legitimate payments.
|
||||
|
||||
### Why they chose Supabase
|
||||
|
||||
Xendit needed something fast. Something that was cheaper than using the global players like Worldcheck or Refinitiv. Xendit already uses Postgres for a lot of their critical infrastructure, and so Xendit team are familiar with the technology and comfortable in it's ability to scale.
|
||||
|
||||
### What they built
|
||||
|
||||
Xendit parses international sanctions lists from the UN and the Indonesian government and loads them into Supabase. Since Supabase provides a full Postgres server, they can then use the [Trigram](https://www.postgresql.org/docs/current/pgtrgm.html) extension to perform full-text search on the lists, with a relevance score on every search.
|
||||
|
||||
Supabase was perfect for their use case, as they needed something built fast. The full solution was built and in production in less than one week.
|
||||
|
||||
> The full solution was built and in production in less than one week.
|
||||
|
||||
Xendit created a database function for searching, which they are able to call directly using their Python clients. They have plans to iterate on the current implementation using more advanced techniques, like machine learning, but for now the Supabase system has been in Production for 9 months without a problem.
|
||||
@@ -1,39 +0,0 @@
|
||||
---
|
||||
title: Xendit
|
||||
description: Two months of building
|
||||
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
|
||||
authorURL: https://github.com/kiwicopple
|
||||
logo: /images/case-studies/logos/xendit.png
|
||||
tags:
|
||||
- supabase
|
||||
date: '28-10-2020'
|
||||
stats:
|
||||
[
|
||||
{ stat: '20,000', label: Number of employees },
|
||||
{ stat: '10', label: Number of offices },
|
||||
{ stat: '$1M', label: Annual revenue },
|
||||
]
|
||||
misc: [{ label: 'Founded', text: San Francisco }]
|
||||
about: Vercel combines the best developer experience with an obsessive focus on end-user performance. Our platform enables frontend teams to do their best work.
|
||||
---
|
||||
|
||||
### Challenge
|
||||
|
||||
As a payment processor, Xendit are responsible for verifying that all transactions are legal. Any transactions which are suspicions must be verified against a strict set of criteria, and the parties involved need to be checked against international sanctions lists. This is a critical anti-money-laundering operation and needs to be performed in realtime to prevent any delays on legitimate payments.
|
||||
|
||||
### Why they chose Supabase
|
||||
|
||||
Xendit needed something fast. Something that was cheaper than using the global players like Worldcheck or Refinitiv. Xendit already uses Postgres for a lot of their critical infrastructure, and so Xendit team are familiar with the technology and comfortable in it's ability to scale.
|
||||
|
||||
### What they built
|
||||
|
||||
Xendit parses international sanctions lists from the UN and the Indonesian government and loads them into Supabase. Since Supabase provides a full Postgres server, they can then use the [Trigram](https://www.postgresql.org/docs/current/pgtrgm.html) extension to perform full-text search on the lists, with a relevance score on every search.
|
||||
|
||||
Supabase was perfect for their use case, as they needed something built fast. The full solution was built and in production in less than one week.
|
||||
|
||||
> The full solution was built and in production in less than one week.
|
||||
|
||||
Xendit created a database function for searching, which they are able to call directly using their Python clients. They have plans to iterate on the current implementation using more advanced techniques, like machine learning, but for now the Supabase system has been in Production for 9 months without a problem.
|
||||
@@ -1,39 +0,0 @@
|
||||
---
|
||||
title: Xendit
|
||||
description: Two months of building
|
||||
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
|
||||
authorURL: https://github.com/kiwicopple
|
||||
logo: /images/case-studies/logos/xendit.png
|
||||
tags:
|
||||
- supabase
|
||||
date: '28-10-2020'
|
||||
stats:
|
||||
[
|
||||
{ stat: '20,000', label: Number of employees },
|
||||
{ stat: '10', label: Number of offices },
|
||||
{ stat: '$1M', label: Annual revenue },
|
||||
]
|
||||
misc: [{ label: 'Founded', text: San Francisco }]
|
||||
about: Vercel combines the best developer experience with an obsessive focus on end-user performance. Our platform enables frontend teams to do their best work.
|
||||
---
|
||||
|
||||
### Challenge
|
||||
|
||||
As a payment processor, Xendit are responsible for verifying that all transactions are legal. Any transactions which are suspicions must be verified against a strict set of criteria, and the parties involved need to be checked against international sanctions lists. This is a critical anti-money-laundering operation and needs to be performed in realtime to prevent any delays on legitimate payments.
|
||||
|
||||
### Why they chose Supabase
|
||||
|
||||
Xendit needed something fast. Something that was cheaper than using the global players like Worldcheck or Refinitiv. Xendit already uses Postgres for a lot of their critical infrastructure, and so Xendit team are familiar with the technology and comfortable in it's ability to scale.
|
||||
|
||||
### What they built
|
||||
|
||||
Xendit parses international sanctions lists from the UN and the Indonesian government and loads them into Supabase. Since Supabase provides a full Postgres server, they can then use the [Trigram](https://www.postgresql.org/docs/current/pgtrgm.html) extension to perform full-text search on the lists, with a relevance score on every search.
|
||||
|
||||
Supabase was perfect for their use case, as they needed something built fast. The full solution was built and in production in less than one week.
|
||||
|
||||
> The full solution was built and in production in less than one week.
|
||||
|
||||
Xendit created a database function for searching, which they are able to call directly using their Python clients. They have plans to iterate on the current implementation using more advanced techniques, like machine learning, but for now the Supabase system has been in Production for 9 months without a problem.
|
||||
+1
-1
@@ -75,7 +75,7 @@ function Blog(props: any) {
|
||||
</div>
|
||||
</div>
|
||||
<div className="border-t dark:border-dark">
|
||||
<div className="container mx-auto px-8 sm:px-16 xl:px-20 mt-32">
|
||||
<div className="container mx-auto px-8 sm:px-16 xl:px-20 mt-16">
|
||||
<div className="mx-auto ">
|
||||
<div className="grid grid-cols-12">
|
||||
<div className="col-span-12 lg:col-span-8">
|
||||
|
||||
@@ -8,6 +8,9 @@ import {
|
||||
Button,
|
||||
IconChevronRight,
|
||||
IconChevronLeft,
|
||||
IconGlobe,
|
||||
IconLink,
|
||||
IconExternalLink,
|
||||
} from '@supabase/ui'
|
||||
import matter from 'gray-matter'
|
||||
import authors from 'lib/authors.json'
|
||||
@@ -214,6 +217,10 @@ function BlogPostPage(props: any) {
|
||||
<div className="flex flex-col space-y-2">
|
||||
<Typography.Text type="secondary">About</Typography.Text>
|
||||
<Typography.Text>{props.blog.about}</Typography.Text>
|
||||
<Typography.Text className="flex items-center space-x-1 transition-opacity cursor-pointer opacity-50 hover:opacity-100">
|
||||
<span>{props.blog.company_url}</span>
|
||||
<IconExternalLink size={14} />
|
||||
</Typography.Text>
|
||||
</div>
|
||||
{props.blog.misc.map((x: any) => {
|
||||
return (
|
||||
@@ -245,36 +252,6 @@ function BlogPostPage(props: any) {
|
||||
Contact sales
|
||||
</Button>
|
||||
</div>
|
||||
|
||||
<div>
|
||||
<Typography.Title className="mb-4" level={5}>
|
||||
Related case stuides
|
||||
</Typography.Title>
|
||||
|
||||
{props.relatedPosts.map((post: any) => (
|
||||
<Link href={`/blog/${post.url}`} as={`/blog/${post.url}`}>
|
||||
<div>
|
||||
<Typography.Text className="cursor-pointer">
|
||||
<Space>
|
||||
<IconFile size={'small'} style={{ minWidth: '1.2rem' }} />
|
||||
<span className="hover:text-gray-900 dark:hover:text-white">
|
||||
{post.title}
|
||||
</span>
|
||||
</Space>
|
||||
</Typography.Text>
|
||||
<Divider light className="mt-2" />
|
||||
</div>
|
||||
</Link>
|
||||
))}
|
||||
|
||||
<Link href={`/case-studies`} as={`/case-studies`}>
|
||||
<Typography.Text type="secondary">
|
||||
<span className="hover:text-gray-900 dark:hover:text-white cursor-pointer">
|
||||
View all case studies
|
||||
</span>
|
||||
</Typography.Text>
|
||||
</Link>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
@@ -17,41 +17,25 @@
|
||||
</item>
|
||||
|
||||
<item>
|
||||
<guid>https://supabase.io/blog//case-studies/xendit copy</guid>
|
||||
<title>Xendit</title>
|
||||
<link>https://supabase.io/blog//case-studies/xendit copy</link>
|
||||
<guid>https://supabase.io/blog//case-studies/replenysh</guid>
|
||||
<title>Replenysh</title>
|
||||
<link>https://supabase.io/blog//case-studies/replenysh</link>
|
||||
<description>Two months of building</description>
|
||||
<pubDate>Invalid Date</pubDate>
|
||||
</item>
|
||||
|
||||
<item>
|
||||
<guid>https://supabase.io/blog//case-studies/xendit copy 5</guid>
|
||||
<title>Xendit</title>
|
||||
<link>https://supabase.io/blog//case-studies/xendit copy 5</link>
|
||||
<guid>https://supabase.io/blog//case-studies/mobbin</guid>
|
||||
<title>Mobbin</title>
|
||||
<link>https://supabase.io/blog//case-studies/mobbin</link>
|
||||
<description>Two months of building</description>
|
||||
<pubDate>Invalid Date</pubDate>
|
||||
</item>
|
||||
|
||||
<item>
|
||||
<guid>https://supabase.io/blog//case-studies/xendit copy 4</guid>
|
||||
<title>Xendit</title>
|
||||
<link>https://supabase.io/blog//case-studies/xendit copy 4</link>
|
||||
<description>Two months of building</description>
|
||||
<pubDate>Invalid Date</pubDate>
|
||||
</item>
|
||||
|
||||
<item>
|
||||
<guid>https://supabase.io/blog//case-studies/xendit copy 3</guid>
|
||||
<title>Xendit</title>
|
||||
<link>https://supabase.io/blog//case-studies/xendit copy 3</link>
|
||||
<description>Two months of building</description>
|
||||
<pubDate>Invalid Date</pubDate>
|
||||
</item>
|
||||
|
||||
<item>
|
||||
<guid>https://supabase.io/blog//case-studies/xendit copy 2</guid>
|
||||
<title>Xendit</title>
|
||||
<link>https://supabase.io/blog//case-studies/xendit copy 2</link>
|
||||
<guid>https://supabase.io/blog//case-studies/epsilon3</guid>
|
||||
<title>Epsilon3</title>
|
||||
<link>https://supabase.io/blog//case-studies/epsilon3</link>
|
||||
<description>Two months of building</description>
|
||||
<pubDate>Invalid Date</pubDate>
|
||||
</item>
|
||||
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 6.3 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 6.7 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 7.2 KiB |
Reference in new issue
Block a user