Search K

Appearance

Installation and Upgrade

Infrastructure Advice ​

This document provides guidance on choosing the right infrastructure and deployment model for VoipNow, a cloud communications platform designed to scale infinitely.

Quick Start ​

Choose your deployment path:

Both deployment models support High Availability configurations.

Why Cloud Infrastructure? ​

Cloud infrastructure is the recommended approach for VoipNow deployments. Cloud services provide:

  • Scalability: Easily scale resources up or down based on demand
  • Cost Efficiency: Pay only for what you use, no upfront hardware investments
  • Reliability: Built-in redundancy, backup, and disaster recovery
  • Flexibility: Provision resources in minutes, deploy globally
  • Reduced Management: Focus on your business while the provider handles infrastructure

VoipNow works excellently with major Infrastructure-as-a-Service (IaaS) providers:

  • Amazon Web Services (AWS)
  • Microsoft Azure
  • Google Cloud Platform
  • Oracle Cloud
  • Other compatible IaaS services

"Cloud-First Recommendation"

While VoipNow can run on your own infrastructure, cloud services eliminate hardware concerns, reduce operational overhead, and provide the flexibility needed for optimal performance and scaling.

Single Node vs. Distributed Deployment ​

VoipNow can be deployed in two modes. Understanding the differences will help you make the right choice.

Single Node Deployment ​

A single node deployment runs all VoipNow services on one computing instance (virtual machine or physical server).

Pros ​

  • Simpler Management: Single system to configure, monitor, and maintain
  • Lower Operational Costs: No need for distributed infrastructure management tools
  • Easier Troubleshooting: All services in one place
  • Faster Initial Setup: Quicker to deploy and configure
  • Sufficient for Most Use Cases: Handles 10,000+ users and 1,000+ concurrent calls
  • Lower Skill Requirements: Less advanced system administration knowledge needed

Cons ​

  • Limited Scaling: Constrained by single node resources (CPU, memory, I/O)
  • Single Point of Failure: Requires HA configuration for redundancy
  • Resource Limits: Cannot scale individual services independently

When to Choose Single Node ​

  • You expect fewer than 10,000 users in the near term
  • You prefer simpler operations and management
  • You want to minimize operational complexity
  • You're starting small and can scale later

Distributed Deployment ​

A distributed deployment runs VoipNow across multiple nodes, with services distributed and specialized by role.

Pros ​

  • Massive Scalability: Scale beyond single-node limitations
  • Independent Scaling: Scale specific services (database, web, signaling) independently
  • Better Resource Utilization: Optimize resources per service type
  • Single System Management: Manage everything as one unified system
  • Infinite Growth: No practical limits on users or capacity

Cons ​

  • Complex Management: Requires advanced system administration skills
  • Higher Operational Costs: Need monitoring, logging, and management tools
  • More Complex Troubleshooting: Issues can span multiple nodes
  • Infrastructure Requirements: Requires distributed infrastructure expertise
  • Professional Support Recommended: Best deployed with expert guidance

When to Choose Distributed ​

  • You need to support more than 10,000 users on a single system
  • You require independent scaling of specific services
  • You have advanced infrastructure management capabilities
  • You want a single unified system for massive scale

"Important Decision"

The choice between single and distributed should ideally be made at installation time. While you can migrate from single to distributed later, you cannot migrate from distributed back to single node on your own. If you need assistance with migration or are unsure about your deployment choice, please contact 4PSA support for guidance.

Growth Path for Less Advanced Users ​

"Recommended Growth Strategy"

For less advanced users, we recommend starting with single node deployments and growing by adding multiple independent single-node systems rather than moving to distributed deployment.

This approach allows you to:

  • Gain experience with VoipNow operations
  • Scale by adding complete systems as needed
  • Avoid the complexity of distributed infrastructure
  • Use SystemAPI to automate management across multiple servers

Managing Multiple Single-Node Systems ​

If you deploy multiple independent VoipNow systems, you can use SystemAPI to automate and control operations across all your servers. SystemAPI provides:

  • Centralized Management: Control multiple VoipNow servers from a single interface
  • Automation: Automate provisioning, configuration, and management tasks
  • Integration: Integrate with your existing provisioning and billing systems
  • Scalability: Manage hundreds of servers programmatically

For more information, see the SystemAPI documentation.

High Availability ​

Both single and distributed deployments can be configured for High Availability (HA).

Cloud Infrastructure HA ​

Cloud providers offer built-in HA features:

  • Automatic Failover: Virtual machines automatically restart on different hosts
  • Load Balancing: Distribute traffic across multiple instances
  • Redundant Storage: Data replicated across multiple locations
  • Multi-Zone Deployment: Deploy across availability zones for redundancy

On-Premises Infrastructure HA ​

If running on your own infrastructure, HA requires:

  • Redundant power, networking, and storage
  • Virtualization-level HA (VMware vSphere, KVM/QEMU, OpenStack)
  • Infrastructure monitoring and incident detection
  • Professional data center management

""

Provisioning HA on your own infrastructure is expensive and complex. This is another reason cloud infrastructure is recommended.

Need Help Deciding? ​

"Contact 4PSA Support"

If you're unsure which deployment model is right for your needs, please contact 4PSA support for expert advice. Our team can help you:

  • Evaluate your requirements and growth projections
  • Choose the best deployment model for your situation
  • Plan your infrastructure and scaling strategy
  • Provide guidance on migration paths

What's Next? ​

Based on your choice:

For automation and managing multiple servers, see:

  • SystemAPI - API for controlling and automating VoipNow operations
Last updated: Dec 17, 2025