---
created: 2026-08-10 12:51
modified: 2026-08-10 12:51
type: note
tags:
  - dev-ops
  - self-hosting
  - inmotionhosting
  - email
  - amazon
aliases: []
---
# [[Email Backup off site hosting]]


# Infrastructure Summary: where-woof.com
**Architecture Overview:** Decoupled layout transitioning away from bundled VPS hosting to a cost-effective local hosting environment, backed by cloud storage and specialized mail delivery platforms.

---

## 1. Email Architecture

Mainstream email companies do not bundle interactive inboxes and bulk transactional sending because **reputation isolation** is required. An outgoing transactional error could blackhole everyday business communications if hosted on the same infrastructure.

### Incoming Email (Interactive Inboxes)
*Handles receiving mail from clients to custom addresses (e.g., hello@where-woof.com) accessible via client apps.*
*   **Primary Providers:** 
    *   **Zoho Mail:** Excellent free tier for up to 5 users via webmail/app; ~$1/user/month to unlock desktop IMAP/POP3 for **Thunderbird** and **Gmail**.
    *   **MXroute:** Flat annual fee ($30–$45) providing unlimited domains and cPanel-style inbox freedom without server administration.
*   **Integration:** Map your domain's **MX Records** to the chosen provider. Connect Thunderbird or your consumer Gmail app using standard IMAP (Port 993) and SMTP (Port 465) settings.

### Outgoing Email (Transactional Web Sending)
*Handles automated website delivery (e.g., password resets, notifications, contact forms) safely avoiding spam filters.*
*   **Primary Providers:**
    *   **Resend:** 3,000 free emails/month (capped at 100/day). Developer-focused UI, easy code API integration, affordable to scale ($20/month for 50k emails).
    *   **Brevo:** 9,000 free emails/month (300/day limit). High free ceilings and built-in SMTP engine.
*   **Integration:** Map your domain's **TXT Records (SPF & DKIM)** to give the platform sending authorization. Configure your application code to authenticate via their API or SMTP credentials.

---

## 2. Server & Local Infrastructure (Caddy)

Running your production application locally behind your existing **Caddy** configuration bypasses strict VPS pricing structures.

*   **Dynamic DNS (DDNS):** Residential internet connections utilize shifting external IP addresses. You must deploy a DDNS client or script (e.g., Cloudflare API) to dynamically point `where-woof.com` to your home network whenever the IP address shifts.
*   **ISP Port Constraints:** Residential ISPs frequently block incoming web traffic on **Ports 80 and 443**. If blocked, native Caddy ACME SSL verification fails. 
*   **Mitigation Strategy:** Route incoming web traffic through **Cloudflare Tunnels** or a lightweight cloud proxy instance ($5/month VPS) to securely bridge public web traffic to your local Caddy server.

---

## 3. Remote Cloud Backup (Amazon Web Services)

Isolating backup storage completely from your local environment secures your data against hardware failure or network loss.

*   **Platform:** **AWS Simple Storage Service (S3)** or **S3 Glacier Flexible Retrieval**.
*   **Workflow:** A native script running locally (via cron and utilities like Restic, Duplicati, or AWS CLI) compresses, encrypts, and transfers database and site assets directly to an AWS bucket.
*   **Cost Efficiency:** Stored data costs roughly **$0.023 per GB per month**. 100 GB of offsite backup data scales cleanly to ~$2.30/month, charging strictly for the storage you consume.