Hosting and deployment

Your own server or hosted by Tallify, and what runs on it.

Two options

• Your own server. A GPU server on the practice's premises or in a South African data centre, joined to the practice's private network. The practice owns the hardware and the data on it.
• Hosted by Tallify. Dedicated infrastructure in South Africa that Tallify operates for that practice alone, under an operator agreement, with the same controls. No practice shares a server with another.

What runs on the server

• The console and API.
• A worker that runs extractions and drafts from a job table, so a restart re-runs a job rather than losing it.
• The Telegram bot and the mailbox poller.
• Local models for reading documents and for search embeddings.
• Scheduled jobs, backups and the monitor.

All services run as a dedicated unprivileged user. Secrets live in a root-only file, never in code.

Network

The console binds to the practice's private network address only, over HTTPS with a certificate for the practice's console name. The only public endpoint is a signed webhook for WhatsApp delivery and a health check that carries no data.

Updates

Updates are deployed from the Tallify repository. The worker is restarted only when no draft is in flight. Changes that affect how users work are described before they are applied, as the terms say.