Dec 1, live webinar: Agents in production, live: who gives the agent production access?

AWS Activate Credits in 2026: How to Get Up to $200,000 and Spend Them on Kubernetes in Your Own Account

How AWS Activate credits work in 2026: the Founders and Portfolio tiers, who is eligible, how to apply, what the credits can and cannot pay for, and how to spend them on Kubernetes in your own AWS account so the infrastructure outlives the credits.

Romaric Philogene
CEO & Co-founder
NOV 22, 2026 · 18 MIN
AWS Activate Credits in 2026: How to Get Up to $200,000 and Spend Them on Kubernetes in Your Own Account

Key points:

  • How much: AWS Activate Founders starts at $1,000 and goes up to $5,000 for self-funded startups. Activate Portfolio goes up to $200,000 for startups backed by an Activate Provider (accelerator, angel investor or VC firm). AWS Credits for AI Startups is invite-only and starts above $200,000 (AWS Activate credits).
  • Who qualifies: pre-Series B, founded in the last 10 years, an AWS account on a Paid Tier Plan, and either new to Activate credits or asking for more than you received before. Free-plan AWS accounts are not eligible.
  • How to apply: create an AWS Builder ID, pick the tier, describe the startup, link the AWS account. AWS says to expect an answer within 5 to 10 business days. Portfolio needs the Organization ID your provider gives you, and each Org ID works once.
  • What they cannot pay for: AWS Marketplace (except third-party models on Amazon Bedrock), upfront fees for Savings Plans and Reserved Instances, AWS Support beyond eligible plans, Professional Services, training, certification, domain registration, crypto mining, and any bill from before the credits landed. They expire, and AWS will not extend them.
  • How to spend them well: run production in your own AWS account (EKS, EC2, RDS, S3), put Spot capacity under non-production, set a budget alert from day one, and build infrastructure you can keep paying for after the credits end. A PaaS that runs on its own infrastructure cannot consume your Activate credits.
  • Where Qovery fits: Qovery, the Agentic DevOps platform, deploys your apps on Kubernetes inside your own AWS account, so the credits pay for the cluster, nodes and databases it runs, and the whole setup stays yours when they expire. The Free plan covers 3 users, unlimited AI agents and one cluster of your own with no credit card.

Qovery · Agentic DevOps platform
A control plane for platform teams and their coding agents
Learn more

Most founders I talk to treat AWS credits as free money and spend them the way you spend free money: fast, on whatever is easiest, with no plan for month 13. Then the credits expire, the bill shows up, and the stack they built is either too expensive to keep or stuck on a platform that never used the credits in the first place.

Activate is one of the best deals in cloud for an early-stage company. This guide covers the boring parts (eligibility, the application, the fine print) and the part that matters more: spending the credits on infrastructure you will still want once they are gone. We have a similar guide for Azure startup credits if Microsoft is your cloud.

What are AWS Activate credits, and how much can a startup get in 2026?

AWS Activate credits are promotional credits that AWS applies to your AWS bill. In November 2026 there are three tiers: Activate Founders (up to $5,000, starting at $1,000), Activate Portfolio (up to $200,000), and AWS Credits for AI Startups (invite-only, $200,000 and more). All amounts are in USD and subject to the AWS Promotional Credit Terms (AWS Activate credits).

Here is what AWS publishes for each tier today:

TierWho it is forCreditsHow you get in
Activate FoundersBootstrapped or self-funded startupsStarts at $1,000; "select participants may qualify for additional credits up to $5,000"Apply directly
Activate PortfolioPre-Series B startups backed by an Activate ProviderUp to $200,000Apply with the Organization ID (Org ID) from your accelerator, angel investor or VC firm
AWS Credits for AI StartupsStartups that have grown beyond Activate Portfolio$200,000+, sized to the workload; AWS says offers have ranged "from thousands into the millions"Invite-only, through your AWS account manager
AWS Free Tier (any new account)Anyone opening an AWS account$100 at sign-up plus up to $100 more you can earn, so up to $200 over 6 monthsAutomatic on a new account

Sources: AWS Activate credits, AWS Free Tier.

