---
title: Hosting Locations
slug: hosting-locations
docTags: 
createdAt: 2025-03-26T17:33:33.286Z
---

Our software product is supported by a robust and distributed hosting infrastructure designed for performance, reliability, and scalability. Below is a breakdown of where various components of our system are hosted and how data is managed across regions.

### Node.js Servers

- All backend services built on Node.js are hosted on **DigitalOcean** infrastructure located in **New York City (NYC)**.
- These servers are responsible for handling core application logic, API routing, authentication, and other backend functionality.
- Our primary relational databases are also hosted on **DigitalOcean**, co-located with the application servers in **NYC** to ensure minimal latency and fast data access.

### Database Backups

- We maintain **regular database backups** that allow, at latest, hourly backups that are stored in a separate geographic location—**San Francisco (SF)**—to provide redundancy and disaster recovery capabilities in the event of an outage or failure in the primary region.

### Static React Applications

- Our front-end interfaces are built using **React** and are deployed as static sites. These are served globally using a **Content Delivery Network (CDN)** to ensure fast and consistent load times for users regardless of their geographic location.

### AWS S3 Buckets

- All media assets, including images and file blobs, are stored on **Amazon Web Services (AWS)** across two distinct regions for different purposes:
  - **Public Assets**: Stored in **us-west-1** (Northern California), these are accessible via public URLs and typically include images and content used in user-facing interfaces.
  - **Private Assets**: Stored in **us-west-2** (Oregon), these are protected and used for internal or restricted purposes such as secure file uploads, private user documents, and system-level data.

***

## TL;DR 🧠

### Summary

- 🖥️ **Node.js Servers**: Hosted on **DigitalOcean** in **NYC**
- 🗄️ **Databases**: Hosted on **DigitalOcean** in **NYC**, with backups in **SF**
- 🌐 **React Frontend**: Served globally via **CDN**
- 🖼️ **Image/Blob Storage**:
  - Public assets → **AWS us-west-1**
  - Private assets → **AWS us-west-2**



*Hosting Overview Table*

| Component             | Hosting Provider | Location(s)            | Notes                                       |
| --------------------- | ---------------- | ---------------------- | ------------------------------------------- |
| Node.js Servers       | DigitalOcean     | New York City (NYC)    | Backend logic, API routing, authentication  |
| Primary Database      | DigitalOcean     | New York City (NYC)    | Co-located with app servers for low latency |
| Database Backups      | DigitalOcean     | San Francisco (SF)     | Redundancy & disaster recovery              |
| Static React Sites    | DigitalOcean     | Global CDN (Worldwide) | Fast front-end delivery                     |
| Public Image Storage  | AWS S3           | us-west-1 (N. CA)      | Publicly accessible media assets            |
| Private Image Storage | AWS S3           | us-west-2 (Oregon)     | Internal/restricted access files            |