News

Google To Impose Fees for App Engine

Nearly one year after releasing its free cloud-based hosting service for developers of Python-based applications, Google revealed a new fee structure for those making active use of the offering.

While the company will continue to offer basic use of its Google App Engine for free, new usage quotas will take effect on May 25. The news is not a surprise; Google had indicated it planned to offer fee-based services beyond the quotas initially put in place.

The company revealed the new pricing structure Tuesday on the Google App Engine Blog. "You can now set a daily budget for your app that represents the maximum amount you're willing to pay for computing resources each day," wrote Google app engine team member Brett Slatkin.

He added that developers pay only beyond the free thresholds, pro-rated to the nearest penny. Even with the new quotas, developers can run applications serving approximately 5 million page views per month using the free service, he noted.

The new per-day limits are capped at 6.5 hours of CPU time and 1GB of data transfer (in and out of the app). Stored data and e-mail quotas remain unchanged at 1GB. The company published further details on the pricing structure.

The additional fees are as follows:

  • $0.10 per CPU core hour
  • $0.10 per gigabyte bandwidth inbound and $0.12 per gigabyte outbound
  • $0.15 per gigabyte of data stored by an app per month
  • $0.0001 per e-mail recipient for messages sent by an app

The company is targeting the Google App Engine for developers looking to build data-intensive applications. Google offers a development environment and set of APIs. The environment supports dynamic Web serving, queryable persistent storage to support transactions, scaling and load balancing.

About the Author

Jeffrey Schwartz is editor of Redmond magazine and also covers cloud computing for Virtualization Review's Cloud Report. In addition, he writes the Channeling the Cloud column for Redmond Channel Partner. Follow him on Twitter @JeffreySchwartz.

comments powered by Disqus

Featured

  • Hands On with GitHub Copilot App Technical Preview: Turning a Blazor Issue into a PR

    GitHub's brand-new Copilot desktop app, in technical preview, handled a small Blazor issue from planning through pull request creation, but the hands-on test also showed why developers still need to verify agent work in the running app before merging.

  • At Build 2026, Microsoft Sets Up Windows as an OS for AI Agents

    Microsoft's Build 2026 Windows developer announcements point to a broader platform strategy for agentic AI, spanning terminal workflows, local models, app-building skills, Cloud PCs and operating system-level containment.

  • Slammed by Copilot Usage-Based Billing on Day 1, Facing $180 Bill for June

    A journalist using GitHub Copilot Pro details how a broken editorial workflow on day one of usage-based billing led to runaway token consumption, a projected $180 monthly bill, and practical tactics for cutting AI credit burn.

  • AdaBoost.R2 Regression Using C#

    AdaBoost.R2 regression works by building an ensemble of decision trees, training them on reweighted data, and combining their predictions with a weighted median, while also showing how parameter choices affect accuracy and overfitting.

Subscribe on YouTube