What happens when my startup's free cloud credits run out, and how do I prepare?

When your startup's cloud credits run out, the provider bills your card at list price for everything still running. Here's how to estimate that bill and prepare, whether you stay, optimize or move to a fixed cost.

When your startup's cloud credits run out or expire, the provider charges the card on file, at list price, for everything still running. Inventory your resources, measure real usage and decide early: stay, optimize or switch to a fixed cost, like Dongee Cloud from 17 USD/month or Dongee Live, a platform for publishing static and Node apps.

This guide covers what happens on the day the credits end, how to estimate the bill that follows and how to migrate without downtime.

Updated November 22, 2026 · Dongee Team

How do cloud credits for startups work?

Cloud credits are promotional balance that the big cloud providers (the so-called hyperscalers) give startups so they build on their platform. Startups get them straight from the provider or through accelerators, incubators and funds that partner with those programs.

Each program has its own rules, but almost all of them share a few traits:

  • They expire. The balance has an expiration date. If you don't spend it in time, you lose it, and from that day on you pay.
  • They usually require a card. Many programs ask for a valid payment method when you activate the account. That card gets charged once the balance is gone.
  • They don't cover everything. Programs often exclude certain services, paid support, the marketplace or some regions.
  • They change often. Amounts, terms and requirements change with little notice. Check them on the program's official page before you plan around them.

The credits themselves aren't the problem. The problem is that they get you used to an architecture you have never paid for out of your own pocket.

What exactly happens when they run out or expire?

You won't get a dramatic warning, and nothing shuts down on its own. The bill simply stops coming out of the balance and goes to your card. This is what usually happens:

  • Everything is billed at list price. The program's discounts disappear, and every compute hour costs whatever the public rate says.
  • Managed services keep billing. Managed databases, queues, functions and load balancers bill even when they get almost no traffic.
  • The “invisible” charges show up. Outbound data transfer to the internet, reserved public IPs, object storage, detached volumes and old snapshots are billed separately. While you had credits, almost nobody looked at them.
  • Forgotten resources get expensive. The test environment an intern spun up, a large instance for an experiment or a cluster nobody shut down keep adding up every hour.
  • If you don't pay, they can suspend you. If the card declines the charge, the provider can limit or suspend the account, and that hits your production.

How do you estimate what you'll pay afterwards?

Do it at least 60 days before the credits expire. That gives you room to optimize or migrate.

  1. Take an inventory of resources. List every instance, database, volume, IP, bucket, snapshot and managed service, in every region. Tag each one as production, testing or “no idea what this is.”
  2. Measure 30 days of real usage. In the provider's billing dashboard, review a full month of usage, service by service, without applying the credits.
  3. Set up a budget alert. Give it a low threshold, for example 50% of what you're willing to pay, so it warns you before the first real bill arrives.
  4. Estimate at list price. Multiply your usage by the current public rate, not by the program's discounted rate.
  5. Add transfer and support. Work out your monthly outbound GB and the cost of the support plan you'd need to handle a production incident.

With that number in hand, compare it with a fixed-price alternative. If you want to run the numbers in detail, follow the guide to calculate the price of a custom cloud server.

Example with Dongee prices: an app with its database on a Dongee Cloud Cloud 3 server (2 CPU, 4 GB RAM, 80 GB SSD) costs a fixed 68 USD/month. If you build the same resources on Cloud On Demand, you pay 2 vCPU × 6 USD + 4 GB × 3 USD + 80 GB × 0.3 USD = 12 + 12 + 24 = 48 USD/month. Check each page for what each option includes (for example, the monthly transfer on Cloud plans). Either way you know in advance what you'll pay, and you can pay in COP, USD, EUR, MXN, PEN, CLP or BRL.

Credits or fixed cost from day one?

There's no single answer. It depends on how much you rely on managed services and how much predictability you need. Here's an honest comparison:

