Skip to content
Pitchpipe

Integrations Overview

The platform doesn’t do everything itself — payments, tokenization, mail, search, and AI classification all run through external services. This is the inventory: what we integrate with, what it does for us, and which system owns the connection.

Most integrations are owned by Foundation, since it’s the system of record. A couple are genuinely client-side and belong to Resonance.

Payments

Section titled “Payments”
Service Role
Unity FI ACH processor — bank-account debits. Handles the submit → NACHA batch → status → return-monitoring lifecycle.
Cornerstone Legacy credit-card gateway.
VGS PCI-compliant tokenization. Card data is swapped for tokens so Foundation never stores raw card numbers.

Communications

Section titled “Communications”
Service Role
Postmark (via Anymail) Transactional email.
Twilio SMS.
Postal mail Physical letters, rendered to PDF and sent.

Data, search & AI

Section titled “Data, search & AI”
Service Role
Anthropic Claude Classifies inbound letters by type in the inbound pipeline.
Typesense Full-text search over debts and people.
NATS JetStream The async backbone — OCR, classification, response generation, and payment jobs all flow over it.
S3 / MinIO Document and letter storage (MinIO locally, S3 in production).

Legacy

Section titled “Legacy”
Service Role
Forth CRM The legacy source of contact, debt, and payment data. Foundation pulls from it one-directionally and maps records into its own models. This is the integration we’re working to retire — see Where We’re Headed.

Client-side (Resonance)

Section titled “Client-side (Resonance)”
Service Role
Calendly Onboarding-call booking during client onboarding.
Sentry Error tracking and session replay for the portal.

Source: foundation/config/settings.py, foundation/requirements.in, foundation/payments/, resonance/src/features/onboarding-call-booking/.