feat: multi-cloud deployment — Vultr, DigitalOcean, AWS Terraform + cost comparison#9
Merged
munisp merged 1 commit intoJun 20, 2026
Conversation
…ost comparison Adds provider-agnostic deployment infrastructure: Vultr (Recommended — ,029/mo): - 3-region VKE clusters (Toronto, London, Johannesburg) - Managed PostgreSQL primary + 2 read replicas - Managed Redis per region - Block storage (NVMe) for TigerBeetle + Kafka - Cloudflare CDN + WAF + GeoDNS + Load Balancer - Object storage for KYC docs + backups - Firewall rules (HTTPS-only ingress) DigitalOcean (Budget — 93/mo, no Africa DC): - 2-region DOKS clusters (Toronto, London) - Managed PostgreSQL with HA - Managed Redis per region - Spaces for object storage - Requires colo partner for Africa (Rack Centre/MainOne) AWS (Existing — ,621-7,621/mo): - Reorganized into ops/deployment/terraform/aws/ - Full hyperscaler feature set (Shield, GuardDuty, PrivateLink) Documentation: - Cost comparison: 3-year TCO analysis (Vultr saves 27-235K vs AWS) - Deployment guide: provider-agnostic setup, DR procedures, migration path - Decision matrix: weighted scoring across 6 factors Co-Authored-By: Patrick Munis <pmunis@gmail.com>
Contributor
Author
Original prompt from Patrick
|
Contributor
Author
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds production-ready Terraform for 3 cloud providers so the team can choose based on cost/compliance tradeoffs, plus documentation comparing them.
Why: AWS costs $4,600-7,600/mo for RemitFlow's multi-region setup. Vultr achieves equivalent compliance (SOC 2, PCI-DSS) with Africa presence (Johannesburg) for $1,029/mo — saving $127-235K over 3 years.
What's included:
All three providers use the same Helm chart (
ops/deployment/helm/remitflow/) and the same Docker images — only the infrastructure layer changes. Cloudflare sits in front of all options for CDN + WAF + GeoDNS.Key design choice: Vultr terraform uses
cloudflare_load_balancerwithregion_poolsfor continent-based routing (WNAM/ENAM → Toronto, WEU/EEU → London, SAF/WAF/NAF → Johannesburg), replacing AWS Route53 GeoDNS.Link to Devin session: https://app.devin.ai/sessions/64d054ae77da41e9a2b74d8593fa635c
Requested by: @munisp