Softwr

Developer Tools · head to head

Ona (formerly Gitpod) vs Pigment

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
Visit Ona (formerly Gitpod)Full review
Pigment logo

Pigment

Business Intelligence

Enterprise business planning platform for finance, sales and workforce modelling

From
On request
Free plan
No
Visit PigmentFull review

The short version

  • Pigment is a French-built planning platform.
  • Ona (formerly Gitpod) starts at $20/mo; Pigment prices on request.
  • Only Ona (formerly Gitpod) lists ephemeral environments; only Pigment lists dimensional modelling.
  • Prices and features on this page were last checked on 31 August 2026.

Where they differ

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

Attributes where Ona (formerly Gitpod) and Pigment differ
AttributeOna (formerly Gitpod)Pigment
Starting priceFreeOn request
Pricing modelPer month by compute unitQuote
Free tierYesNo
PlatformsWeb, Linux, macOS, Windows, AWSWeb
CategoryDeveloper ToolsBusiness Intelligence

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 Pigment

  • Dimensional modelling
  • Scenario planning
  • Data connectors
  • Application blocks
  • Reporting and boards
  • Access control
  • Audit trail
  • AI assistance

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

Pigment

  • A finance team retiring a fragile Excel consolidation that no one can audit and only one person can runnot Ona (formerly Gitpod)
  • Sales operations modelling quota, territory and headcount capacity against a revenue plan in the same system finance usesnot Ona (formerly Gitpod)
  • A company that needs monthly re-forecasting fast enough to run scenarios live in the leadership meetingnot Ona (formerly Gitpod)
  • Replacing an ageing Anaplan estate where the model has become unmaintainable and per-workspace costs have crept upnot 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

Pigment

  • No pricing is published and the structure has three moving parts, platform fee, use-case fees and tiered seats, so two companies of the same size can pay very different amounts and neither can benchmark the other
  • Cost scales with planning processes rather than with company size, so a successful first deployment creates internal demand that directly increases the bill at renewal
  • It requires a modelling owner. Without a person who understands dimensional design, teams rebuild spreadsheet patterns in Pigment and inherit all the maintenance problems they were trying to escape
  • Implementation is partner-led and measured in months, so the payback horizon is long compared with lighter FP&A tools that a controller can configure alone
  • The connector library covers major systems well but the long tail is thinner than the incumbents, and industry-specific source systems often need a warehouse or a file drop in between

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

Pigment

On request
  • Pigment platformOn request
    • Platform fee plus per use-case fees
    • Licences tiered as editor, contributor and explorer
    • No free tier and no self-service signup

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.
Ona (formerly Gitpod) review

Choose Pigment if

  • You need dimensional modelling.
  • You also want scenario planning.
Pigment review

Questions people ask

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

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.

Pigment: Does Pigment publish prices?

No. Expect a quote combining a platform fee, fees per planning use case, and seat licences split into editor, contributor and explorer tiers.

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.

Pigment: Is Pigment an alternative to Anaplan?

It is positioned directly against Anaplan and much of its customer base is migrating from it, mainly citing modelling readability and recalculation speed.

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.

Pigment: Can we use it without consultants?

In practice most deployments use Pigment or a partner for the initial build. Ongoing model changes can be handled in-house once someone owns the modelling discipline.

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.

Pigment: Where is data hosted?

Pigment is a European vendor with regional hosting options, which is often the deciding factor for EU buyers with data residency requirements.

Share

Related pages

More on Ona (formerly Gitpod)

More on Pigment

Keep looking

Other head to heads