NCache Deployment

Cache Cloud is provisioned natively inside your own cloud account and virtual network—whether on Microsoft Azure (as an Azure Managed Application) or Amazon Web Services (AWS) (via AWS CloudFormation). While the deployment, lifecycle orchestration, monitoring agent configuration, and patching are fully automated, you retain ownership of the underlying infrastructure, network boundaries, and direct cloud compute billing.

Deployment Architecture and Tenant Isolation

NCache Cloud operates within an isolated architecture:

100% In-Tenant Footprint: Cache servers deploy directly into a dedicated subnet within your chosen Azure Virtual Network. Data, access logs, and diagnostic telemetry remain in your environment.
Separation of Software and Infrastructure: Software licensing and infrastructure costs are billed independently. You pay your cloud provider directly for the underlying compute (Azure VMSS or AWS ASG), networking, and storage at your negotiated rates, allowing reserved instances and enterprise discounts to apply directly.
Network and Management Boundary:
- Private Data Channel: Client applications connect to the cluster via internal private endpoints (e.g., port 9800) over your private VNet.
- Management Interfaces: The NCache Cloud Portal and NCache Management Center run inside your network (accessible over HTTPS via Azure Front Door or AWS CloudFront with optional IP restrictions). Cache servers do not require public IP addresses.
Vendor Access Restrictions: The vendor has no persistent or standing access to your servers, network, or data. If technical assistance is required, access must be explicitly granted per incident via temporary access mechanisms (JIT policies on Azure or tokenized IAM roles on AWS) for a limited window (1, 2, or 4 hours), with operations audited directly to your monitoring logs.
Native Telemetry Integration: Cluster telemetry is collected via native monitoring agents pre-installed on the host nodes (Azure Monitor Agent or CloudWatch agent), forwarding metrics, logs, and traces directly into your workspace without traversing public networks.

Cloud Marketplace Offerings and Billing Models

NNCache Cloud is available through cloud marketplaces under three software licensing plans:

Hourly (Pay-As-You-Go)
- Consumption-based software pricing billed directly to your cloud invoice on a per-server-hour basis.
- Eliminates the need for manual license activation keys - nodes register and activate automatically upon VMSS boot.
- Offers various server profiles (e.g., 4 GB, 8 GB, 16 GB, 32 GB, 64 GB, and 256 GB configurations).
Free Trial (30-Day Evaluation)
- Provides complete enterprise feature access with no memory or server-profile restrictions for a 30-day evaluation period.
- Software usage is fully waived, and you are responsible only for the underlying cloud infrastructure compute.
BYOL (Bring Your Own License)
- Allows organizations with existing NCache Enterprise licenses to apply them to cloud deployments.
- You incur zero NCache software charges via the marketplace bill, paying only for the underlying cloud resources.
- Facilitates multi-cloud or hybrid migrations from on-premises deployments without repurchasing software licenses.

When to Choose Which Plan

Pick the option that best fits your needs:

Free Trial (30 Days): Choose this to test NCache, run a proof of concept, or evaluate features before buying.
Hourly (Pay-As-You-Go): Choose this if your traffic changes often, you want flexible scale without managing license keys, or you want to pay through your cloud bill.
Bring Your Own License (BYOL): Choose this if your company already bought NCache licenses from Alachisoft and just wants to run them in the cloud.

Marketplace Support Plans

Alongside the software plan, NCache Cloud provides two support tiers selected during marketplace provisioning:

Standard Support:
- Technical support during standard business hours.
- Covers routine operational queries, configuration assistance, and general troubleshooting.
Premium Support:
- 24/7 priority technical support designed for mission-critical production environments.
- Includes faster target response times, priority SLA escalation paths, and support for high-severity production outage incidents.

RESP Server Management

Because NCache Cloud operates as a fully managed service where users do not have direct terminal or SSH login access to underlying cache servers, NCache automatically manages Redis Serialization Protocol (RESP) server bindings:

Automatic Port Allocation: Whenever a cache is created or deleted via the NCache Management Center or PowerShell cmdlets, the system automatically enables or disables the RESP server by updating the resp.ncconf file.
Port Limits: NCache Cloud allocates a dedicated block of 9 ports for RESP-enabled caches, supporting up to 9 concurrent RESP-enabled cache instances per deployment. Beyond this limit, manual port mapping reconfiguration is not supported within the managed cloud environment.