External API Platforms
One-line description. Non-GCP platforms worth using alongside GCP for specific workloads. Captured catalog, not an active build.
Why
GCP isn't the right tool for every workload.
Some things are cheaper, faster, or simpler somewhere else.
Cloudflare for the edge. RESO for MLS truth. Twilio for voice and SMS. Stripe for money. Brevo for transactional + multi-channel messaging.
Each does what it's best at. None duplicate GCP. Together they cover the full lead-to-close-to-past-client lifecycle without manual seams.
This file exists so future-me doesn't forget what's on the menu when an adjacent problem shows up.
Current state
Captured but not active.
The four platforms are scoped. None are wired up beyond what already exists (Cloudflare for DNS and Pages).
What pulls each one forward:
- Cloudflare Workers / R2 / Browser Rendering — first public webhook, lead-magnet form, or screenshot job that fits the edge pattern.
- RESO Web API — Matrix scraping breaks, or market reports / Showing Day app start scoping.
- Twilio — SMS appointment reminder need, or the Custom Dialer project promotes out of "idea."
- Stripe — first decision to charge for anything (FSBO playbook, premium market reports, setter system as a product).
-
Brevo — first concrete need for transactional email, SMS reminders, or WhatsApp that Kit can't handle. See Brevo API capability map.
-
Status: planning
- Last update: 2026-04-26
- Blocked on: nothing. Held by priority.
Next 3 actions
(none — surface when relevant)
Decisions log
- Portfolio organization — vault README is the front door, every project gets a hub from the template
Open issues
The four platforms, in priority order to actually wire up:
- Cloudflare Developer Platform — already have account. Lowest barrier. First Worker could be the wallet-pass generator or a lead-magnet form handler.
- RESO Web API — paperwork barrier, not money. Apply for NTREIS credentials early. Approval can take weeks.
- Twilio — SMS reminders first (low-stakes integration). Custom dialer is its own project.
- Stripe — only when monetization is a near-term decision.
- Brevo — captured 2026-05-06. Transactional email + SMS + WhatsApp + CRM under one API key. Pulls forward when SMS reminders or transactional triggers (CMA-ready, doc-signed) need a real channel. Kit stays the nurture/newsletter layer.
References
- Idea-Inbox doc:
~/CCPJ/projects/Idea-Inbox/idea/2026-04-26-external-api-platforms.md(if filed there) - Related: Appointment Wallet Pass, Custom Dialer, Market Report Lead Conversion, GCP Enhancement Candidates
2026-07-16 — RECONCILED (RYR-172 E1): Brevo + Telnyx superseded, hub is reference-only
The 5/6 platform picks aged out where comms are concerned, and this pass records it: - Brevo — superseded by Resend. Every transactional-email need Brevo was earmarked for now ships on Resend (comms-platform sender, consult-profile triggers, should-i-sell welcome — the last verified live 2026-07-16), and the ratified Flywheel gate G1 makes Resend the default for everything new. Brevo has no live integration and no planned pull-forward; do not build on it. - Telnyx — superseded by Twilio for any near-term voice/SMS. The Phone Platform that would have exercised Telnyx was shelved indefinitely 6/30; the Custom Dialer track (~Sept 2026, RYR-57) specs Twilio. No Telnyx code, terraform, or GCP secrets exist in the monorepo (verified 2026-07-16: zero hits in .py/.tf/*.js and secrets list); it appears only in comms-platform design docs as the planned-but-never-built SMS layer. - Cloudflare, RESO, Twilio, Stripe entries remain accurate as capability references. This hub stays as a reference index only — new platform adoption decisions route through the vendor kill-criteria rule and the relevant project's spec, not this planning doc.