Softwr

Developer Tools · head to head

Ona (formerly Gitpod) vs OpsLevel

Ona (formerly Gitpod) logo

Ona (formerly Gitpod)

Developer Tools

Cloud development environments repositioned as a control plane for software engineering agents

From
Free
Rated
-
Full reviewWebsite
OpsLevel logo

OpsLevel

Developer Tools

Internal developer portal that scores service ownership and production readiness

From
On request
Rated
-
Full reviewWebsite

The short version

  • Only Ona (formerly Gitpod) has a free tier, so it costs nothing to try first.
  • Each has a real cost: Ona (formerly Gitpod) acquisition risk has already materialised: the company closed a sale to OpenAI on 10 August 2026 and now sits inside the Codex team, so nothing public guarantees pricing, continuity or neutrality between model vendors beyond honouring existing commitments.; OpsLevel opsLevel does not publish prices at all, not even a starting figure, so you cannot size a budget or compare against Backstage's zero licence cost without entering a sales cycle.
  • They diverge on capability: Ona (formerly Gitpod) covers Ephemeral environments, OpsLevel covers Service catalogue.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Ona (formerly Gitpod) and OpsLevel actually diverge.

Attributes where Ona (formerly Gitpod) and OpsLevel differ
AttributeOna (formerly Gitpod)OpsLevel
Starting priceFreeOn request
Pricing modelPer month by compute unitquote
Free tierYesNo
PlatformsWeb, Linux, macOS, Windows, AWS, Google Cloud PlatformWeb

Identical on both: user rating (Not yet rated), category (Developer Tools).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Ona (formerly Gitpod)

  • Ephemeral environments
  • Agent sessions
  • Bring your own cloud
  • Devcontainer standard
  • Compute unit budgeting
  • Enterprise identity

Only in OpsLevel

  • Service catalogue
  • Scorecards and rubric
  • Checks
  • Campaigns
  • Self-service actions
  • Slack and Teams integration
  • Catalogue auto-enrichment
  • Deployment on request

What people use each for

The jobs each tool is most often brought in to do.

Ona (formerly Gitpod)

  • Giving a large engineering team identical, disposable environments so onboarding is a link rather than a two day setupnot OpsLevel
  • Running several coding agents in parallel against real databases and services instead of on a laptopnot OpsLevel
  • Keeping source code off contractor and offshore laptops by moving the whole environment into a controlled accountnot OpsLevel
  • Reproducing a hard-to-configure toolchain for a short-lived project without polluting anyone machinenot OpsLevel

OpsLevel

  • A platform team that needs to prove every production service has a named owner and an on-call rota before an auditnot Ona (formerly Gitpod)
  • Driving a fleet-wide migration such as a runtime upgrade across 400 services with a deadline and visible progressnot Ona (formerly Gitpod)
  • Giving developers a paved road to create a new service from a template without waiting on the platform teamnot Ona (formerly Gitpod)
  • An organisation where an incident took an hour to route because nobody could identify the owning teamnot Ona (formerly Gitpod)

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Ona (formerly Gitpod)

  • Acquisition risk has already materialised: the company closed a sale to OpenAI on 10 August 2026 and now sits inside the Codex team, so nothing public guarantees pricing, continuity or neutrality between model vendors beyond honouring existing commitments.
  • Two disruptive changes of direction inside a year, from development environments to agent orchestration and then from independence to acquisition, mean the product a browser IDE buyer originally chose no longer exists in that form.
  • The Gitpod Classic sunset on 15 October 2025 required manual conversion of configuration, hand-moved secrets, self-rescued workspace data and a brand new account, which is the clearest available precedent for how the vendor handles deprecation.
  • Community self-hosting is finished: the AGPL-3.0 repository is deprecated by its own README, and self-hosted now means a vendor-operated install in your AWS or GCP account, with no Azure, no on-premises and no air-gapped path.
  • Pricing is difficult to model because it runs on a compute unit currency where subscription credits expire at the end of the month, the mapping from units to actual compute is not published on the pricing page, and Enterprise is quotation only.

OpsLevel

  • OpsLevel does not publish prices at all, not even a starting figure, so you cannot size a budget or compare against Backstage's zero licence cost without entering a sales cycle.
  • The Standard plan caps at 50 users, which is below the size at which service ownership becomes a real problem, so most genuine buyers land on Enterprise and its unpublished pricing.
  • Scores are only as honest as the metadata teams maintain; where ownership records go stale the rubric produces confident numbers about a catalogue that no longer reflects reality, and leadership acts on them.
  • It reports on quality rather than producing it, so it can generate friction between platform teams who set the rubric and product teams who see it as a scoreboard imposed on them without extra headcount to fix the findings.
  • As a hosted product it needs read access to source control, cloud accounts and observability tooling, which is a meaningful vendor review in regulated environments; on-premises exists but only on the Enterprise tier.

