us-west1 and 730 hours per month. It does not include sustained use discounts, which Google Cloud applies automatically to N2 and N2D VMs. The database, Redis, and node pool sizes are the defaults for a new data plane. Application and SmithDB node counts are based on a LangChain-operated test data plane with low tracing volume. LangSmith increases capacity as tracing volume requires it.
Scaling capacity for any resource can be lowered when required, as long as the deployment remains within safe operating limits.
Rough monthly estimate
Sandboxes are excluded from this estimate. See Sandbox add-on.
Estimated monthly total, excluding sandboxes: $2,495–$4,207
Notes on the estimate
- Cloud SQL prices both the primary and the standby for high availability. Storage grows automatically, and backup storage beyond the included allowance costs extra.
- SmithDB keeps its caches on local SSD. They are not separately billed persistent disks. If the first SmithDB pool cannot add a node, for example during a zonal stockout, GKE scales up a fallback pool instead:
n2d-standard-16, thenc3-standard-22-lssd, thenc3d-standard-30-lssd. - Cloud NAT costs $0.0014 per VM per hour, plus $0.045 per GB processed.
- Cloud Logging receives VPC flow logs from every data plane subnet. Ingestion beyond the free monthly allowance is billed per GB.
SmithDB object store pricing
SmithDB stores trace data in the data plane’s Cloud Storage bucket, at Standard storage pricing of $0.020 per GB per month inus-west1. The figures assume about 2 million traces per month.
See Prepare SmithDB supporting infrastructure for details of SmithDB infrastructure.
Sandbox add-on
If your data plane runs sandboxes, budget separately for these resources:See also
- Google Cloud pricing calculator
- Compute Engine VM pricing
- GKE pricing
- Cloud SQL pricing
- Memorystore for Redis Cluster pricing
- Cloud NAT pricing
- BYOC architecture on GCP
- Configure SmithDB for scale
Connect these docs to your agent of choice via MCP for real-time answers.

