Softwr

Developer Tools · head to head

Ona (formerly Gitpod) vs RisingWave

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

RisingWave

Databases

Streaming database that maintains incremental materialised views in SQL instead of Flink jobs

From
Free
Free plan
Yes
Visit RisingWaveFull review

The short version

  • Free plans on both; paid from $20/mo and $0.227/mo.
  • Only Ona (formerly Gitpod) lists ephemeral environments; only RisingWave lists SQL materialised views.
  • 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 RisingWave actually diverge.

Attributes where Ona (formerly Gitpod) and RisingWave differ
AttributeOna (formerly Gitpod)RisingWave
Pricing modelPer month by compute unitPer RisingWave Unit hour
PlatformsWeb, Linux, macOS, Windows, AWSLinux, Self-hosted, Web
CategoryDeveloper ToolsDatabases

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

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 RisingWave

  • SQL materialised views
  • Postgres wire compatibility
  • Object storage state
  • Source connectors
  • Sink connectors
  • Iceberg tables
  • Watermarks and windowing
  • User defined functions

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

RisingWave

  • A team with Kafka topics that needs continuously fresh aggregates for a dashboard without standing up a Flink clusternot Ona (formerly Gitpod)
  • A fraud or risk team maintaining rolling counters and joins across event streams expressed as SQL viewsnot Ona (formerly Gitpod)
  • A company doing Postgres CDC into a real-time denormalised view for search or servingnot Ona (formerly Gitpod)
  • An analytics group that wants streaming results landed directly into Apache Iceberg without a separate writer jobnot 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

RisingWave

  • Anything that does not fit SQL, such as custom windowing, complex event processing or heavy stateful logic, still needs Flink, so RisingWave often adds a system rather than removing one
  • The Apache 2.0 community edition excludes premium features behind a licence key, and which capabilities sit on which side of that line moves between releases, so a self-hosted plan can be invalidated by an upgrade
  • Long-running materialised views accumulate state in object storage, and cost and recovery time grow with retention in ways that are hard to forecast before you are in production
  • The Postgres compatibility is protocol level; it is not a transactional Postgres and using it as a general purpose database, with point updates or high write concurrency, goes badly
  • It is a comparatively young venture-funded project competing with Flink, Materialize and warehouse-native streaming, and the ecosystem of connectors, operators and third-party expertise is much thinner

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

RisingWave

Free
  • Community EditionFree
    • Apache 2.0 licence, self-hosted
    • Core streaming engine and connectors
    • Premium features excluded and require a licence key
  • Cloud Basic$0.227/hour
    • Billed per RisingWave Unit hour
    • Hosted on AWS, GCP or Azure
    • Capped at 64 cores
  • Cloud ProOn request
    • No core limit
    • Bring your own cloud option
    • Premium features included
  • Self-managed EnterpriseOn request
    • On premises or Kubernetes
    • Premium features unlocked by licence
    • Annual contract with SLA

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

  • You need sql materialised views.
  • You want to start without paying.
  • You work on Linux, Self-hosted, Web.
  • You also want postgres wire compatibility.
RisingWave review

Questions people ask

Is Ona (formerly Gitpod) or RisingWave better?
Neither clearly leads. Ona (formerly Gitpod) starts at Free and RisingWave at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Ona (formerly Gitpod) or RisingWave?
Ona (formerly Gitpod) starts at Free and RisingWave at Free.
Does Ona (formerly Gitpod) or RisingWave run on more platforms?
Ona (formerly Gitpod) runs on Web, Linux, macOS, Windows, AWS. RisingWave runs on Linux, Self-hosted, Web.
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 RisingWave is typically brought in for.
What can Ona (formerly Gitpod) do that RisingWave cannot?
Ona (formerly Gitpod) covers Ephemeral environments, Agent sessions, Bring your own cloud, Devcontainer standard. RisingWave covers SQL materialised views, Postgres wire compatibility, Object storage state, Source connectors.

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.

RisingWave: Is RisingWave open source?

The community edition is Apache 2.0 and self-hostable, but a set of premium features requires a paid licence key.

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.

RisingWave: What does the cloud cost?

It starts at 0.227 US dollars per RisingWave Unit hour on the Basic tier, which is capped at 64 cores.

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.

RisingWave: Does it replace Flink?

For SQL-expressible transformations, often yes. For custom stateful processing and complex event handling, no.

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.

RisingWave: Can I query it like Postgres?

Yes over the Postgres wire protocol, but it is an analytical streaming engine, not a transactional database.

Share

Related pages

More on Ona (formerly Gitpod)

More on RisingWave

Keep looking

Other head to heads