Run on your own host.
A supported Windows server or workstation can host the service and SQLite records. We review hardware, call concurrency, and recovery requirements for your deployment.
BRENDA’S DESK · SELF-HOSTED & PRIVATE DEPLOYMENT
Your infrastructure.
Your control.
Run the Brenda’s Desk receptionist application and its customer records on infrastructure you manage. For teams that want control over the host, network access, backups, and local record retention.
A deployment and licensing discussion shaped around your environment.
Application and logs on your hostDirect provider connectionsSeparate staff authorization
A LEAN APPLICATION STACK
Own the operational layer.
The modular .NET 10 service handles call routing, staff authorization, request intake, and encrypted application records. Telnyx provides call control and media streaming; OpenAI Realtime supplies the voice conversation.
Choose your entry points.
Plan HTTPS and WebSocket ingress through a reverse proxy or Cloudflare Tunnel. Separate the private staff workspace from the endpoints Telnyx needs to reach.
Set your own policies.
Control application access, backups, maintenance, and local record retention. Caller authorization and private agent routing remain enforced by the service.
CLEAR DATA BOUNDARIES
Local records.
Connected voice.
The application and saved customer records reside on your installation. You do not need an additional multi-tenant receptionist platform between your application and the voice providers.
Self-hosting still uses external processing: Telnyx carries the call and audio, and OpenAI processes conversation audio and the context sent to it. Provider terms and retention settings must be reviewed for your use case.
We review where information travels, what gets saved locally, and what your team can access before agreeing the deployment.
BEFORE WE CHOOSE A HOST
Make the environment fit.
Tell us about locations, expected concurrent calls, uptime needs, and your IT team’s preferred operations model.
Windows deployment
The current install and recovery tooling targets Windows. We discuss service identity, protected keys, unattended startup, and a recoverable backup plan.
Proxmox or virtualization
A Windows guest may fit your existing virtual infrastructure. Capacity, public connectivity, and restore procedures need to be validated on the target host.
Docker or Linux requirements
Bring these into the setup discussion. Container packaging and non-Windows key protection require environment-specific work and validation before we commit to support.
LICENSING & PRIVATE SETUP
Let’s map your
deployment.
Share the environment, call volume, intake workflows, and data requirements you have in mind. We’ll review licensing, setup, and ongoing responsibilities with you.
Describe your requirements without credentials, patient information, or confidential client details.
Open the licensing enquiry form ↗Prefer a managed service? Explore hosted reception. See our privacy information.