Softwr

Developer Tools · head to head

Ona (formerly Gitpod) vs LiquidPlanner

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
LiquidPlanner logo

LiquidPlanner

Project Management

Predictive project management

From
On request
Free plan
No

The short version

  • LiquidPlanner is a predictive project management solution.
  • Ona (formerly Gitpod) has a free plan, then $20/mo; LiquidPlanner starts at $15/mo.
  • Only Ona (formerly Gitpod) lists ephemeral environments; only LiquidPlanner lists predictive scheduling.
  • Where LiquidPlanner falls short: rebranded to Tempo Portfolio Manager; the pricing page shows no published figures, only an early access sign-up.
  • Prices and features on this page were last checked on 13 November 2026.

Where they differ

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

Attributes where Ona (formerly Gitpod) and LiquidPlanner differ
AttributeOna (formerly Gitpod)LiquidPlanner
Starting priceFreeOn request
Pricing modelPer month by compute unitSubscription
Free tierYesNo
PlatformsWeb, Linux, macOS, Windows, AWSWeb
CategoryDeveloper ToolsProject Management

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

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 LiquidPlanner

  • Predictive scheduling
  • Resource management
  • Time tracking
  • Analytics
  • Workload management
  • Jira
  • Salesforce
  • Slack

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

LiquidPlanner

  • Productivitynot Ona (formerly Gitpod)
  • Collaborationnot Ona (formerly Gitpod)
  • Task managementnot Ona (formerly Gitpod)
  • Organizationnot 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

LiquidPlanner

  • Rebranded to Tempo Portfolio Manager; the pricing page shows no published figures, only an early access sign-up

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/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

LiquidPlanner

On request
  • Essentials$15/mo
    • Project management
    • Basic scheduling
  • Professional$25/mo
    • Predictive scheduling
    • Resource management
    • Analytics

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 LiquidPlanner if

  • You need predictive scheduling.
  • You also want resource management.

Questions people ask

Is Ona (formerly Gitpod) or LiquidPlanner better?
Neither clearly leads. Ona (formerly Gitpod) starts at Free and LiquidPlanner 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 LiquidPlanner?
Ona (formerly Gitpod) has a free tier; the other does not. Paid plans start at Free for Ona (formerly Gitpod) and On request for LiquidPlanner.
Does Ona (formerly Gitpod) or LiquidPlanner run on more platforms?
Ona (formerly Gitpod) runs on Web, Linux, macOS, Windows, AWS. LiquidPlanner 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. LiquidPlanner 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 LiquidPlanner is typically brought in for.
What can Ona (formerly Gitpod) do that LiquidPlanner cannot?
Ona (formerly Gitpod) covers Ephemeral environments, Agent sessions, Bring your own cloud, Devcontainer standard. LiquidPlanner covers Predictive scheduling, Resource management, Time tracking, Analytics.

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.

LiquidPlanner: How is Tempo timesheets pricing calculated for my organization?

Pricing is per-user per month and scales based on organization size. For 1-10 users: $1.00/user; 11-100 users: $5.21/user; 101-250 users: $3.66/user; scaling down to $0.25-$0.39/user for organizations with 5,000+ users.

Source
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.

LiquidPlanner: What license matching requirement exists for Tempo?

Your Tempo license size must match your Jira license size, with a user defined as anyone who can log into Jira.

Source
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.

LiquidPlanner: Is there a free trial for Tempo timesheets?

Yes, Tempo offers a free trial available through the Atlassian Marketplace.

Source
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.

LiquidPlanner: What deployment options are available for Tempo?

Both Cloud and Data Center deployment options are offered, with annual billing available.

Source
Share

Related pages

Other head to heads