eastus, Linux VMs, and 730 hours per month. The database and system node sizes match the default profile. Application and SmithDB node counts are assumptions, not fixed deployment sizes. AKS node auto-provisioning selects VM sizes and counts within each pool’s limits.
Rough monthly estimate
This example budget assumes two to six application nodes, one SmithDB cache node, and one SmithDB compute node. Each compute row covers a separate set of VMs. SmithDB compute is not included in the application node estimate.Sandboxes are excluded from the baseline, including their host compute, storage, and private endpoint. The estimate does not imply that sandboxes are disabled by default or that a self-service opt-out is available.
Estimated monthly subtotal for priced items, excluding sandboxes: $3,283–$4,460, or about $3.3k–$4.5k. Add the additional charges above, taxes, and LangSmith fees to estimate the full bill.
The system-node reduction from three
Standard_D4s_v6 to three Standard_D2s_v6 saves about $221 per month in VM compute. The older D8s_v5-only SmithDB estimate does not represent the dedicated NVMe pool. Smaller system nodes alone do not establish a lower total bill.
The PostgreSQL estimates use $0.089 per vCore-hour and $0.115 per GiB-month of provisioned storage. Each server has two vCores and a matching standby. Storage growth and backup storage beyond the included allowance cost extra.
The SmithDB cache example has 32 vCPUs and 128 GiB of memory. Azure-specific pod requests are 4 vCPUs and 8 GiB for query, 4 vCPUs and 8 GiB for ingestion, and 8 vCPUs and 16 GiB per compaction worker. Their cache requests are 200 GiB, 100 GiB, and 100 GiB per worker, respectively. These run on the dedicated local NVMe pool, separate from the compaction scheduler and cluster manager. Replica counts, scheduling overhead, upgrades, and load can require more nodes. This example does not guarantee a throughput level or a highly available SmithDB node layout.
For networking, the NAT gateway alone costs about $33 per month before data processing. Without sandboxes and with control-plane private access enabled, seven explicit customer-side private endpoints cost about $51 per month: two PostgreSQL, two Blob storage, Redis, Key Vault, and control-plane access. The AKS management private endpoint runs in LangChain’s subscription and is not part of your bill. A Standard load balancer’s first five rules cost about $18.25 per month. These charges are not included in the subtotal. Add the resources and traffic for your deployment in the Azure pricing calculator.
Sandbox add-on
If your deployment includes sandboxes, budget separately for their dedicated host nodes, Blob storage, and private endpoint. One illustrativeStandard_D16ds_v6 host costs about $728 per month at $0.997/hour. Its private endpoint adds $7.30 per month, plus sandbox storage and traffic charges. Additional hosts increase the compute cost.
See also
- Azure retail prices API
- Azure pricing calculator
- Azure NAT Gateway pricing
- Azure Managed Redis pricing
- Azure Database for PostgreSQL pricing
- BYOC operations on Azure
- Configure SmithDB for scale
Connect these docs to your agent of choice via MCP for real-time answers.