Architecture
How Astervis works at a high level
Astervis runs as a set of Docker containers on your server, separate from your PBX.
How It Works
Key Benefits
| Traditional Approach | Astervis Approach |
|---|---|
| Query MySQL directly | Dedicated analytics database |
| Heavy queries slow PBX | Zero impact on PBX |
| Polling for updates | Real-time sync (seconds) |
| Slow on large datasets | Optimized for millions of records |
Data Flow
- Call happens → Your PBX writes a CDR record
- Instant capture → Astervis detects the new record
- Transform & store → Data optimized for analytics
- Dashboard updates → See the call immediately
New calls appear in your dashboard within seconds of completion.
What's Installed
Astervis installs these components via Docker:
- Analytics Database — optimized for time-series queries
- API Server — powers the dashboard and integrations
- Web Dashboard — the interface you use daily
- Background Workers — handle sync and scheduled tasks
- Reverse Proxy — HTTPS access on port 8443
All components are containerized and managed by Docker Compose.
Resource Usage
Typical production deployment (400K+ CDR records):
| Component | RAM Usage |
|---|---|
| Database | ~400 MB |
| API Server | ~150 MB |
| Dashboard | ~130 MB |
| Sync Services | ~1.5 GB |
| Cache | ~10 MB |
| Total | ~2.3 GB |
Network
| What | Port |
|---|---|
| Dashboard (HTTPS) | 8443 |
| Internal services | Not exposed |
Only port 8443 is accessible from outside. All other services communicate internally.
Next: Installation — deploy Astervis on your server