Two things trip people up. The amounts are ceilings, and your Activate Provider decides which offer it can extend to you. AWS's own FAQ gives the example of a provider offering $5,000, $25,000 and $100,000 packages to different companies (AWS Startups FAQ). And the Free Tier is separate from Activate: a free-plan account closes after 6 months or when its credits run out, and AWS says free account plans "are not eligible for Activate promotional credits" (AWS Startups FAQ). Upgrade the account to the Paid Tier Plan before you apply.

You can also climb tiers. If you received $10,000 and later qualify for $100,000 through a provider, AWS tops you up by the difference, $90,000, as long as you still meet the criteria and have a valid Org ID (AWS Startups FAQ).

Who is eligible for AWS Activate credits?

A startup is eligible for AWS Activate credits if it is pre-Series B, was founded in the last 10 years, runs an AWS account on a Paid Tier Plan, and is either new to Activate credits or requesting more than it received before. Portfolio also requires an Org ID from an Activate Provider (AWS Activate credits).

The criteria are short, but the application review is strict. AWS publishes the status messages its application system can return, and the rejection reasons read like a checklist of what to get right before you click submit (AWS Startups FAQ):

  • Company age: "Startups must be less than 10 years old to be eligible for Activate Credits."
  • Funding stage: "Startups at Series B or later are not eligible for the Activate Credit program."
  • Funding recency: "Your most recent funding round must be within 12 months of your application to be eligible for Activate Credits."
  • Email domain: "Applications require that the email used on your AWS account matches the domain used in your application. Free email providers are not accepted for business applications."
  • Previous credits: an application fails if "you previously received Activate Credits of equal or greater value across all your AWS accounts."
  • Provider confirmation: Portfolio applications fail if the Activate Provider "has not confirmed your affiliation after 30 days", or if the Org ID "is no longer valid or has expired."
  • Account standing: "We can only issue credits to accounts in good standing."
  • Location: some applications are refused "based on the region where your startup is located."

My advice from watching founders go through this: open the AWS account with an address on your company domain, make sure the company name on the application matches what a search engine finds about you, and ask your investor or accelerator for the Org ID before you start the form. Most delays I have seen came from a domain mismatch or a provider that took weeks to confirm.

Who is not eligible: Series B and later companies, companies older than 10 years, and companies that already received the maximum Activate value. Those companies still have options, but they come through migration programs run with AWS Partners, covered further down.

How do you apply for AWS Activate credits, step by step?

You apply in four steps on the AWS Startups site: create an AWS Builder ID, choose your credit tier, provide your startup details, then link your AWS account and submit. AWS says to expect a response within 5 to 10 business days (AWS Activate credits).

  1. Prepare the AWS account. Use the account that will run production, on the Paid Tier Plan, with an email on your company domain. Credits redeem to one account; you can share them across an AWS Organization later (see below).
  2. Create an AWS Builder ID and join AWS Activate on the AWS Startups site. Membership is free and also gives access to the partner offers and resources.
  3. Choose the tier. Self-funded companies apply to Founders. Funded companies apply to Portfolio with the Org ID from their Activate Provider. AWS describes the Org ID as confidential and "not a promotional code", and "an Org ID can only be used one time" (AWS Startups FAQ).
  4. Describe the startup (name, website, funding, founding date) and link the AWS account ID, then submit.
  5. Check the result in the Billing console. Approved credits appear in the AWS Billing and Cost Management console with their expiration date.

If you buy AWS through a reseller with consolidated billing, tell the reseller about the application: AWS can reject an application when it has "not received confirmation from your Reseller" (AWS Startups FAQ).

One honest note on timing. The credits only apply to charges "incurred during or following the billing cycle in which you receive the credits", and they "cannot be used to offset or cover historical AWS bills" (AWS Startups FAQ). Apply before you start a big build or migration, not after the first large invoice.

What can AWS Activate credits pay for, and what can't they?

AWS Activate credits pay for AWS "Eligible Services": compute, storage, databases, networking, analytics, machine learning, and third-party models on Amazon Bedrock. They cannot pay for AWS Marketplace purchases (Bedrock third-party models excepted), upfront fees on Savings Plans and Reserved Instances, ineligible AWS Support, Professional Services, training, certification, Route 53 domain registration, or crypto mining (AWS Startups FAQ, AWS Promotional Credit Terms).

