Price, limit, tier and overage changes across 15 providers, newest first. RSS feed
Every Monday: what changed on the dev-infra pricing pages we track. One click to unsubscribe.
Supabase added a new 'pipelines' overage rate to the Team plan overage rates, priced at $0.053 per pipeline per hour + $3.00 per GB ongoing / $0.60 per GB initial sync. All other overage rate keys were unchanged.
Railway free tier modified on Trial (plans[Trial].included): {"credits":"$5 one-time (30 days)","projects":"5 during trial, then 1","build_timeout":"20 mins during trial, then 10 mins","log_retention":"7 days during trial, then 3","ephemeral_disk":"1 GB","object_storage":"50 GB during trial, then 10 GB","volume_storage":"0.5 GB","cpu_per_service":"Up to 1 vCPU (2 vCPU during trial)","ram_per_service":"Up to 0.5 GB (1 GB during trial)","concurrent_builds":"3 during trial, then 1","replicas_per_service":"2 during trial, then 1","services_per_project":"5 during trial, then 3"} → {"credits":"$5 one-time (30 days)","projects":"5 during trial, then 1","build_timeout":"20 mins during trial, then 10 mins","log_retention":"7 days during trial, then 3","custom_domains":"1 trial, then 0","ephemeral_disk":"1 GB","object_storage":"50 GB during trial, then 10 GB","volume_storage":"0.5 GB","cpu_per_service":"Up to 1 vCPU (2 vCPU during trial)","project_members":"1","ram_per_service":"Up to 0.5 GB (1 GB during trial)","service_domains":"2","build_image_size":"4 GB","max_sandbox_size":"2 vCPU / 2 GB","concurrent_builds":"3 during trial, then 1","buckets_per_project":"3 during trial, then 1","volumes_per_project":"3 during trial, then 1","default_sandbox_size":"2 vCPU / 2 GB","replicas_per_service":"2 during trial, then 1","services_per_project":"5 during trial, then 3","cron_jobs_per_project":"Free Trial only","running_sandboxes_per_env":"10"}.
Railway raised several included limits on the Hobby plan. Max sandbox size went from 2 vCPU / 2 GB to 8 vCPU / 8 GB, default sandbox size from 2 vCPU / 2 GB to 4 vCPU / 4 GB, replicas per service from up to 5 to up to 6 at 8 vCPU / 8 GB, and running sandboxes per environment from 10 to 50.
Railway raised several included limits on the Pro plan. Max sandbox size went from 8 vCPU / 8 GB to 32 vCPU / 32 GB, default sandbox size from 4 vCPU / 4 GB to 8 vCPU / 8 GB, and running sandboxes per environment from 50 to 100. Buckets per project (100) and volumes per project (20) were marked as 'can be increased'.
AWS Amplify's AWS Free Tier overage rates were restructured. The standard instance build key was renamed to build_standard at the same $0.01/minute, and a web application firewall rate of $15/month per Amplify app + WAF costs was added. Storage, data transfer, and SSR rates were unchanged.
AWS Amplify's AWS Free Tier included allowances were reordered and the SSR requests wording changed from 500,000 requests/month to 500,000/month. All quantities were unchanged: 1,000 build minutes, 5 GB storage, 15 GB data transfer out, 100 GB-hours SSR duration, 12 months duration.
AWS Amplify's AWS Free Tier feature list was reworded. The 'Amplify Hosting' and 'Backend powered by AWS services' entries were replaced with itemized backend services (Cognito auth, AppSync, DynamoDB, Lambda, S3), and 'Always free team collaboration' became 'No pay-per-seat pricing'.
AWS Amplify's Pay as you go plan monthly price changed from null to 0 cents. This reflects no base monthly fee and no change to a charged amount.
AWS Amplify's Pay as you go overage rate keys were renamed (for example, standard_instance_build to build_standard_instance) and data transfer out changed in wording from $0.15/GB served to $0.15/GB. All rates were unchanged, including $0.01/minute standard, $0.025/minute large, and $0.10/minute XLarge builds.
AWS Amplify's Pay as you go feature list was reworded. The SSR support, Web Application Firewall integration, and Standard/Large/XLarge build instance entries were no longer listed, and backend services were itemized as Cognito, AppSync, DynamoDB, Lambda, and S3.
Vercel limit changed on Hobby (plans[Hobby].included): {"isr_reads":"1M / month","isr_writes":"200k / month","drive_reads":"30 GB / month","ip_blocking":"Up to 3","blob_storage":"1 GB / month","cdn_requests":"1M / month","drive_writes":"30 GB / month","runtime_logs":"1 hour","drive_storage":"15 GB (lifetime)","flag_requests":"10K / month","tracing_spans":"1M span units / month","bulk_redirects":"1K per project","developer_seats":"1","session_tracing":"1 hour","workflow_events":"50K / month","fluid_active_cpu":"4 hours / month","service_requests":"1M / month","snapshot_storage":"15 GB","sandbox_creations":"5K / month","blob_data_transfer":"10 GB / month","daemons_active_cpu":"5 hours / month","fast_data_transfer":"100 GB / month","sandbox_active_cpu":"5 hours / month","ai_gateway_triggers":"1000 / month","custom_environments":"0","global_config_reads":"100K / month","concurrent_sandboxes":"10","fast_origin_transfer":"10 GB / month","function_invocations":"1M / month","global_config_writes":"100 / month","web_analytics_events":"50K / month","custom_firewall_rules":"Up to 3","queues_api_operations":"1M / month","sandbox_data_transfer":"20 GB / month","speed_insights_events":"10K events / team / rolling 30 days","blob_simple_operations":"10K / month","microfrontends_projects":"2","workflow_storage_writes":"1 GB","blob_advanced_operations":"2K / month","fluid_provisioned_memory":"360 GB-hrs / month","ai_gateway_token_requests":"500 / month","daemons_provisioned_memory":"420 GB-hrs / month","sandbox_provisioned_memory":"420 GB-hrs / month","firewall_rate_limit_requests":"1M allowed requests / month","image_optimization_cache_reads":"300K / month","microfrontends_routed_requests":"50K / month","image_optimization_cache_writes":"100K / month","container_registry_image_storage":"10 GB / month","image_optimization_transformations":"5K / month"} → {"cdn_requests":"1M / month","fast_data_transfer":"100 GB / month","firewall_rate_limit_requests":"1M allowed requests / month","custom_firewall_rules":"Up to 3","ip_blocking":"Up to 10","isr_reads":"1M / month","isr_writes":"200k / month","bulk_redirects":"1K per project","blob_storage":"1 GB / month","blob_simple_operations":"10K / month","blob_advanced_operations":"2K / month","blob_data_transfer":"10 GB / month","image_optimization_transformations":"5K / month","image_optimization_cache_reads":"300K / month","image_optimization_cache_writes":"100K / month","global_config_reads":"100K / month","global_config_writes":"100 / month","microfrontends_projects":"2","microfrontends_routing":"50K routed requests / month","fluid_active_cpu":"4 hours / month","fluid_provisioned_memory":"360 GB-hrs / month","function_invocations":"1M / month","service_requests":"1M / month","sandbox_active_cpu":"5 hours / month","sandbox_provisioned_memory":"420 GB-hrs / month","sandbox_creations":"5K / month","sandbox_data_transfer":"20 GB / month","concurrent_sandboxes":"10","snapshot_storage":"15 GB","drive_storage":"15 GB (lifetime)","drive_reads":"30 GB / month","drive_writes":"30 GB / month","daemons_active_cpu":"5 hours / month","daemons_provisioned_memory":"420 GB-hrs / month","container_registry_storage":"10 GB / month","fast_origin_transfer":"10 GB / month","workflow_events":"50K / month","workflow_storage_writes":"1 GB","queues_api_operations":"1M / month","ai_gateway_token_requests":"500 requests / month","ai_gateway_triggers":"1,000 / month","deployment_storage":"10 GB","developer_seats":"1","flag_overrides":"150 / month","flag_requests":"10K / month","web_analytics_events":"50K / month","tracing_spans":"1M span units / month","speed_insights_events":"10K events / team / rolling 30 days","runtime_logs_retention":"1 hour","session_tracing_retention":"1 hour","custom_environments":"0","seats":"1"}.
Vercel feature removed on Hobby (plans[Hobby].features): ["Import your repo, deploy in seconds","Automatic CI/CD","Web Application Firewall","Global, automated CDN","Fluid compute","DDoS Mitigation","Traffic & performance insights","HTTPS Certificates","TLS/SSL Encryption","Rewrites","Redirects","Middleware Support","Automated DDoS Mitigation","Zero-config CDN cache","Automated Compression","Incremental Static Regeneration (ISR)","Vercel Toolbar","OAuth Sign-in (GitHub, Google, GitLab, Bitbucket)","Multi-Factor Authentication (MFA)","SOC 2 Type 2","PCI DSS","ISO 27001","EU-U.S. DPF"] → ["Import your repo, deploy in seconds","Automatic CI/CD","Web Application Firewall","Global, automated CDN","Fluid compute","DDoS Mitigation","Traffic & performance insights","Automated DDoS Mitigation","AI Bots managed ruleset","Bot Protection managed ruleset","BotID basic checks","Attack Challenge Mode","Zero-config CDN cache","Automated Compression","Background Revalidation","Stale-While-Revalidate","Incremental Static Regeneration (ISR)","Unlimited Deployments","Instant Rollback","OAuth Sign-in (GitHub, Google, GitLab, Bitbucket)","Multi-Factor Authentication (MFA)","SOC 2 Type 2","PCI DSS","ISO 27001","EU-U.S. DPF"].
Vercel overage rate changed on Pro (plans[Pro].overage_rates): {"saml_sso":"$300 / month","hipaa_baa":"$350 / month","isr_reads":"$0.40 per 1M","isr_writes":"$4 per 1M","static_ips":"$100 / project / month + $0.15 per GB","drive_reads":"$0.0015 per GB","blob_storage":"$0.023 per GB","drive_writes":"$0.004 per GB","drive_storage":"$0.05 per GB-month","flag_requests":"$0.03 per 1K requests","tracing_spans":"$0.50 per 1M span units","developer_seat":"$20 / month","ai_agent_tokens":"$0.25 per million tokens + pass-through","workflow_events":"$20 per 1,000,000","fluid_active_cpu":"$0.128 per hour","service_requests":"$0.50 per 1M","snapshot_storage":"$0.08 per GB-month","log_drains_volume":"$0.50 per 1 GB","sandbox_creations":"$0.60 per 1,000,000","daemons_active_cpu":"$0.128 per hour","sandbox_active_cpu":"$0.128 per hour","web_analytics_plus":"$10 / month","ai_gateway_triggers":"$0.95 per 1,000 triggers","botid_deep_analysis":"$1 per 1,000 checks","build_minutes_basic":"$0.007 per minute","build_minutes_turbo":"$0.105 per minute","global_config_reads":"$3 per 1M","password_protection":"$20 / project / month","speed_insights_plus":"$10 / project / month, $0.65 per 10K events","fast_origin_transfer":"$0.06 per GB","function_invocations":"$0.60 per 1M","global_config_writes":"$1 per 100","observability_events":"$1.20 per 1M events","web_analytics_events":"$3 per 100K events","build_minutes_elastic":"$0.0035 per CPU minute","queues_api_operations":"$0.60 per 1M","blob_simple_operations":"$0.40 per 1M","build_minutes_enhanced":"$0.028 per minute","build_minutes_standard":"$0.014 per minute","microfrontends_routing":"$2 per 1M routed requests","workflow_storage_writes":"$0.50 per GB","blob_advanced_operations":"$5 per 1M","flag_overrides_unlimited":"$250","fluid_provisioned_memory":"$0.0106 per GB-hr","ai_gateway_token_requests":"$3.00 per 1,000 requests","bulk_redirects_additional":"$50 / month per 25K","preview_deployment_suffix":"$100 / month","daemons_provisioned_memory":"$0.0212 per GB-hr","sandbox_provisioned_memory":"$0.0212 per GB-hr","workflow_storage_retention":"$0.50 per GB-month","firewall_rate_limit_requests":"$0.50 per 1M allowed requests","image_optimization_cache_reads":"$0.40 per 1M","image_optimization_cache_writes":"$4 per 1M","container_registry_image_storage":"$0.10 per GB-month","microfrontends_additional_project":"$250 per additional project","image_optimization_transformations":"$0.05 per 1K"} → {"firewall_rate_limit_requests":"$0.50 per 1M allowed requests","botid_deep_analysis":"$1 per 1,000 checks","isr_reads":"$0.40 per 1M","isr_writes":"$4 per 1M","bulk_redirects":"$50 / month per 25K","blob_storage":"$0.023 per GB","blob_simple_operations":"$0.40 per 1M","blob_advanced_operations":"$5 per 1M","image_optimization_transformations":"$0.05 per 1K","image_optimization_cache_reads":"$0.40 per 1M","image_optimization_cache_writes":"$4 per 1M","global_config_reads":"$3 per 1M reads","global_config_writes":"$1 per 100 writes","microfrontends_additional_project":"$250 per additional project","microfrontends_routing":"$2 per 1M routed requests","fluid_active_cpu":"$0.128 per hour","fluid_provisioned_memory":"$0.0106 per GB-hr","function_invocations":"$0.60 per 1M","service_requests":"$0.50 per 1M","sandbox_active_cpu":"$0.128 per hour","sandbox_provisioned_memory":"$0.0212 per GB-hr","sandbox_creations":"$0.60 per 1,000,000 creations","snapshot_storage":"$0.08 per GB-month","drive_storage":"$0.05 per GB-month","drive_reads":"$0.0015 per GB","drive_writes":"$0.004 per GB","daemons_active_cpu":"$0.128 per hour","daemons_provisioned_memory":"$0.0212 per GB-hr","container_registry_storage":"$0.10 per GB-month","fast_origin_transfer":"$0.06 per GB","workflow_events":"$20 per 1,000,000 events","workflow_storage_writes":"$0.50 per GB","workflow_storage_retention":"$0.50 per GB-month","queues_api_operations":"$0.60 per 1M","vercel_agent":"$0.25 / million tokens + pass-through","ai_gateway_token_requests":"$3.00 per 1,000 requests","ai_gateway_triggers":"$0.95 per 1,000 triggers","build_minutes_basic":"$0.007 per minute","build_minutes_standard":"$0.014 per minute","build_minutes_enhanced":"$0.028 per minute","build_minutes_turbo":"$0.105 per minute","build_minutes_elastic":"$0.0035 per CPU minute","deployment_storage":"$0.10 per GB-month","preview_deployment_suffix":"$100 / month","developer_seat":"$20 / month","flag_overrides":"$250 for unlimited overrides","flag_requests":"$0.03 per 1K requests","observability_events":"$1.20 per 1M events","speed_insights_plus":"$10 / project / month","web_analytics_events":"$3 per 100K events","web_analytics_plus":"$10 / month","tracing_spans":"$0.50 per 1M span units","drains_volume":"$0.50 per 1 GB","saml_sso":"$300 / month","password_protection":"$20 / project / month","static_ips":"$100 / project / month + $0.15 per GB","hipaa_baa":"$350 / month"}.
Vercel limit changed on Pro (plans[Pro].included): {"ip_blocking":"Up to 100","cdn_requests":"Included in Flat Rate CDN","runtime_logs":"1 day (30 days with Observability Plus)","viewer_seats":"Unlimited","billing_seats":"1","bulk_redirects":"1K per project","flags_overrides":"150 / month","session_tracing":"1 day","rolling_releases":"1 project","fast_data_transfer":"Included in Flat Rate CDN","custom_environments":"1","system_bypass_rules":"Up to 25","concurrent_sandboxes":"10K","custom_firewall_rules":"Up to 40","included_usage_credit":"$20","speed_insights_events":"10K events / team / rolling 30 days","microfrontends_projects":"2","firewall_rate_limit_requests":"included via usage credit"} → {"usage_credit":"$20","cdn_requests":"Included in Flat Rate CDN","fast_data_transfer":"Included in Flat Rate CDN","firewall_rate_limit_requests":"included then $0.50 per 1M","custom_firewall_rules":"Up to 40","ip_blocking":"Up to 40","system_bypass_rules":"Up to 10","microfrontends_projects":"2","concurrent_sandboxes":"10K","custom_environments":"1","developer_seats":"$20 / month per seat","viewer_seats":"Unlimited free","billing_seats":"1","skew_protection_projects":"1","runtime_logs_retention":"1 day (30 days with Observability Plus)","session_tracing_retention":"1 day","speed_insights_events":"10K events / team / rolling 30 days"}.
Vercel feature removed on Pro (plans[Pro].features): ["All Hobby features","$20 of included usage credit","Flat Rate CDN with traffic spike protection","Advanced spend management","Team collaboration & free viewer seats","Cold start prevention","Free custom domain","Private Inter-Region Network","Automatic Region Failover","Configurable Routing","Reverse Proxy","Bot Protection (managed ruleset)","AI Bots (managed ruleset)","Attack Challenge Mode","Vercel Sandbox","Vercel Drives","Vercel Daemons","Vercel Workflows","AI Gateway","v0 (paid add-on)","Vercel Agent (beta)","Webhook Triggers","Custom Environments","Rolling Releases","Preview Deployment Suffix","Role-Based Access Control (Team level)","SAML Single Sign-On (SSO)","Password Protection","Static IPs (shared pool)","HIPAA BAA","Comments","Layout Shift Tool","Draft Mode","Accessibility Audit","Marketplace Integrations"] → ["All Hobby features","$20 of included usage credit","Flat Rate CDN with traffic spike protection","Advanced spend management","Team collaboration & free viewer seats","Cold start prevention","Free custom domain","Role-Based Access Control (Team level)","SAML Single Sign-On (SSO) add-on","Password Protection add-on","Static IPs (shared pool) add-on","HIPAA BAA add-on","Custom Environments","Skew Protection","Rolling Releases","Unlimited Previewers","Accessibility Audit","v0 paid add-on","Vercel Agent (Beta)","AI Gateway","Marketplace Integrations"].
Vercel free tier modified on Enterprise (plans[Enterprise].included): {"sla":"99.99%","ip_blocking":"Up to 1,000","runtime_logs":"3 days (30 days with Observability Plus)","viewer_seats":"Unlimited","billing_seats":"Custom","session_tracing":"3 days","custom_environments":"12 environments","system_bypass_rules":"Up to 100","custom_firewall_rules":"Up to 1,000","web_analytics_reporting_windows":"24 months","observability_extended_retention":"30 days"} → {"custom_firewall_rules":"Up to 250","ip_blocking":"Up to 250","system_bypass_rules":"Up to 75","custom_environments":"12 environments","viewer_seats":"Unlimited","runtime_logs_retention":"3 days (30 days with Observability Plus)","session_tracing_retention":"3 days","observability_extended_retention":"30 days"}.
Vercel feature removed on Enterprise (plans[Enterprise].features): ["All Pro features","Guest & Team access controls","SCIM & Directory Sync","Managed WAF Rulesets","Multi-region compute & failover","99.99% SLA","Advanced Support","OWASP Core Ruleset (managed)","Passport","SSO Protected Previews","Secure Compute","BYOC","Role-Based Access Control (Team & project level)","Audit Logs","Directory Sync (SCIM)","Advanced metrics","Query engine","Alerts","UTM Parameters","TISAX","Custom Security Questionnaire","Custom invoicing"] → ["All Pro features","Guest & Team access controls","SCIM & Directory Sync","Managed WAF Rulesets","Multi-region compute & failover","99.99% SLA","Advanced Support","OWASP Core Ruleset (managed)","Role-Based Access Control (Team & project level)","Audit Logs","SAML Single Sign-On (SSO)","Directory Sync (SCIM)","Passport","SSO Protected Previews","Secure Compute","BYOC","TISAX","Custom Security Questionnaire","HIPAA BAA","Advanced metrics","Query engine","Alerts","Custom invoicing"].
Upstash added 'Primary Replicas' to the Free plan feature list. A duplicate 'REST API' entry was also removed from the list.
Upstash removed the extra databases overage rate ($0.5 per database beyond 10) from the Pay as You Go plan. The storage ($0.25 per GB) and commands ($0.20 per 100K commands) rates were unchanged, and the bandwidth rate stayed at $0.03/GB after 200 GB (formatting only).
Upstash restructured the Pay as You Go included allowances. Bandwidth changed from 'Unlimited (free up to 200 GB, then metered)' to 'Unlimited' with a separate 'free_bandwidth' of 200 GB/month, and the free storage entry changed from '1 GB free' to '1 GB'. Other limits were unchanged.
Upstash's Pay as You Go feature list changed 'Budget limit' to 'Budget limits'. It also added IP Allowlist, Community Support and Email Support.
Upstash removed the prod_pack overage rate (+$200/month per database) from the Fixed 250MB plan. The read_region rate stayed at +$5/region.
Upstash removed 'Global replication' from the Fixed 250MB plan features. It added IP Allowlist, Primary Replicas and Email Support.
Upstash removed the prod_pack overage rate (+$200/month per database) from the Fixed 1GB plan. The read_region rate stayed at +$10/region.
Upstash's Fixed 1GB plan no longer lists the 'monthly_commands: Unlimited' entry in its included limits. Data size (1 GB), bandwidth (100 GB), 10,000 commands per second, 10 MB request size and 200 MB record size were unchanged.
Upstash removed the prod_pack overage rate (+$200/month per database) from the Fixed 5GB plan. The read_region rate stayed at +$50/region.
Upstash's Fixed 5GB plan no longer lists the 'monthly_commands: Unlimited' entry in its included limits. Data size (5 GB), bandwidth (500 GB), 10,000 commands per second, 20 MB request size and 300 MB record size were unchanged.
Upstash removed the prod_pack overage rate (+$200/month per database) from the Fixed 10GB plan. The read_region rate stayed at +$100/region.
Upstash's Fixed 10GB plan no longer lists the 'monthly_commands: Unlimited' entry in its included limits. Data size (10 GB), bandwidth (1 TB), 10,000 commands per second, 30 MB request size and 400 MB record size were unchanged.
Upstash removed the prod_pack overage rate (+$200/month per database) from the Fixed 50GB plan. The read_region rate stayed at +$200/region.
Upstash's Fixed 50GB plan no longer lists the 'monthly_commands: Unlimited' entry in its included limits. Data size (50 GB), bandwidth (5 TB), 10,000 commands per second, 50 MB request size and 500 MB record size were unchanged.
Upstash removed the prod_pack overage rate (+$200/month per database) from the Fixed 100GB plan. The read_region rate stayed at +$400/region.
Upstash's Fixed 100GB plan no longer lists the 'monthly_commands: Unlimited' entry in its included limits. Data size (100 GB), bandwidth (10 TB), 16,000 commands per second, 75 MB request size and 1 GB record size were unchanged.
Upstash removed the prod_pack overage rate (+$200/month per database) from the Fixed 500GB plan. The read_region rate stayed at +$750/region.
Upstash's Fixed 500GB plan no longer lists the 'monthly_commands: Unlimited' entry in its included limits. Data size (500 GB), bandwidth (20 TB), 16,000 commands per second, 100 MB request size and 5 GB record size were unchanged.
Upstash removed '100K+ commands per second' and 'Unlimited bandwidth and database count' from the Enterprise plan features. It added Private Link and 'Primary and Read Replicas', and renamed 'SAML Single Sign-On (SSO)' to 'SAML SSO'.
Render's Hobby plan overage rate data was restructured: the key 'persistent_disk' was renamed 'persistent_disks'. All rates were unchanged, including bandwidth at $0.15/GB, build minutes at $5 per 1K mins, custom domains at $0.25/domain/month, persistent disk at $0.25/GB/month and Postgres storage at $0.30/GB.
Render's Hobby plan included-limits data changed only in format: 'environments' with the value '2 per project' became 'environments_per_project' with the value '2'. Seats (1), services (25), bandwidth (5 GB), build minutes (500) and the other limits were unchanged.
Render's Hobby plan feature list no longer includes Vertical scaling, SSH access, Health checks and Service metrics. Service discovery and Automatic DDoS mitigation were added. The data does not show whether the removed items were dropped from the plan or only from the listing.
Render's Pro plan overage rate data was restructured: 'performance_build_minutes' became 'performance_build_pipeline' and 'persistent_disk' became 'persistent_disks'. All rates were unchanged, including $25 per 1000 mins for the performance build pipeline and $0.25/GB/month for persistent disks.
Render's Pro plan included-limits data changed only in format: 'environments' (Unlimited) became 'environments_per_project' (Unlimited). Seats, services, bandwidth (25 GB), build minutes (1K) and the other limits were unchanged.
Render's Pro plan feature list no longer includes 'Workspace user roles (Admin, Developer)'. Read-only replicas, High availability and Performance build pipeline were added to the list.
Render's Scale plan overage rate data was restructured: 'performance_build_minutes' became 'performance_build_pipeline', 'persistent_disk' became 'persistent_disks', and 'hipaa_premium' ('20% compute premium') became 'hipaa_compute_premium' ('20%'). All rate values were unchanged.
Render's Scale plan included-limits data changed only in format: 'environments' (Unlimited) became 'environments_per_project' (Unlimited). Bandwidth (1 TB), build minutes (5K per workspace), custom domains (25) and the other limits were unchanged.
Render's Scale plan feature list no longer includes 'Workspace user roles (Admin, Developer, Contributor, Viewer, Billing)'. 'Organization user roles (Owner, Member, Guest)' was shortened to 'Organization user roles', and Network-isolated environments was added.
Render's Enterprise plan overage rate data changed only in naming: 'persistent_disk' became 'persistent_disks'. Persistent disk stayed at $0.25/GB/month and Postgres storage at $0.30/GB.
Render's Enterprise plan feature list no longer includes 'SOC 2 & ISO documentation'. All other listed features were unchanged.
DO App Platform added a new plan, Shared (Fixed) 1 vCPU / 1 GiB, at $10.00/mo. It includes 1 vCPU, 1 GiB memory, and 100 GiB bandwidth, with no autoscaling, a limit of one container instance, and a bandwidth overage rate of $0.02/GiB.
DO App Platform added a new plan, Shared 1 vCPU / 1 GiB, at $12.00/mo. It includes 1 vCPU, 1 GiB memory, and 150 GiB bandwidth, with no autoscaling and a bandwidth overage rate of $0.02/GiB.
DO App Platform added a new plan, Shared 1 vCPU / 2 GiB, at $25.00/mo. It includes 1 vCPU, 2 GiB memory, and 200 GiB bandwidth, with no autoscaling and a bandwidth overage rate of $0.02/GiB.
DO App Platform added a new plan, Shared 2 vCPUs / 4 GiB, at $50.00/mo. It includes 2 vCPUs, 4 GiB memory, and 250 GiB bandwidth, with no autoscaling and a bandwidth overage rate of $0.02/GiB.
DO App Platform renamed the Free Tier included field data_transfer_per_app to bandwidth_per_app. The value stayed at 1 GiB, and the 3 static-site apps and unlimited team members were unchanged.
DO App Platform renamed the Paid Tier included field data_transfer to bandwidth, with the value unchanged at 50 GiB. It also listed 'Up to 10 revisions for rollbacks' under included resources; the vCPU (1 vCPU) and memory (512 MiB) values were unchanged.
DO App Platform added 'All Free Tier features' to the top of the Paid Tier feature list. The other eleven listed features were unchanged.
Heroku removed the "Resource scalability" feature from the Key-Value Store Premium 5 plan.
Heroku renamed fields in the Postgres Standard-2 limits (disk_size to disk, connection_limit to connections). The values stayed the same: 8 GB RAM, 256 GB disk, 400 connections.
Heroku renamed fields in the Postgres Premium-0 limits (disk_size to disk, connection_limit to connections). The values stayed the same: 4 GB RAM, 64 GB disk, 120 connections.
Heroku changed the Performance-M Dyno field from dyno_units_per_month "8" to dyno_units "8/month". The allowance stayed at 8 and only the labeling changed.
Heroku renamed the included-limit field for the Private-M Dyno from dyno_units_per_month (10) to dyno_units (10/month). RAM (2.5 GB) and compute (12x) were unchanged.
Heroku added a 'Private Space required' feature entry to Postgres Private-5, alongside 'Network isolation in Private Space'.
Heroku removed "No row limitations" from the Postgres Standard-2 feature list and added "Priority service restoration".
Heroku added "Private Space required" to the feature list of the Fir Classic 2CPU-1GB plan.
Heroku renamed fields in the Postgres Standard-0 limits (disk_size to disk, connection_limit to connections). The values stayed the same: 4 GB RAM, 64 GB disk, 120 connections.
Heroku added a 'Private Space required' feature entry to Postgres Private-L-6, alongside 'Network isolation in Private Space'.
Heroku removed the Dyno Shield-L-RAM plan, previously listed at $600/mo with 30 GB RAM and 24 dyno units per month.
Heroku removed the Key-Value Store Private-3 plan, previously listed at $150/mo with 500 MB RAM and a 400 connection limit.
Heroku removed the Postgres Private-0 plan, previously listed at $300/mo with 4 GB RAM, 68 GB disk and a 120 connection limit.
Heroku removed the Dyno Performance-L-RAM plan, previously listed at $500/mo with 30 GB RAM and 16 dyno units per month.
Heroku removed the Dyno Private-L-RAM plan, previously listed at $500/mo with 30 GB RAM and 20 dyno units per month.
Heroku removed the Postgres Private-2 plan, previously listed at $600/mo with 8 GB RAM, 256 GB disk and a 400 connection limit.
Heroku added the Key-Value Store Private-0 (300) plan at $300/mo with 500 MB RAM and 400 connections.
Heroku added the Key-Value Store Private-2 plan at $600/mo with 500 MB RAM and 400 connections.
Heroku added the Key-Value Store Private-7 plan at $900/mo with 7 GB RAM and 10,000 connections.
Heroku changed the Basic Dyno included-limits field from dyno_units_per_month "0.28" to dyno_units "0.28/month". The allowance stayed at 0.28 and only the labeling changed.
Heroku renamed fields in the Postgres Essential-0 limits (disk_size to disk, connection_limit to connections) and wrote the table limit as 4000 instead of 4,000. The values stayed the same: 1 GB disk, 20 connections, 4,000 tables.
Heroku renamed fields in the Postgres Essential-1 limits (disk_size to disk, connection_limit to connections) and wrote the table limit as 4000 instead of 4,000. The values stayed the same: 10 GB disk, 20 connections.
Heroku renamed fields in the Postgres Essential-2 limits (disk_size to disk, connection_limit to connections) and wrote the table limit as 4000 instead of 4,000. The values stayed the same: 32 GB disk, 40 connections.
Heroku renamed the Key-Value Store Mini field connection_limit to connections. The value stayed at 20 and RAM stayed at 25 MB.
Heroku renamed the Key-Value Store Premium 0 field connection_limit to connections. The value stayed at 40 and RAM stayed at 50 MB.
Heroku changed the Standard-1X Dyno field from dyno_units_per_month "1" to dyno_units "1/month". The allowance stayed at 1 and only the labeling changed.
Heroku added the feature "Available in multiple global regions" to the Fir Classic 1CPU-0.5GB plan.
Heroku renamed the Key-Value Store Premium 1 field connection_limit to connections. The value stayed at 80 and RAM stayed at 100 MB.
Heroku changed the Standard-2X Dyno field from dyno_units_per_month "2" to dyno_units "2/month". The allowance stayed at 2 and only the labeling changed.
Heroku changed the Postgres Standard-0 feature "Dedicated server (not shared)" to "Dedicated server" and added "Max downtime 1 hour per month". The other listed features were unchanged.
Heroku renamed the Key-Value Store Premium 2 field connection_limit to connections. The value stayed at 200 and RAM stayed at 250 MB.
Heroku removed "Private network and data services" from the Fir General Purpose 2CPU-4GB feature list and added "Private Space required".
Heroku removed "Private network and data services" from the Fir Memory 1CPU-8GB feature list and added "Private Space required".
Heroku renamed the Key-Value Store Premium 3 field connection_limit to connections. The value stayed at 400 and RAM stayed at 500 MB.
Heroku removed the "Resource scalability" feature from the Key-Value Store Premium 3 plan.
Heroku changed the Private-S Dyno field from dyno_units_per_month "5" to dyno_units "5/month". The allowance stayed at 5 and only the labeling changed.
Heroku removed "Private network and data services" from the Private-S Dyno feature list. The other features were unchanged.
Heroku changed the Shield-S Dyno field from dyno_units_per_month "6" to dyno_units "6/month". The allowance stayed at 6 and only the labeling changed.
Heroku reworded the Shield-S Dyno feature "HIPAA BAA support" to "HIPAA compliance (BAA)" and added "Space level log drains" and "Private Space required".
Heroku removed "Private network and data services" from the Fir Compute 2CPU-4GB feature list and added "Private Space required".
Heroku renamed the Postgres Advanced 4G-Performance field included_storage to storage_included and changed "100 GB-mo" to "100GB-mo". The storage amount stayed at 100 GB-mo.
Heroku removed "Private network and data services" from the Fir General Purpose 2CPU-8GB feature list and added "Private Space required".
Heroku renamed the Key-Value Store Premium 5 field connection_limit to connections and wrote the value as 1000 instead of 1,000. The limit stayed the same.
Heroku removed 'Dedicated runtime environment' from the Private-M Dyno feature list. The other three listed features (Performance features, full network isolation, Private Space required) were unchanged.
Heroku added 'Private Space required' to the Fir Memory 2CPU-16GB feature list.
Heroku renamed connection_limit to connections (700) for Key-Value Store Private-5 and dropped the requires_private_space field from the included limits. RAM stayed at 750 MB.
Heroku replaced 'Region support' with 'Fork support' in the Key-Value Store Private-5 feature list, which removed the listed Region support. High availability and network isolation in Private Space were unchanged.
Heroku renamed the included-limit field for the Shield-M Dyno from dyno_units_per_month (12) to dyno_units (12/month). RAM and compute were unchanged.
Heroku removed 'Keystroke logging' from the Shield-M Dyno feature list and added 'Private Space required'. 'HIPAA BAA support' was reworded to 'HIPAA compliance (BAA)'.
Heroku added 'Private Space required' to the Fir Compute 4CPU-8GB feature list.
Heroku added a storage_included value of 100GB-mo to the Postgres Advanced 8G-Performance included limits. vCPU (2), memory (8 GB) and connections (800) were unchanged.
Heroku reworded 'High Availability' to 'High Availability (customer configurable)' in the Postgres Advanced 8G-Performance feature list.
Heroku added 'Private Space required' to the Fir General Purpose 4CPU-16GB feature list.
Heroku renamed the Postgres Premium-2 limit fields (disk_size to disk, connection_limit to connections). Values were unchanged at 8 GB RAM, 256 GB disk and 400 connections.
Heroku replaced 'Everything in Standard tier plans' with 'Max downtime 15 minutes per month' in the Postgres Premium-2 feature list. High Availability and 7-day rollback were unchanged.
Heroku renamed the Postgres Shield-0 limit fields (disk_size to disk, connection_limit to connections). Values were unchanged at 4 GB RAM, 68 GB disk and 120 connections.
Heroku renamed the Postgres Standard-3 limit fields (disk_size to disk, connection_limit to connections). Values were unchanged at 15 GB RAM, 512 GB disk and 500 connections.
Heroku removed 'No row limitations' from the Postgres Standard-3 feature list and added 'Rollback up to 4 days'. Dedicated server and fork and follow support were unchanged.
Heroku renamed the included-limit field for the Performance-L Dyno from dyno_units_per_month (16) to dyno_units (16/month). RAM and compute were unchanged.
Heroku removed 'Predictable performance' from the Performance-L Dyno feature list. Dedicated compute resources and autoscaling remained listed.
Heroku renamed the included-limit field for the Private-L Dyno from dyno_units_per_month (20) to dyno_units (20/month). RAM and compute were unchanged.
Heroku added 'Private Space required' to the Fir Memory 4CPU-32GB feature list.
Heroku added a storage_included value of 100GB-mo to the Postgres Advanced 16G-Performance included limits and reformatted connections from '1,600' to '1600'. The connection count itself was unchanged.
Heroku replaced 'High Availability' with 'Zero-downtime scaling' in the Postgres Advanced 16G-Performance feature list, which removed the listed High Availability.
Heroku renamed the included-limit field for the Shield-L Dyno from dyno_units_per_month (24) to dyno_units (24/month). RAM and compute were unchanged.
Heroku reworded 'HIPAA BAA support' to 'HIPAA compliance (BAA)' in the Shield-L Dyno feature list. No other features changed.
Heroku added 'Private Space required' to the Fir Compute 8CPU-16GB feature list.
Heroku renamed the included-limit field for the Performance-XL Dyno from dyno_units_per_month (30) to dyno_units (30/month). RAM and compute were unchanged.
Heroku replaced 'Predictable performance' with 'Dedicated compute resources' in the Performance-XL Dyno feature list. Autoscaling and the Standard features were unchanged.
Heroku renamed the included-limit field for the Private-XL Dyno from dyno_units_per_month (30) to dyno_units (30/month). RAM and compute were unchanged.
Heroku renamed the Postgres Standard-4 limit fields (disk_size to disk, connection_limit to connections). Values were unchanged at 30 GB RAM, 768 GB disk and 500 connections.
Heroku renamed the Postgres Premium-3 limit fields (disk_size to disk, connection_limit to connections). Values were unchanged at 15 GB RAM, 512 GB disk and 500 connections.
Heroku renamed the Postgres Shield-2 limit fields (disk_size to disk, connection_limit to connections). Values were unchanged at 8 GB RAM, 256 GB disk and 400 connections.
Heroku added a 'Private Space required' feature entry to Postgres Shield-7, alongside the existing 'HIPAA and PCI compliant' entry.
Heroku replaced 'Everything in Private tier plans' with 'Private Space required' in the Postgres Shield-2 feature list. 'HIPAA and PCI compliant' was unchanged.
Heroku renamed connection_limit to connections for Key-Value Store Premium 7 and reformatted the value from '10,000' to '10000'. The connection count and 7 GB RAM were unchanged.
Heroku renamed the included-limit field for the Shield-XL Dyno from dyno_units_per_month (36) to dyno_units (36/month). RAM and compute were unchanged.
Heroku reworded 'HIPAA BAA support' to 'HIPAA compliance (BAA)' in the Shield-XL Dyno feature list. No other features changed.
Heroku added a storage_included value of 100GB-mo to the Postgres Advanced 32G-Performance included limits and reformatted connections from '3,200' to '3200'. The connection count itself was unchanged.
Heroku removed 'High Availability' from the Postgres Advanced 32G-Performance feature list. Pay only for what you use and decoupled storage and compute remained listed.
Heroku renamed the Postgres Private-3 limit fields (disk_size to disk, connection_limit to connections). Values were unchanged at 15 GB RAM, 512 GB disk and 500 connections.
Heroku added 'Everything from Premium tier plans' to the Postgres Private-3 feature list.
Heroku renamed the Postgres Premium-4 limit fields (disk_size to disk, connection_limit to connections). Values were unchanged at 30 GB RAM, 768 GB disk and 500 connections.
Heroku Postgres Shield-3 included-limit field names changed (disk_size to disk, connection_limit to connections). Values stayed the same at 15 GB RAM, 512 GB disk and 500 connections.
Heroku added a 'Private Space required' feature entry to Postgres Shield-3, alongside the existing 'HIPAA and PCI compliant' entry.
Heroku Postgres Standard-5 included-limit field names changed (disk_size to disk, connection_limit to connections). Values stayed the same at 61 GB RAM, 1 TB disk and 500 connections.
Heroku removed 'No row limitations' from the Postgres Standard-5 feature list and added 'Fork and follow support'. 'Dedicated server' was unchanged.
Heroku Key-Value Store Premium 9 included-limit field name changed (connection_limit to connections) and the value format changed from '25,000' to '25000'. The limit stayed at 25,000 connections with 10 GB RAM.
Heroku reworded the Key-Value Store Premium 9 feature 'High availability' to 'High availability with low-latency failover'. 'Single tenant (dedicated server)' was unchanged.
Heroku added a 'Private Space required' feature entry to the Postgres Shield-10 plan, alongside the existing 'HIPAA and PCI compliant' entry.
Heroku Performance-2XL Dyno included-limit field changed from dyno_units_per_month '60' to dyno_units '60/month'. The value stayed at 60 per month, with 126 GB RAM and 100x compute.
Heroku removed the 'Predictable performance' feature entry from the Performance-2XL Dyno feature list. 'Includes all Standard features' and 'Autoscaling' remained.
Heroku Private-2XL Dyno included-limit field changed from dyno_units_per_month '60' to dyno_units '60/month'. The value stayed at 60 per month, with 126 GB RAM and 100x compute.
Heroku added a 'Private Space required' feature entry to Private-2XL Dyno, alongside 'Includes all Performance features' and 'Full network isolation'.
Heroku Postgres Private-4 included-limit field names changed (disk_size to disk, connection_limit to connections). Values stayed the same at 30 GB RAM, 768 GB disk and 500 connections.
Heroku added a 'Private Space required' feature entry to Postgres Private-4, alongside 'Network isolation in Private Space'.
Heroku Postgres Advanced 64G-Performance included limits added storage_included of 100GB-mo and changed the connections format from '5,000' to '5000'. vCPU (8) and memory (64 GB) were unchanged.
Heroku removed 'High Availability' from the Postgres Advanced 64G-Performance feature list. 'Pay only for what you use' and 'Decoupled storage and compute' remained.
Heroku Postgres Shield-4 included-limit field names changed (disk_size to disk, connection_limit to connections). Values stayed the same at 30 GB RAM, 768 GB disk and 500 connections.
Heroku added a 'Private Space required' feature entry to Postgres Shield-4, alongside 'HIPAA and PCI compliant'.
Heroku Shield-2XL Dyno included-limit field changed from dyno_units_per_month '72' to dyno_units '72/month'. The value stayed at 72 per month, with 126 GB RAM and 100x compute.
Heroku reworded the Shield-2XL Dyno feature 'HIPAA BAA support' to 'HIPAA compliance (BAA)'. 'PCI compliance' and 'Includes all Private features' were unchanged.
Heroku Postgres Standard-6 included-limit field names changed (disk_size to disk, connection_limit to connections). Values stayed the same at 122 GB RAM, 1.5 TB disk and 500 connections.
Heroku removed 'No row limitations' from the Postgres Standard-6 feature list. 'Dedicated server' remained.
Heroku Postgres Premium-5 included-limit field names changed (disk_size to disk, connection_limit to connections). Values stayed the same at 61 GB RAM, 1 TB disk and 500 connections.
Heroku Postgres Private-5 included-limit field names changed (disk_size to disk, connection_limit to connections). Values stayed the same at 61 GB RAM, 1 TB disk and 500 connections.
Heroku Postgres Advanced 128G-Performance included limits added storage_included of 100GB-mo and changed the connections format from '5,000' to '5000'. vCPU (16) and memory (128 GB) were unchanged.
Heroku Postgres Shield-5 included-limit field names changed (disk_size to disk, connection_limit to connections). Values stayed the same at 61 GB RAM, 1 TB disk and 500 connections.
Heroku added a 'Private Space required' feature entry to Postgres Shield-5, alongside 'HIPAA and PCI compliant'.
Heroku Postgres Standard-7 included-limit field names changed (disk_size to disk, connection_limit to connections). Values stayed the same at 244 GB RAM, 2 TB disk and 500 connections.
Heroku Postgres Premium-6 included-limit field names changed (disk_size to disk, connection_limit to connections). Values stayed the same at 122 GB RAM, 1.5 TB disk and 500 connections.
Heroku added a 'Roll back up to 7 days' feature to Postgres Premium-6, alongside 'High Availability'.
Heroku Key-Value Store Premium 10 included-limit field name changed (connection_limit to connections) and the value format changed from '40,000' to '40000'. The limit stayed at 40,000 connections with 25 GB RAM.
Heroku reworded the Key-Value Store Premium 10 feature 'High availability' to 'High availability with low-latency failover'. 'Single tenant (dedicated server)' was unchanged.
Heroku Postgres Private-6 included-limit field names changed (disk_size to disk, connection_limit to connections). Values stayed the same at 122 GB RAM, 1.5 TB disk and 500 connections.
Heroku added a 'Private Space required' feature entry to Postgres Private-6, alongside 'Network isolation in Private Space'.
Heroku Postgres Shield-6 included-limit field names changed (disk_size to disk, connection_limit to connections). Values stayed the same at 122 GB RAM, 1.5 TB disk and 500 connections.
Heroku added a 'Private Space required' feature entry to Postgres Shield-6, alongside 'HIPAA and PCI compliant'.
Heroku Postgres Standard-8 included-limit field names changed (disk_size to disk, connection_limit to connections). Values stayed the same at 488 GB RAM, 3 TB disk and 500 connections.
Heroku Postgres Premium-L-6 included-limit field names changed (disk_size to disk, connection_limit to connections). Values stayed the same at 122 GB RAM, 2 TB disk and 500 connections.
Heroku Postgres Advanced 256G-Performance included limits added storage_included of 100GB-mo and changed the connections format from '5,000' to '5000'. vCPU (32) and memory (256 GB) were unchanged.
Heroku Postgres Private-L-6 included-limit field names changed (disk_size to disk, connection_limit to connections). Values stayed the same at 122 GB RAM, 2 TB disk and 500 connections.
Heroku renamed the included-spec fields for Postgres Standard-9 from disk_size and connection_limit to disk and connections. The values were unchanged at 768 GB RAM, 4 TB disk and 500 connections.
Heroku renamed the included-spec fields for Postgres Premium-XL-6 from disk_size and connection_limit to disk and connections. The values were unchanged at 122 GB RAM, 3 TB disk and 500 connections.
Heroku renamed the included-spec fields for Postgres Premium-7 from disk_size and connection_limit to disk and connections. The values were unchanged at 244 GB RAM, 2 TB disk and 500 connections.
Heroku renamed the included-spec fields for Postgres Shield-L-6 from disk_size and connection_limit to disk and connections. The values were unchanged at 122 GB RAM, 2 TB disk and 500 connections.
Heroku added a 'Private Space required' feature entry to Postgres Shield-L-6, alongside the existing 'HIPAA and PCI compliant' entry.
Heroku renamed the connection_limit field to connections for Key-Value Store Premium 12 and changed its formatting from '65,000' to '65000'. The 65,000 connection limit and 50 GB RAM were unchanged.
Heroku changed the Key-Value Store Premium 12 feature text from 'High availability' to 'High availability with low-latency failover'. The 'Single tenant (dedicated server)' entry was unchanged.
Heroku renamed the included-spec fields for Postgres Private-XL-6 from disk_size and connection_limit to disk and connections. The values were unchanged at 122 GB RAM, 3 TB disk and 500 connections.
Heroku added a 'Private Space required' feature entry to Postgres Private-XL-6, alongside the existing 'Network isolation in Private Space' entry.
Heroku renamed the included-spec fields for Postgres Private-7 from disk_size and connection_limit to disk and connections. The values were unchanged at 244 GB RAM, 2 TB disk and 500 connections.
Heroku added a 'Private Space required' feature entry to Postgres Private-7, alongside the existing 'Network isolation in Private Space' entry.
Heroku added a storage_included value of 100GB-mo to Postgres Advanced 384G-Performance and reformatted connections from '5,000' to '5000'. The 48 vCPU, 384 GB memory and 5,000 connection figures were unchanged.
Heroku renamed the included-spec fields for Postgres Shield-XL-6 from disk_size and connection_limit to disk and connections. The values were unchanged at 122 GB RAM, 3 TB disk and 500 connections.
Heroku added a 'Private Space required' feature entry to Postgres Shield-XL-6, alongside the existing 'HIPAA and PCI compliant' entry.
Heroku renamed the included-spec fields for Postgres Shield-7 from disk_size and connection_limit to disk and connections. The values were unchanged at 244 GB RAM, 2 TB disk and 500 connections.
Heroku renamed the included-spec fields for Postgres Premium-8 from disk_size and connection_limit to disk and connections. The values were unchanged at 488 GB RAM, 3 TB disk and 500 connections.
Heroku added a storage_included value of 100GB-mo to Postgres Advanced 512G-Performance and reformatted connections from '5,000' to '5000'. The 64 vCPU, 512 GB memory and 5,000 connection figures were unchanged.
Heroku added a 'Decoupled storage and compute' feature entry to Postgres Advanced 512G-Performance, alongside the existing 'Pay only for what you use' entry.
Heroku renamed the included-spec fields for Postgres Private-8 from disk_size and connection_limit to disk and connections. The values were unchanged at 488 GB RAM, 3 TB disk and 500 connections.
Heroku added a 'Private Space required' feature entry to Postgres Private-8, alongside the existing 'Network isolation in Private Space' entry.
Heroku renamed the included-spec fields for Postgres Premium-9 from disk_size and connection_limit to disk and connections. The values were unchanged at 768 GB RAM, 4 TB disk and 500 connections.
Heroku renamed the included-spec fields for Postgres Standard-10 from disk_size and connection_limit to disk and connections. The values were unchanged at 1 TB RAM, 8 TB disk and 500 connections.
Heroku renamed the included-spec fields for Postgres Shield-8 from disk_size and connection_limit to disk and connections. The values were unchanged at 488 GB RAM, 3 TB disk and 500 connections.
Heroku added a 'Private Space required' feature entry to Postgres Shield-8, alongside the existing 'HIPAA and PCI compliant' entry.
