Company and compliance
Reliability and backups
Each part of a call has a backup that takes over mid-call, so the caller doesn't hear silence.
| Part | Main | Backup |
|---|---|---|
| Hearing | Deepgram Flux (knows when the caller has finished) | Deepgram Nova-3 |
| Thinking | The agent's AI model (Gemini) | The other model (Claude), picking up from the transcript |
| Voice | The agent's Fish Audio voice | Its backup Fish voice; a voice that hasn't started within 3 seconds counts as down |
| Garbled replies | A reply that comes out muddled | Is written again before it's spoken |
Hosting and backups
- One always-on server in Sydney runs the dashboard and the voice server; Fly restarts it if it stops responding.
- The database is managed Postgres (Supabase, Sydney), backed up daily by Supabase.
- A copy of every table is also exported every night and uploaded to separate storage.
- Errors are emailed to whoever runs the app (ALERT_EMAIL), at most once per kind every 15 minutes.
- The test site checks the live site every minute and emails when it stops answering for about 3 minutes, and again when it's back.
- A failing connected app never stops a call or the other apps.
Both voices are on Fish Audio, so a Fish Audio outage isn't covered by the backup.