SpendCovered by Activate credits?Notes
EC2, EKS, Fargate, LambdaYesCompute is where most of the credits go
RDS, Aurora, DynamoDB, ElastiCacheYesManaged databases count as eligible services
S3, EBS, data transfer, NAT gateways, load balancersYesWatch NAT and egress, they add up quietly
Amazon Bedrock, including third-party models (Anthropic, Cohere, AI21 Labs...)YesThe one Marketplace exception AWS calls out
Savings Plans and Reserved InstancesUsage yes, upfront fees no"Upfront fees for Reserved Instances and Savings Plans are not covered"
AWS Marketplace software (other than Bedrock models)NoIncludes SaaS you buy through Marketplace
AWS Professional Services, Managed Services, Training, CertificationNoPay these in cash
Route 53 domain registration or transferNoDNS queries are fine, registering the domain is not
Bills from before the credits were issuedNoCredits only apply going forward

Sources: AWS Startups FAQ, AWS Promotional Credit Terms.

The Marketplace rule has a consequence many teams miss. A PaaS that runs on its own infrastructure bills you directly, and even when it sells through AWS Marketplace, Activate credits do not cover the purchase. Railway is candid about this: its own guide says "Railway is not a BYOC platform. We run a managed PaaS on infrastructure we own" (Railway). If your credits are meant to pay for production, production has to run in your AWS account. I compared the options in Railway vs Render vs your own cloud account.

Three more rules worth knowing:

  • Expiry is final. Credits have an expiration date visible in the Billing console, and "the AWS Activate team is unable to extend the expiration date of AWS Activate Credits, even if there are remaining credits left unused" (AWS Startups FAQ).
  • Sharing across accounts is a switch. With credit sharing enabled in the Billing console, the parent account and its child accounts in your AWS Organization can use the credits (AWS credit sharing docs). That is how you keep separate production and staging accounts without splitting the credits.
  • No resale, one account per code. Each credit code "can only be redeemed once and only on one AWS account", and credits cannot be sold or transferred outside authorized sharing within an AWS Organization (AWS Promotional Credit Terms).

How do AWS credits compare with Google Cloud and Azure startup credits?

Google Cloud offers the largest headline number (up to $350,000 for AI startups over two years), AWS Activate Portfolio goes up to $200,000, and Microsoft for Startups goes up to $150,000. The bigger differences are in who qualifies and how the credits unlock, so read the terms before you look at the ceiling.

ProgramHeadline creditsWho qualifiesHow credits unlock
AWS Activate Founders$1,000, up to $5,000Self-funded, pre-Series B, under 10 years oldGranted on approval
AWS Activate PortfolioUp to $200,000Pre-Series B with an Activate Provider Org IDGranted on approval, top-ups possible
Google for Startups Cloud ProgramUp to $350,000 for AI startups, up to $200,000 for other funded startupsStart tier for startups founded in the past 2 years with an MVP; funded tiers need verifiable Pre-Seed to Series A fundingAI: year 1 up to $250,000, year 2 covers 20% up to $100,000 more
Microsoft for StartupsUp to $150,000Early-stage startups building software productsUp to $5,000 through business verification, more unlocked progressively with sustained Azure usage

Sources: AWS Activate credits, Google for Startups Cloud Program, Microsoft for Startups.

My view: apply where you plan to run, not where the number is biggest. Rebuilding a stack to chase a second credit package costs more engineering time than most credit packages are worth. If your team already knows AWS, Activate is the right program, and the same Kubernetes setup can run on Google Cloud or Azure later if you keep it portable.

Spend your AWS credits on infrastructure you keep.
Qovery deploys your apps on Kubernetes in your own AWS account, so Activate credits pay for the compute and the setup stays yours when they run out. Free plan, no credit card.

How do you spend AWS credits on Kubernetes in your own account without wasting them?

Spend AWS credits on infrastructure you would keep paying for: an EKS cluster in your own account, managed databases on RDS, Spot capacity for non-production, and budget alerts from day one. Credits are a runway extension, so build the setup that still makes sense the month after they expire.

Here is the setup I recommend to most funded startups, with the costs you should know.

One EKS cluster per environment tier, in your own account. The EKS control plane costs $0.10 per cluster per hour on standard support, about $73 a month, and $0.60 per hour once a Kubernetes version falls into extended support (Amazon EKS pricing). That last number is a good reason to keep upgrading your clusters: a forgotten old version multiplies the control-plane fee by six.

