Case Study: How Startup Pipe Went From Prototype to Production In 11 Days With Hasura
Tags: casestudy, graphql
Published: 2021-05-05 14:48:34

---
title: Case Study: How Startup Pipe Went From Prototype to Production In 11 Days With Hasura
published: true
date: 2021-05-05 13:21:17 UTC
tags: CaseStudy,GraphQL
canonical_url: https://hasura.io/blog/case-study-how-startup-pipe-went-from-prototype-to-production-in-11-days-with-hasura/
---

![Case Study: How Startup Pipe Went From Prototype to Production In 11 Days With Hasura](https://hasura.io/blog/content/images/2021/05/hasura_pipe_case_study.png)<figcaption>How Startup Pipe Went From Prototype to Production In 11 Days With Hasura</figcaption>

The on-demand recording of this webinar is available [here](https://hasura.io/events/webinar/hasura-pipe/).

[Pipe](https://www.pipe.com/) is a rapidly growing fintech startup that’s transforming how companies fund their growth by unlocking their biggest asset - revenue. Through Pipe’s platform, companies can trade their monthly or quarterly contracts for their annual value upfront, instead of taking on highly dilutive equity and restrictive debt.

> **11 Days:  
> The time it took to go from prototype to production with Hasura**

In just one year Pipe has experienced amazing success, gaining over 3,500 customers and $1 billion in tradable annual recurring revenue - accomplishing this with just 11 engineers.  

> **$600k USD Saved Annually:  
> Using Hasura, Pipe needed 50% fewer developers than they anticipated**

Helping fuel this efficiency was Pipe’s decision early on to make [Hasura](hasura.io) an essential part of their technical architecture, which has provided tangible benefits to their dev processes and their bottom line:

> _ **“Hasura is a fantastic way to create a data fetching layer to our database.  It’s ultra-stable and often better at planning queries than ones we were writing ourselves.”** _

Other advantages include:

- 90% reduction in time for new feature development
- Simplified GraphQL data fetching architecture makes it easy to add new features
- Authorization and permissions model secures sensitive financial data
- Incremental migration to GraphQL rather than monolithic rewrite
- Breaking down barriers between frontend and backend engineering
- Consistency in production deployment and configuration utilizing Hasura metadata

![Case Study: How Startup Pipe Went From Prototype to Production In 11 Days With Hasura](https://hasura.io/blog/content/images/2021/05/Frame-7.png)<figcaption>Pipe's technical architecture</figcaption>

Let’s dive deeper to learn more!

# Pipe’s Challenge

Pipe makes it easy for companies with recurring revenue streams and subscription-based business models to convert that into capital to scale and quickly scale and grow their businesses.

![Case Study: How Startup Pipe Went From Prototype to Production In 11 Days With Hasura](https://lh3.googleusercontent.com/aF0AUT63ZoQBSV2PKEnz1eeQeCfG2xlPW6iVJwyInl4xBp_dLm1Jbx98mYLizTETdxeah5EVENoLHhwN2uGELNyomacCeOjvGoMA97bKafbGLut66bpINun9Vw_Ru478Gt7zcHa3)<figcaption><em>Pipe helps businesses convert subscriptions and recurring contracts into up-front capital</em></figcaption>

Pipe’s development team needed to thread the needle balancing the immediate requirements of the business while also building for the future.  Their technical architecture started with a [Postgres database](https://hasura.io/learn/database/postgresql/what-is-postgresql/), Go as their backend language, REST APIs, and React for their web front-end running on Google Cloud.  As they rapidly grew, they needed to consider additional concerns:

- **Fast Time to Market & Feature Innovation:** Pipe’s team needed to quickly create or change features based to gain new customers and respond to user feedback
- **Flexible Architecture:** One of Pipe’s architectural goals was to keep the architecture as agile as possible, where changes to the underlying database and frontend UX could happen rapidly.  
- **Small Development Team:** Pipe’s 11 engineers needed to stay agile and flexible - understanding all layers of their system - database, backend, integrations, and the frontend web UI
- **Flexible Web APIs:** One of their early challenges was inflexibility of utilizing REST APIs, where they encountered multiple variations of similar request types, but each requiring its own REST endpoint because of differing requirements.
- **Performance:** Pipe’s website needed to run quickly to provide a great user experience, and scale to meet the traffic of their rapidly growing customer base.
- **Security & Authorization:** Pipe’s system stores sensitive financial and customer data of their customers and they needed to make sure that the data was secure and that users could only view data they were authorized to see

# Why Pipe Chose Hasura

As Pipe started investigating solutions to these challenges, they discovered Hasura and went into production with it _within_ _11 days_.

> _ **“We needed 50% fewer frontend developers than we thought we needed.  Hasura and GraphQL reduced the toil to build and iterate on the frontend.”** _

<!--kg-card-begin: html-->

| 

![Case Study: How Startup Pipe Went From Prototype to Production In 11 Days With Hasura](https://lh4.googleusercontent.com/l0m1Ay0-A8tkyJs3uDtYDqu0t7BG3dl8zONlqFrO9CaIXSSOFL6Fp-53T4zFVdEnp6eR4UM1t2cgjE7_lavfiEoMy4jmGR5LtLYUKB2CEcJDY-ARDfLcVn-Sh5e2JTUz_YWPnF8M)

Zain - Pipe’s CTO

 | 

![Case Study: How Startup Pipe Went From Prototype to Production In 11 Days With Hasura](https://lh4.googleusercontent.com/8hGMPbsiQoE47mpMhmsl_QPeZ8NzaSgLXEhjvoPt3buHgqI6hNKm2d6VBJ_YP1dNGVXVBh-adYEYJC-VWPV1qy0njwQNjNs2gFbCjVK3q1yUplQyj-MDZ6QgqbPnWHuL87ifK6f2)

  
  
  
  

Ian - Frontend developer

 |
| 

Pipe put Hasura into production within 11 days of discovering it, helping them develop new features rapidly and breaking down barriers between backend and frontend development.

 |

<!--kg-card-end: html-->
### Ease of Use

Hasura’s intuitive tools and documentation made it easy to set up and connect to their Postgres database, instantly [auto-generating](https://hasura.io/docs/latest/graphql/core/databases/index.html) GraphQL schemas and resolvers based on the tables and views in their database.  This saved them development and maintenance time not having to author any more of their data access APIs themselves and modifying the code every time they made a database change.

### GraphQL-based Data Access

Moving to GraphQL from REST also enabled them to unify and simplify their data access APIs.  The flexibility allows the same endpoint to return only the requested fields and child (tree) data structures - making the queries more efficient and eliminating the need to create a different API for each unique request.

As Pipe made changes in their database, they didn’t have to rewrite their APIs - they just had to adjust requests made from their React frontend to access the new data.

### Security and Authorization

Another benefit Hasura provided is its built-in security and [authorization](https://hasura.io/docs/latest/graphql/core/auth/authorization/index.html#authorization) capabilities, which can limit what data is returned down to the individual column and row level.  This capability saved on development time implementing it themselves and ensured that customers could only view their own data.

### Development Team & Processes

Utilizing Hasura made it easier for every engineer to understand the flow of data from the database to their frontend, making it possible for backend or frontend developers to make changes and add features quickly.

Operationally, their deployment processes are simplified by utilizing Hasura’s [metadata](https://hasura.io/docs/latest/graphql/core/migrations/config-v2/manage-metadata.html#manage-hasura-metadata-v2) capabilities to make sure configuration changes made in development and staging are consistently deployed to production.

> _ **“Hasura helps us remove the strict boundaries that traditionally separate front-end and back-end engineers, and makes it easier for any developer to make changes.”** _

# What’s Next for Pipe

Pipe is currently using Hasura to query data to present in their React web frontend.  In the future they plan on exploring additional Hasura features such as mutations - utilizing their existing Hasura GraphQL APIs to perform data inserts and updates -- and remote schemas to fetch data from 3rd party services.

They're also looking closely at GraphQL [subscriptions](https://hasura.io/docs/latest/graphql/core/databases/postgres/subscriptions/index.html#subscriptions) to add real-time updates and notifications to the user experience. As their site traffic increases they plan to use Hasura’s database read-replica support to balance queries and subscriptions across database replicas.

Finally, webhooks - initiated by Hasura [Event Triggers](https://hasura.io/docs/latest/graphql/core/event-triggers/create-trigger.html#create-trigger) when database changes occur - may also provide a layer of real-time integration to their other microservices.

_Thank you to our friends at [Pipe](https://www.pipe.com/), and [Peter Downs](https://www.linkedin.com/in/peterldowns/) - Director of Engineering for sharing their story with us!_