Pricing, plan by plan

Ona (formerly Gitpod)

Free
  • FreeFree
    • Up to 3 parallel environments
    • Machines up to 4 vCPU, 16 GB memory and 80 GB disk
    • Ona Cloud multi-tenant only
  • Core$20/month
    • From 20 US dollars a month, up to 100 team members
    • Includes 80 to 2,200 recurring compute units a month depending on tier
    • Additional units from 10 US dollars per 40 units
  • Enterprise$undefined/year
    • Single-tenant deployment in your own AWS or GCP account
    • SAML and OIDC single sign-on
    • Dedicated account management and forward deployed engineers

OpsLevel

On request
  • Standard$undefined/year
    • Up to 50 users
    • Unlimited catalogued components
    • Scorecards, campaigns and the global rubric
  • Enterprise$undefined/year
    • Unlimited users
    • Custom integrations
    • Customisable dashboards

Which should you pick?

Choose Ona (formerly Gitpod) if

  • You need ephemeral environments.
  • You want to start without paying.
  • You work on Web, Linux, macOS, Windows, AWS, Google Cloud Platform.
  • You also want agent sessions.
Ona (formerly Gitpod) review

Choose OpsLevel if

  • You need service catalogue.
  • You also want scorecards and rubric.
OpsLevel review

Questions people ask

Is Ona (formerly Gitpod) or OpsLevel better?
Neither clearly leads. Ona (formerly Gitpod) starts at Free and OpsLevel at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Ona (formerly Gitpod) or OpsLevel?
Ona (formerly Gitpod) has a free tier; the other does not. Paid plans start at Free for Ona (formerly Gitpod) and On request for OpsLevel.
Does Ona (formerly Gitpod) or OpsLevel run on more platforms?
Ona (formerly Gitpod) runs on Web, Linux, macOS, Windows, AWS, Google Cloud Platform. OpsLevel runs on Web.
Can I use Ona (formerly Gitpod) for free?
Yes. Ona (formerly Gitpod) has a free tier, so you can try it without paying. OpsLevel starts at On request.
What is Ona (formerly Gitpod) best used for?
Ona (formerly Gitpod) is most often used for giving a large engineering team identical, disposable environments so onboarding is a link rather than a two day setup, running several coding agents in parallel against real databases and services instead of on a laptop, keeping source code off contractor and offshore laptops by moving the whole environment into a controlled account, reproducing a hard-to-configure toolchain for a short-lived project without polluting anyone machine. Of those, giving a large engineering team identical, disposable environments so onboarding is a link rather than a two day setup and running several coding agents in parallel against real databases and services instead of on a laptop are not what OpsLevel is typically brought in for.
What can Ona (formerly Gitpod) do that OpsLevel cannot?
Ona (formerly Gitpod) covers Ephemeral environments, Agent sessions, Bring your own cloud, Devcontainer standard. OpsLevel covers Service catalogue, Scorecards and rubric, Checks, Campaigns.

Answered from the vendors’ own pages

Ona (formerly Gitpod): Is Gitpod still called Gitpod?

No. It rebranded to Ona in September 2025, and gitpod.io now redirects to ona.com. The company was acquired by OpenAI in a deal that closed on 10 August 2026.

OpsLevel: How much does OpsLevel cost?

It does not publish pricing. Billing is per developer using the portal, with volume discounts, and a quote requires a sales conversation.

Ona (formerly Gitpod): Can I still self-host it for free?

No. The AGPL-3.0 self-hosted project is deprecated by its own README. What is offered now is a vendor-operated single-tenant install in your AWS or GCP account on the Enterprise plan.

OpsLevel: How does it compare with Backstage?

Backstage has no licence fee but you staff a team to build and run it. OpsLevel is hosted with checks, campaigns and scorecards out of the box, and you pay per developer instead.

Ona (formerly Gitpod): What happened to Gitpod Classic?

Pay-as-you-go Classic was switched off on 15 October 2025. Migration required converting gitpod.yml to devcontainer.json, moving secrets by hand, downloading workspace data before the cutoff and creating a new account.

OpsLevel: Does it require writing catalogue YAML by hand?

No. It auto-discovers and enriches entries from connected systems, though teams still curate ownership and metadata.

Ona (formerly Gitpod): What does it cost?

Core starts at 20 US dollars a month and includes a monthly allowance of Ona Compute Units, with more from 10 dollars per 40 units. Subscription credits expire monthly. Enterprise is quoted.

OpsLevel: Can it run on premises?

Yes, but only on the Enterprise plan.

Share

Related pages

More on Ona (formerly Gitpod)

More on OpsLevel

Keep looking

Other head to heads