Camlin Connect
Deployment and architecture
How Camlin Connect is hosted, what it is made of, where your data is processed and how it connects to the systems you already run. One platform, four ways to deploy it.
Deployment models
Every tenant declares one deployment model. The same platform runs in all of them.
Shared SaaS
Operated by Nuamedia in Sydney (ap-southeast-2). The fastest path to a working service. Data stays in the region.
Dedicated cloud
The platform runs in your own cloud account, inside your network boundary and under your monitoring.
Your own infrastructure
The same containers run on your servers with Docker or Kubernetes, including air-gapped sites with no outbound network. Licences are signed files verified locally. No activation call.
No-AI runtime mode
A validated mode for deterministic flows. A service flagged No AI in runtime cannot make a model call. The rule is enforced when the design is saved and again at run time.
Components
- Camlin Architect
- The builder. Service design, review, version history and publishing.
- Runtime services
- Turn-by-turn execution for voice, chat, SMS, avatar and web from one service model.
- Camlin Contact
- Telephony on open SIP trunks with Asterisk-based call control, queues and agent handling.
- Camlin Speech
- Australian-English recognition and text-to-speech, hosted in Sydney or on your hardware.
- Camlin Insight
- Analytics, release history, diagnostics and the audit trail for every live service.
Data and residency
- Processing happens in Sydney by default.
- Customer-hosted deployments keep data inside the customer boundary.
- Traffic is encrypted in transit with TLS.
- Secrets are held in the hosting platform’s secrets store and injected at run time.
- The Sydney region and the speech supply chain are mapped against PSPF, FOCI and HCF guidance on the Camlin Speech sovereignty page. This is alignment language. Nuamedia does not claim any third-party security certification.
- How Nuamedia handles personal information on this website is set out in the privacy policy.
Integration
Telephony and APIs
Open SIP for carriers and trunks. REST and WebSocket APIs for sessions, events and data. An external agent flow-edit API lets your own agents and tools change flows under the same review controls as the builder.
Identity
Sign-in uses your identity provider through standards-based OIDC, including providers that run inside an air-gapped network. Owner, admin, editor and viewer roles are managed in the platform and do not change when the provider does.
Operations
- Releases are cut from a reviewed version and activated with operator confirmation.
- Rollback returns the service to the previous release.
- Camlin Insight holds the release history, diagnostics and audit trail.
Commercial options for each model are on the how to buy page.
Next step
Discuss a secure deployment
Tell us the hosting model, the network constraints and the frameworks you need to meet.