OptionStarting costPredictabilityAdvantagesRisks
Hyperscaler credits0 while the balance lastsLow once the balance endsHuge catalog of managed servicesList-price bill, transfer charges and lock-in to proprietary services
Fixed-price cloud (Dongee Cloud)From 17 USD/month (Cloud 1) to 1,088 USD (Cloud 7)High: fixed monthly feeRoot, Docker and Docker Compose, scaling without rebooting, disk backup includedSelf-managed: you run the system; no GPU
Cloud On Demand (per resource)17 USD/month minimumHigh: you pay for the resources you chooseYou size vCPU, RAM and disk to fit; automatic backups includedYou need to know your usage to avoid oversizing
App publishing platform (Dongee Live)Live Free 0 USD, Live Pro 15 USD, Live Team 29 USDHighHTTPS, automatic restart and one MySQL database per app; no servers to manageStatic sites and Node only; no Python, PHP or Docker

For many startups the most sensible combination is the frontend or Node app on Dongee Live, and the backend, workers or database on a cloud server with containers. If you're evaluating the full architecture, see how to set up a scalable cloud server for your startup.

Does your product use several AI models? Dongee AI Router, a single gateway for calling several AI models, works prepaid from 3 USD with no monthly fee. If the balance runs out, requests stop and no debt is created. That's the opposite of a surprise bill.

How do you move out before the bill arrives?

If you decide to migrate, start while you still have credits, so running both environments side by side doesn't cost you anything.

  1. Package your app in containers. With Docker and Docker Compose, your app stops depending on one specific provider. Define each service (app, workers, cache) in a docker-compose.yml file.
  2. Take a snapshot of the current environment. Save a copy of the current state of your servers and volumes before you touch anything.
  3. Migrate the database. Take a full dump, restore it on the new server and check row counts and key queries. Plan a short window for the final sync.
  4. Lower your DNS TTL. One or two days before the switch, lower the TTL on the records you'll change so the change propagates quickly.
  5. Test in parallel. Bring up the new environment, for example on a Dongee Cloud server in Mexico, São Paulo, Santiago, Miami or Dallas, and test it with a subdomain or by editing your hosts file.
  6. Make the switch. Point your DNS to the new server, run the final data sync and watch logs and metrics closely for the first few hours.
  7. Shut down the old resources. After a few stable days, delete the old provider's instances, volumes, reserved IPs, buckets and snapshots. If you don't delete them, they keep billing.

Dongee Cloud gives you assisted migration and 24/7 human support in your language (the platform translates on the fly). Support can review your migration plan with you before you sign up.

Which mistakes cost the most?

  • Not setting budget alerts and only finding out what you spent when the statement arrives.
  • Leaving test environments running or oversized instances “just in case.”
  • Forgetting orphaned snapshots and volumes, which pile up month after month.
  • Locking yourself into proprietary services with no portable equivalent, which makes any migration expensive and slow.
  • Underestimating outbound transfer, especially if you serve video, images or downloads.
  • Waiting until the last month to decide, leaving no time to test in parallel.

If you're still choosing where to host your product, this comparison of business web hosting for startups will help you decide.

Frequently asked questions

Will I be notified before my cloud credits run out?

It depends on the program and the provider. Some send emails and some don't. Don't count on it: set up your own budget alerts and put the balance's expiration date on your calendar.

Can I ask for more credits when they end?

Sometimes there are extra tiers or renewals through accelerators, but the terms change. Check them on the program's official page, and don't build your budget around getting an extension.

How much does a fixed-price server on Dongee Cloud cost?

Dongee Cloud runs from 17 USD/month (Cloud 1: 1 CPU, 1 GB RAM, 25 GB SSD) to 1,088 USD/month (Cloud 7: 10 CPU, 64 GB RAM). Every plan includes disk backup and snapshots, and you can scale CPU, RAM and disk without rebooting.

What do I do with my frontend built with Lovable, Bolt or Cursor?

You can publish it on Dongee Live. It supports static sites and Node apps (Express, Next.js standalone and others) and includes HTTPS and one MySQL database per app. The Live Free plan gives you 1 app and lets you connect your own domain.

Can I pay in my local currency?

Yes. At Dongee you can pay in COP, USD, EUR, MXN, PEN, CLP or BRL on every product. If you need a specific tax document, ask support in writing before you sign up.

Cloud credits give you a good head start, but they aren't a cost plan. Work out today what you'll pay tomorrow and decide based on the numbers. If a fixed cost suits you better, migrate early, with Dongee's 24/7 support on your side.

Comenta lo que quieras

Unete a la charla
Solo ingresa tu email