Softwr

Developer Tools · head to head

Ona (formerly Gitpod) vs pytest

Ona (formerly Gitpod) logo

Ona (formerly Gitpod)

Developer Tools

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

From
Free
Free plan
Yes
pytest logo

pytest

Testing

Python testing framework maintained by an independent core team funded partly through Tidelift

From
Free
Free plan
Yes

The short version

  • pytest is free; Ona (formerly Gitpod) starts at $20/mo.
  • Only Ona (formerly Gitpod) lists ephemeral environments; only pytest lists assert-based test syntax.
  • Prices and features on this page were last checked on 20 November 2026.

How do Ona (formerly Gitpod) and pytest differ?

Ona (formerly Gitpod) and pytest differ on pricing model, platforms and category (Developer Tools against Testing). Only the attributes on which Ona (formerly Gitpod) and pytest actually diverge.

Attributes where Ona (formerly Gitpod) and pytest differ
AttributeOna (formerly Gitpod)pytest
Pricing modelPer month by compute unitOpen source, no licence fee
PlatformsWeb, Linux, macOS, Windows, AWSLinux, macOS, Windows
CategoryDeveloper ToolsTesting

Identical on both: starting price (Free), free tier (Yes).

Not yet recorded: founded for Ona (formerly Gitpod).

Which features does each one have?

They share no listed features; 6 appear only for Ona (formerly Gitpod) and 6 only for pytest. 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 pytest

  • Assert-based test syntax
  • Fixture system
  • Parametrised testing
  • Plugin ecosystem
  • Detailed assertion introspection
  • Test discovery

What is each one used 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 pytest
  • Running several coding agents in parallel against real databases and services instead of on a laptopnot pytest
  • Keeping source code off contractor and offshore laptops by moving the whole environment into a controlled accountnot pytest
  • Reproducing a hard-to-configure toolchain for a short-lived project without polluting anyone machinenot pytest

pytest

  • A Python team moving off the standard library's unittest module for a less verbose, fixture-driven testing stylenot Ona (formerly Gitpod)
  • A project needing parametrised tests to cover many input combinations without duplicating test codenot Ona (formerly Gitpod)
  • A team wanting a large plugin ecosystem for coverage, async testing or Django-specific test supportnot Ona (formerly Gitpod)
  • An organisation wanting a commercial support and maintenance assurance layer via a Tidelift subscription rather than relying purely on community response timesnot Ona (formerly Gitpod)

Where do Ona (formerly Gitpod) and pytest fall 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

pytest

  • There is no corporate owner or dedicated support organisation, so response time on bugs or security issues depends on volunteer maintainer availability unless a Tidelift subscription is purchased separately
  • The plugin ecosystem's quality and maintenance level varies widely between plugins, and a team building a workflow around several plugins takes on the risk of any one of them going unmaintained
  • Its assert-rewriting magic, while convenient, can behave unexpectedly in edge cases involving custom assert helpers, which occasionally confuses developers used to explicit assertion methods
  • Large test suites with many fixtures can develop hard-to-trace fixture dependency chains, since fixtures can depend on other fixtures in ways that are not always obvious from a single test file
  • Being free and volunteer-maintained, roadmap direction is set by contributor consensus rather than a company with commercial incentive to prioritise enterprise-requested features quickly

How much do Ona (formerly Gitpod) and pytest cost?

Ona (formerly Gitpod) has a free plan, with paid plans from $20/mo; pytest is free to use. Plan by plan below, from each vendor's own pricing page.

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/mo
    • 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
  • EnterpriseOn request
    • Single-tenant deployment in your own AWS or GCP account
    • SAML and OIDC single sign-on
    • Dedicated account management and forward deployed engineers

pytest

Free
  • pytestFree
    • Full functionality, no usage limits
    • Community support via GitHub
    • Optional Tidelift subscription for a commercial support and licence assurance layer

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.
  • You also want agent sessions.

Choose pytest if

  • You need assert-based test syntax.
  • You want to start without paying.
  • You work on Linux, macOS, Windows.
  • You also want fixture system.

Questions people ask

Is Ona (formerly Gitpod) or pytest better?
Neither clearly leads. Ona (formerly Gitpod) starts at Free and pytest at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Ona (formerly Gitpod) or pytest?
Ona (formerly Gitpod) starts at Free and pytest at Free.
Does Ona (formerly Gitpod) or pytest run on more platforms?
Ona (formerly Gitpod) runs on Web, Linux, macOS, Windows, AWS. pytest runs on Linux, macOS, Windows.
Can I use Ona (formerly Gitpod) for free?
Both have a free tier, so you can try either at no cost before committing.
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 pytest is typically brought in for.
What can Ona (formerly Gitpod) do that pytest cannot?
Ona (formerly Gitpod) covers Ephemeral environments, Agent sessions, Bring your own cloud, Devcontainer standard. pytest covers Assert-based test syntax, Fixture system, Parametrised testing, Plugin ecosystem.

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.

pytest: Is pytest owned by a company?

No, it is maintained by the pytest-dev volunteer community with no single corporate parent; some maintainers receive partial funding through Tidelift subscriptions.

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.

pytest: Is there a paid version?

No, pytest itself is free and open source; buyers can optionally pay for a Tidelift subscription for commercial assurance and support.

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.

pytest: Does it replace the standard library unittest module?

It does not replace unittest at the language level, but it is now the de facto standard choice for most Python projects over unittest's more verbose syntax.

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.

Share

Related pages

Other head to heads