Managed databases, not databases in pods. RDS or Aurora handle backups, point-in-time recovery and failover. The credits cover them, and when the credits end you still have a database you did not have to babysit.

Spot for everything that can be interrupted. EC2 Spot instances are up to 90% cheaper than On-Demand (AWS Spot pricing). Preview environments, CI workers and staging rarely need On-Demand capacity. Karpenter can mix Spot and On-Demand nodes on EKS for you.

Stop non-production at night. A work week is about 40 of the 168 hours in a week. Environments that only run during working hours burn roughly a quarter of the compute hours of always-on ones.

Watch the quiet line items. NAT gateways cost $0.045 per hour plus $0.045 per GB processed (AWS VPC pricing), and they run whether anyone uses them or not. Orphaned load balancers, EBS volumes and snapshots are the other classic leaks. Credits hide this waste until the day they expire.

Do not prepay with credits. Upfront fees for Savings Plans and Reserved Instances are not covered. If you want commitment discounts, choose no-upfront options so the usage portion is billed in a way the credits can offset, and only commit once your baseline is stable. Compute Savings Plans go up to 66% off On-Demand (AWS Savings Plans).

Set a budget the day the credits land. AWS itself recommends setting up a budget with alerts in the Billing console (AWS Budgets). Alert on gross usage as well as on what you pay, so you see the real burn rate behind the credits.

Where you runDo Activate credits pay for the compute?What you keep when credits expireOps work
DIY EKS with Terraform and Argo CD in your AWS accountYesEverything: account, cluster, dataHigh, usually a platform engineer
Qovery on EKS in your AWS accountYes, for the cluster, nodes, databases and load balancersEverything: account, cluster, dataLow, Qovery operates deployments and upgrades
Other BYOC platforms (Northflank, Porter) in your AWS accountYesEverything in your accountLow
ECS, App Runner or Lambda directlyYesEverything, but tied to AWS-specific servicesMedium
Managed PaaS on its own infrastructure (Railway, Render, Fly.io, Heroku)NoNothing in your AWS accountVery low

Sources: AWS Startups FAQ, Railway, Northflank BYOC, Porter docs.

What happens when your AWS credits run out?

When your Activate credits run out or expire, AWS bills the same usage at normal rates on your next invoice. Nothing switches off, which is the danger: a stack sized for free money becomes a real cost overnight.

Plan for that month from the start:

  • Know your gross burn. Track what the infrastructure would cost without credits, every month. If that number is not a line in your financial model, it will surprise you.
  • Right-size before the cliff. Two months before expiry, cut idle environments, move non-production to Spot, and commit to Savings Plans on the baseline you know you will keep.
  • Look at migration funding if you are moving workloads. AWS funds migrations through partners rather than direct applications. Qovery's funding calculator estimates what AWS, Google Cloud, Azure or Scaleway could fund for a move, and the page explains that "migration funding is applied for by partners, not by customers", and that Qovery, as a partner, does the application for you. If you are leaving Heroku, I wrote about what AWS credits cover in a Heroku migration.
  • Keep it portable. Containers on Kubernetes, Terraform for cloud resources, and data in managed services you can export. That keeps your next negotiation, with AWS or anyone else, an actual negotiation.

How does Qovery help you spend AWS Activate credits?

Qovery, the Agentic DevOps platform, deploys and operates your applications on Kubernetes inside your own AWS account, so your Activate credits pay for the EKS cluster, EC2 nodes, RDS databases and load balancers it runs. Qovery holds the control plane; your account holds the workloads, the data and the bill, and all of it stays yours when the credits expire.

What you set up, concretely:

  1. Connect your AWS account. Qovery creates and manages an EKS cluster in it, with Karpenter for node scaling and Spot capacity where you allow it. If you already run a cluster, you connect it instead by installing the Qovery Operator with Helm; Qovery never stores your kubeconfig (BYOK docs).
  2. Connect your Git repositories. Qovery builds the container images, pushes them to a registry in your account and deploys them with git-push deployments.
  3. Add databases as managed AWS services such as RDS through Blueprints, and secrets through your secrets manager.
  4. Turn on preview environments per pull request and auto-stop for non-production, so credits go to production-like testing instead of idle staging.

