Internet-connected
Public endpoint, TLS from a public authority, optional relay for traversal. Best for distributed offices and inter-agency reach.
- Public DNS
- Public TLS
- Self-hosted push
- Optional public relay
Deployment
From a single host to an air-gapped tactical network.
Amana ships as a small set of services with documented sizing. There is no managed cloud component. You can stand up a working server in under an hour on a single mid-range box.
Deployment
Three topologies. One product.
The same Amana runs in your data centre, on a closed LAN, or on a single network segment with no internet at all. Decide once how you want to be reached. The product follows.
Air-gapped private network
No internet. Your own certificate authority. Your own relay. The deployment most ministries and defence customers choose.
- No external dependency
- Internal TLS authority
- Private relay
- Internal push
Flat tactical LAN
A single network segment. Calls connect peer-to-peer. No relay required. For field and forward deployments.
- No relay
- Peer-to-peer calls
- Single segment
- Tactical-grade
Server stack
Amana API
Go binary. HTTP and WebSocket. Single process.
PostgreSQL 16+
Encrypted envelopes, device records, audit log.
Redis 7+
Presence, transient state, SFU coordination.
Coturn
WebRTC NAT traversal. Optional on flat LAN.
SFU
Self-hosted Selective Forwarding Unit for group calls.
ntfy
Self-hosted push. iOS uses an APNs relay (token only).
Hardware sizing, rough starting points
| Tier | CPU | RAM | Disk | Notes |
|---|---|---|---|---|
| Up to 1,000 users | 4 vCPU | 8 GB | 100 GB NVMe | Single host |
| 1,000–10,000 users | 8 vCPU | 32 GB | 500 GB NVMe | Database on dedicated host |
| 10,000–100,000 users | 16+ vCPU per node | 64 GB per node | 1 TB+ NVMe | Horizontal scaling, multi-region SFU |
Talk to us
Thirty minutes with the people who built it.
Not a sales bench. The engineers who wrote the protocol take the meeting, hear the constraint, and tell you honestly whether Amana fits.
contact@amana.app