Technology
For the technically minded: what VoicerCRM is built on and how it's structured. You don't need any of this to use it, but it's here if you're evaluating or integrating.
Architecture
| Layer | Details |
|---|---|
| Server | Server-side Swift on the Vapor framework, running on macOS. |
| Database | PostgreSQL for all records; Redis for fast caching. |
| Web UI | HTML5 + Bootstrap 5 + HTMX — fast, server-rendered pages. |
| Mobile | Native iOS / iPad clients. |
| A built-in mail server (SMTP/IMAP) with PostgreSQL-backed mailboxes. |
The Universal Customer Data Model
Rather than separate tables for "contacts", "companies", "patients" and "students", VoicerCRM uses a single Party record (a person or an organization) joined to others by typed relationships and roles. Industry-specific details attach as extensions without changing the core schema, and every record carries a data classification (Standard, Confidential, PHI, PCI) that drives how it's handled.
It's what lets one product serve retail, healthcare, SaaS, education and trades — and grow with a business — without migrations or forked codebases.
Security & compliance
- Encryption in transit (TLS) and at rest; secrets kept out of the codebase.
- RBAC with fine-grained permissions and JWT authentication.
- Audit trails, consent records, data retention/archiving and right-to-be-forgotten.
- Controls aligned to HIPAA, GDPR and PCI-DSS — see Compliance.
Voice services
Beyond the phone integration, VoicerCRM includes text-to-speech and speech recognition services (multiple providers) used for IVR and call features, and call sentiment/conversation analytics.