To start, the Free plan gives you 3 users plus unlimited AI agents, one cluster of your own and 1,000 deployment minutes a month, with no credit card. You can try the workflow on your laptop first with qovery demo up, which creates a local k3s cluster in Docker (quickstart). Paid plans add a cluster managed by Qovery, more users and support.

Qovery has been an AWS ISV Accelerate partner since 2024 and is sold on AWS Marketplace, which is also why it can apply for AWS migration funding on your behalf through the funding calculator.

What Qovery does not do: it is not an AWS Activate Provider, so it does not hand out Activate credits or Org IDs, and eligibility is always AWS's decision. And if you buy Qovery through AWS Marketplace, Activate credits do not pay the Qovery subscription, because Marketplace is excluded. They pay for the AWS resources Qovery runs in your account, which is most of the bill.

How do I set this up from Claude Code or Cursor?

Install the Qovery Agent Skills once, then ask your coding agent to deploy your app into your AWS account. The agent proposes a plan and you approve each step before anything is created.

Install the skills globally for Claude Code, Cursor, Codex, OpenCode and Gemini CLI, or for one project only:

BASH
curl -fsSL https://skill.qovery.com/install.sh | bash
curl -fsSL https://skill.qovery.com/install.sh | bash -s -- --project

Add the Qovery MCP Server to Claude Code to inspect and operate what is already running (OAuth, read-only by default):

BASH
claude mcp add --transport http qovery https://mcp.qovery.com/mcp --callback-port 4242

Enable write access only if you want the agent to change things. It also has to be turned on in the Qovery Console:

BASH
claude mcp add --transport http qovery "https://mcp.qovery.com/mcp?read_write=true" --callback-port 4242

Then ask: "deploy this app to my AWS account with Qovery, with an RDS PostgreSQL database, preview environments per pull request, and non-production stopped at night." The skills that do the work are qovery-onboard, qovery-deploy, qovery-preview and qovery-optimize. Reference pages: the AI agent quickstart and the Claude Code integration.

Frequently asked questions
How do I get AWS Activate credits?

Create an AWS Builder ID on the AWS Startups site, choose Activate Founders if you are self-funded or Activate Portfolio if an accelerator, angel investor or VC firm gave you an Org ID, fill in your startup details, and link an AWS account on the Paid Tier Plan. AWS says to expect a response within 5 to 10 business days. Use an email on your company domain, because free email providers are refused.

How much are AWS startup credits worth in 2026?

Activate Founders starts at $1,000 and can reach $5,000. Activate Portfolio goes up to $200,000, depending on the package your Activate Provider can offer. AWS Credits for AI Startups is invite-only and starts above $200,000 for startups that have outgrown Portfolio.

Who is eligible for AWS Activate credits?

Startups that are pre-Series B, were founded in the last 10 years, run an AWS account on the Paid Tier Plan, and have not already received the same or a larger amount of Activate credits. AWS also checks that your most recent funding round is within 12 months and that your company email domain matches the application.

Do AWS Activate credits expire?

Yes. Each grant has an expiration date shown in the AWS Billing and Cost Management console, and AWS says it cannot extend it even if credits are left unused. Credits also only apply to bills from the month they are issued onward.

Can I use AWS Activate credits on Railway, Render or other platforms?

Not on platforms that run your apps on their own infrastructure, because Activate credits only pay for eligible AWS services in your own AWS account, and AWS Marketplace purchases are excluded. They do pay for what a platform like Qovery deploys in your account (EKS, EC2, RDS, load balancers), though not for the Qovery subscription itself if you buy it through Marketplace.

Can Qovery help me use AWS credits on Kubernetes?

Yes. Qovery deploys your apps on an EKS cluster in your own AWS account, or on a cluster you already run, so the credits pay for the infrastructure while Qovery handles deployments, preview environments and cluster upgrades. Qovery is not an Activate Provider, so applying for the credits stays between you, your investor and AWS.

Romaric Philogene
About the author
Romaric Philogene

Romaric founded Qovery to make Kubernetes accessible to every engineering team. He writes about platform strategy, developer experience, and the future of cloud infrastructure.

Next step

Spend your AWS credits on infrastructure you keep.

Qovery deploys your apps on Kubernetes in your own AWS account, so Activate credits pay for the compute and the setup stays yours when they run out. Free plan, no credit card.