Gitpod Classic PAYG sunset on October 15th

We're reaching out to all Gitpod Classic pay-as-you-go (PAYG) users with an important reminder that Gitpod Classic will sunset on October 15th.

As we announced in our Ona launch blog post, Gitpod is evolving into Ona, the mission control for software engineering agents. For our long-time PAYG users, all of the features you love and rely on with Gitpod will remain from one-click reproducible development environments to Ona Cloud, a simple hosted compute offering.

For Enterprise: The following timelines do not apply. Enterprise customers will have received information from their account manager on a custom migration timeline.

How to know if you’re using Gitpod Classic

If your dashboard is accessible at gitpod.io you’re using Gitpod Classic.

You will also see "Gitpod Classic" displayed in the interface.

Why are we making this change?

With Ona you'll gain access to more powerful infrastructure, industry-standard specifications for defining your development environment, and integrated AI agents that weren't possible with the previous version of Gitpod.

The new architecture comes with three powerful components:

Ona Environments - One-click, fully configured development environments based on Dev Container. Work from any device, and seamlessly transition between a conversational agent UI, VS Code Web, and your desktop IDE.

Ona Agents - Your personal team of professional software engineering agents working in sandboxed environments, helping you scope, explore, produce, and review code changes.

Ona Guardrails - Enterprise-grade security with audit trails, organizational policies, and complete control over agent capabilities. Upgrade to Enterprise for maximum control.

The new architecture and experience is vastly improved, and we think you're going to love the enhanced capabilities and performance it brings to your development workflow.

Migrating from .gitpod.yml to Dev Container

The main user-facing difference for PAYG users between Gitpod Classic and Ona is the configuration format of the dev environments.

The .gitpod.yml format is now deprecated and has been replaced by:

• devcontainer.json - The open-source specification from Microsoft for defining development environments
• automations.yml - For defining automated tasks and workflows

The Dev Container specification is more fully-featured than .gitpod.yml, offering greater flexibility and industry-standard compatibility.

To help you migrate, we've created a migration command that will give you a head start. To execute the command, start an environment in Ona and run the command.

gitpod env migrate

For detailed documentation on the new configuration formats, please see:

• Dev Container configuration guide
• Automations setup guide

We're also developing an automated migration agent that will handle your configuration and migration seamlessly, making the transition easier.

Pricing tiers beyond October 15th

Following the migration, Ona will offer three tiers:

1. Free is ideal for individuals getting started, offering up to 3 parallel environments and machine sizes up to 4 vCPUs, 16GB RAM, and 80GB disk.
2. Core starts at $20/month and is for teams who want hosted compute plus support for up to 100 team members at no extra cots and unlimited parallel environments.
3. Enterprise provides maximum security, compliance, and control including a self-hosted private VPC deployment, SSO, audit trails, and premium support.

Launch offer: Try Ona Agents for free and get $100 in free credits when you upgrade to Core in September.

Running environments in Ona is considerably cheaper compared to Gitpod Classic

Ona environments cost up to 66% less than Gitpod Classic on comparable machines, with far greater flexibility in choosing sizes.

For more details see the pricing page.

FAQ

Will Ona offer hosted compute so I don’t need to self-host infrastructure? Yes, by default your environment will run in Ona Cloud, our secure infrastructure and you’ll be able to spin up one click, fully prepared environments with up to 32 cores, 128G RAM, 200G disk. Enterprise customers can host all development environments and AI agents within their own cloud infrastructure.

Can I self-host Ona? Yes, on the Enterprise plan. Enterprise customers can deploy Ona entirely within their own VPC, maintaining complete control over their networking, source code, secrets, and data. The self-hosted version includes all features including Ona Agents. Free and Core tiers are only available on our hosted infrastructure.

What happens if I don't migrate by October 15th? Pay-as-you-go users will not be able to login or start new environments after October 15th. We recommend that you push any code changes to GitHub before October 15th.

Will my data be automatically migrated? No. Secrets, projects, configurations, and workspace data must be manually migrated. The gitpod env migrate command helps convert your configuration format, but you'll need to manually transfer any secrets, environment variables, and other data to the new platform.

Can I download my workspace content? Yes, you must download all your workspace content by October 15th if you want to keep local copies. If you have pushed to Git already, there should be no reason to download workspace content.

What happens to my existing workspace URLs and integrations? The "Open in Gitpod" buttons on repositories will continue to work and will be redirected to app.ona.com. Browser extensions are configured to point to the new domain. Specific workspace URLs will change, so update any bookmarks or documentation accordingly.

Can I disable Ona Agents if I just want development environments? Yes. Ona Agents are an optional feature. You can use Ona purely for development environments if preferred.

Can I still use JetBrains IDEs with Ona? Yes. Ona supports VS Code, JetBrains IDEs, Cursor, Windsurf and many more.

Will my login credentials remain the same? No, you will need to sign up to a new account as you'll log in at app.ona.com instead of gitpod.io.