DigitalOcean Startups: Cloud Credits and Support for Early-Stage Companies
DigitalOcean Startups gives eligible new companies a defined period of cloud credits and startup support, with the award amount set during onboarding.
DigitalOcean Startups is the company’s current startup support program for new businesses that need cloud infrastructure. It replaces the former DigitalOcean Hatch Program, which DigitalOcean says is no longer active. That distinction matters: old articles and startup directories may still call the opportunity “Hatch,” repeat an older credit ceiling, or send applicants to a retired application path. The current source of truth is the DigitalOcean Startups page linked above.
The program is open on an ongoing basis rather than tied to a published annual closing date. That makes it useful for a team preparing a real deployment, but it does not mean every applicant is accepted or that the same award is available to everyone. DigitalOcean reviews applications, sets the credit award for an approved startup, and describes the amount in the onboarding email. A company should therefore plan its infrastructure budget as though it will eventually pay its own bill, with the credits treated as temporary support rather than permanent financing.
At a glance
| Category | Current details |
|---|---|
| Program | DigitalOcean Startups |
| Provider | DigitalOcean |
| Opportunity type | Cloud credits and startup support |
| Credit term | 12 months |
| Credit amount | Set in the onboarding email; the public page says the amount varies |
| Typical monthly limit | Participants generally have a $10,000 monthly limit; excess use can be charged |
| Deadline | Ongoing; the official page does not publish a fixed closing date |
| Geographic scope | Global, subject to DigitalOcean’s application and account requirements |
| Priority | AI-native startups are prioritized |
| Company stage screen | Applicants must have raised $10 million or less |
| Account requirement | A new registered DigitalOcean team account with a company email and valid credit card |
| Official program page | https://www.digitalocean.com/startups |
What the current program provides
The central benefit is a period of DigitalOcean credits that lasts 12 months. Those credits can help an approved company run qualifying DigitalOcean infrastructure while it builds, launches, and grows. The program page also describes access to startup-oriented support, including expert one-on-ones, a startup community, and Standard-tier paid support for a limited period. Accepted companies receive program perks through the welcome materials supplied after acceptance.
The credit award is not a universal public prize. DigitalOcean says the amount varies and is set out in the onboarding email. The page also says that participants generally have a $10,000 monthly limit, with charges applying to use above that amount in a month. This is a budgeting boundary, not a promise that every company receives $10,000 per month or $120,000 in total credits. Applicants should wait for their own award details and confirm which services and limits apply to their account before moving production workloads.
Credits are intended for qualifying DigitalOcean services. The current program information lists important exclusions, including GPU Droplets, NVIDIA H100 GPU Kubernetes, Bare Metal GPUs, Dedicated Inference, Serverless Inference and third-party AI models hosted outside DigitalOcean infrastructure, Paperspace Machines, Cloudways services, and charges passed through to outside providers. Core credits do not automatically cover GPU usage. DigitalOcean says GPU credits are a separate benefit available only to selected customers after review of their GPU needs, so an AI startup should not assume that its model-training or inference bill will be covered by the core award.
The credits are also not cash, transferable property, or a substitute for financial planning. They cannot be moved to another company, and unused credits can be forfeited. The program does not grant extensions. A responsible applicant should map the first twelve months of infrastructure usage, identify excluded services, and keep a reserve for ordinary billing after the program term ends.
Who the program is for
DigitalOcean says it prioritizes AI-native startups. That does not make an AI label a requirement for every startup, but it does signal where the program is focusing its review and product support. A company building an AI application, model-enabled workflow, developer tool, inference product, or data system should explain exactly what it is building and why DigitalOcean infrastructure is relevant. A non-AI software startup can still review the criteria and apply if it fits the other requirements, but it should not describe itself as AI-native unless that is genuinely central to the product.
The company must have raised $10 million or less. This is a qualification screen, not a suggestion to omit financing information. Give the application a clear, accurate account of the company’s funding history and current stage. If the company has raised more than that amount, it should not present itself as eligible merely because its current cloud budget is small.
The page specifically excludes service-based startups, including consulting services, web or app development services, and marketing agencies. A product company that sells software to those customers is different from an agency that primarily sells client work; the application should make that distinction clear. The strongest fit is a company with a repeatable digital product or service of its own, a real deployment plan, and a clear reason to use DigitalOcean resources.
DigitalOcean also says this program is for new startups that have not used prior DigitalOcean credits. Previous participation is therefore important to disclose. Do not create duplicate accounts or try to reframe an old credit award as a first application. Account history and inconsistent company information can create verification problems even when the product itself is a good fit.
Required company and account setup
Before applying, prepare a working company website. It should explain what the company does, identify the product clearly, and be reachable by the reviewer. A placeholder page, broken domain, or site that describes a different business is likely to create avoidable questions.
The applicant also needs an email address associated with the company’s website domain. DigitalOcean requires a matching corporate email address for the application and says that the DigitalOcean team account must use a business or company email rather than a personal address. This is an operational requirement as well as a credibility check. Set up the account under the company’s domain, make sure the relevant founder or technical owner can access it, and avoid making a contractor’s personal inbox the permanent owner of the cloud account.
DigitalOcean says applicants must create a new registered team account before applying. The setup requires the corporate email associated with the company domain and a valid credit card. The card does not turn the credits into a cash award; it provides a billing method for charges that are outside the credit scope or above the applicable monthly limit. Confirm that the billing owner understands this before submitting.
Use consistent details across the website, application, team account, and any partner referral. The legal or operating name, domain, product description, founder contact, and funding stage should agree. If the company is still changing its public name, resolve that mismatch first. A short, accurate company description is more useful than a polished pitch that conflicts with the website or account record.
How to apply
Read the current DigitalOcean Startups page and confirm that the company fits the product, funding, prior-credit, and service-based-company criteria. The page is the current application reference because the old Hatch program is discontinued.
Publish or repair the company website. Check it from an unauthenticated browser, make sure the product is understandable, and use the same company domain for the applicant email.
Create a new DigitalOcean team account for the startup. Register it with the company email and add the valid credit card required by the account setup. Keep the account under company control and assign an owner who will monitor billing and usage.
Open the application linked from the official Startups page. If the company is not backed by a listed venture capital firm, accelerator, or incubator, DigitalOcean says an applicant can select “Other” for the affiliated partner organization rather than inventing an affiliation. If a program manager or approved partner is involved, use the accurate relationship and ask that person about the appropriate route.
Describe the product, customers, stage, funding, and infrastructure plan plainly. Explain what will run on DigitalOcean during the first several months: for example, application services, managed databases, object storage, backups, monitoring, or a qualifying AI workload. Separate those services from GPU or third-party services that the core credits exclude.
Submit only after checking the domain, email, team account, funding figure, and prior-credit answer. DigitalOcean’s application review determines acceptance and the award. Submission is not an approval, and the published page does not promise a particular credit amount.
If accepted, read the welcome kit and onboarding email carefully. Record the award amount, term, eligible services, monthly limit, billing contact, and any instructions for partner perks. Put an owner and a monthly review on the company calendar before using the credits.
A practical first-month plan
The first month should establish control, not maximize consumption. Start by recording the company’s current monthly infrastructure cost and the workloads it expects to move or create. Tag resources by environment and owner. Set billing alerts below the monthly limit so the team has time to adjust before an overage becomes a charge.
Next, separate development, staging, and production where the product needs that distinction. Use least-privilege access, backups, and a documented recovery procedure. Add monitoring for the metrics that matter to the product: request failures, latency, storage growth, database health, and queue or job backlog. These steps make the credits produce operational value instead of merely postponing a bill.
For an AI-native company, write down which parts of the system use eligible DigitalOcean services and which require a separate budget. Model inference, GPU compute, and third-party APIs can have different treatment from ordinary compute, storage, databases, and networking. Ask DigitalOcean’s startup contact if a service is unclear before deploying it at scale. A prototype that quietly relies on excluded services can still generate a charge even when the account has unused core credits.
At the end of the first month, compare actual usage with the plan. Remove idle resources, set a review cadence, and forecast the post-program bill. The goal is not to spend the award; it is to build a system the company can continue operating after the twelve-month term.
Common mistakes
The first mistake is using the old Hatch name and URL as if the program were unchanged. The Hatch terms page now says that Hatch is no longer active and has been replaced by DigitalOcean Startups. Use the current program name in the application and direct readers to the Startups page.
The second is treating a headline credit figure from an old directory as a guaranteed award. DigitalOcean now says the amount varies and is set in the onboarding email. Do not promise investors, founders, or customers a fixed total that the official page does not promise.
The third is applying with a personal email or an unregistered team account. Create the company team account first, use the matching domain email, and keep a valid card on file for non-covered or excess usage.
The fourth is ignoring the service-based exclusion. A consulting agency may have cloud costs, but that does not make it an eligible product startup under this program. Explain the company’s own product and recurring software offering if that is the basis for eligibility.
The fifth is budgeting for GPU workloads without checking the separate GPU rules. Core credits do not automatically pay for GPU Droplets or the other listed exclusions. Ask about a separate GPU award if the company’s infrastructure plan depends on those products.
The sixth is waiting for a fixed deadline that does not exist. The opportunity is ongoing, so choose an internal submission date based on account readiness, a defined infrastructure plan, and the ability to respond to review questions. Ongoing availability is not a reason to submit an incomplete application.
Frequently asked questions
Is DigitalOcean Hatch still active?
No. DigitalOcean’s Hatch terms page says the Hatch Program is no longer active and has been replaced by DigitalOcean Startups. This page retains the existing file identity for continuity, but the opportunity described here is the current Startups program.
How long do the credits last?
DigitalOcean describes 12 months of credits. The award amount and onboarding details are supplied to an approved startup. The program does not grant extensions, so plan to transition paid workloads before the term ends.
Is the monthly limit the same as the credit award?
No. The public page says the credit amount varies and that participants generally have a $10,000 monthly limit. The limit is a billing boundary for monthly usage, not a promise that every applicant receives $10,000 per month or a particular total award.
Can a company without a VC or accelerator apply?
Yes. DigitalOcean says a company that is not backed by a listed partner can fill out the application and select “Other” when asked for an affiliated partner organization. That does not remove the other eligibility and account requirements.
Does every accepted startup receive GPU credits?
No. GPU credits are described as a separate benefit for selected customers after review of GPU needs and infrastructure requirements. Core credits do not automatically cover the excluded GPU products.
What should a team do if it goes over the monthly limit?
Assume the excess usage can be charged. Set alerts, review the service exclusions, and keep a payment method and budget for overages. Contact DigitalOcean if a product’s coverage is unclear before incurring a large bill.
Final application checklist
Before submitting, confirm that the company has a working website, a matching company-domain email, and a new registered DigitalOcean team account with a valid credit card. Verify that the business is a product startup rather than an excluded service-based company, has raised no more than $10 million, and has not used prior DigitalOcean startup credits. Prepare a concise explanation of the product and a qualifying infrastructure plan. If the company is accepted, use the onboarding email and welcome kit as the binding source for the award amount, term details, and available perks.
Applications are ongoing. Apply through the current DigitalOcean Startups page when those materials are ready: DigitalOcean Startups.