Softwr

Developer Tools · head to head

Ona (formerly Gitpod) vs ngrok

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

ngrok

Networking

Reverse tunnel service that gives a local or private service a public URL without opening a firewall

From
Free
Free plan
Yes

The short version

  • ngrok is free; Ona (formerly Gitpod) starts at $20/mo.
  • Only Ona (formerly Gitpod) lists ephemeral environments; only ngrok lists static domains.
  • Where ngrok falls short: bandwidth is metered on paid tiers, so a workload that quietly grows into serving real traffic produces overage rather than a flat bill.
  • Prices and features on this page were last checked on 20 November 2026.

How do Ona (formerly Gitpod) and ngrok differ?

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

Attributes where Ona (formerly Gitpod) and ngrok differ
AttributeOna (formerly Gitpod)ngrok
Pricing modelPer month by compute unitPer user per month
PlatformsWeb, Linux, macOS, Windows, AWSLinux, macOS, Windows, Self-hosted
CategoryDeveloper ToolsNetworking

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

Which features does each one have?

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

  • Outbound agent tunnels
  • Static domains
  • Traffic policy
  • Request inspection
  • Kubernetes ingress
  • TCP and TLS endpoints

What is each one used for?

ngrok is most often brought in for giving a partner a temporary authenticated endpoint into an internal API. 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 ngrok
  • Running several coding agents in parallel against real databases and services instead of on a laptopnot ngrok
  • Keeping source code off contractor and offshore laptops by moving the whole environment into a controlled accountnot ngrok
  • Reproducing a hard-to-configure toolchain for a short-lived project without polluting anyone machinenot ngrok

ngrok

  • Receiving webhooks from a payment or messaging provider on a laptop during developmentnot Ona (formerly Gitpod)
  • Demonstrating a work in progress application to someone outside the network without deploying itnot Ona (formerly Gitpod)
  • Publishing a service inside a private network or Kubernetes cluster without a public load balancernot Ona (formerly Gitpod)
  • Giving a partner a temporary authenticated endpoint into an internal APInot Ona (formerly Gitpod)

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

ngrok

  • Free HTTP endpoints show a browser interstitial before the page loads, which breaks first impressions in demos and confuses anyone you send the link to
  • All traffic passes through ngrok infrastructure, so you inherit its latency and an ngrok incident takes every published endpoint down at once with no local failover
  • Pricing is per user seat plus allowances, so a platform team publishing many endpoints ends up buying seats for people who never open the dashboard
  • Bandwidth is metered on paid tiers, so a workload that quietly grows into serving real traffic produces overage rather than a flat bill
  • Traffic policy configuration is specific to ngrok, so the authentication and routing logic you accumulate at the edge has to be rebuilt if you later move to a conventional ingress

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

Ona (formerly Gitpod) has a free plan, with paid plans from $20/mo; ngrok 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

ngrok

Free
  • FreeFree
    • One static domain
    • HTTP endpoints with a browser interstitial
    • Limited simultaneous connections
  • PersonalOn request
    • Removes the interstitial warning page
    • Additional reserved domains
    • TCP endpoints
  • ProOn request
    • Per user billing with team accounts
    • Traffic policy rules and edge authentication
    • Higher bandwidth allowances
  • EnterpriseOn request
    • Custom terms and volume pricing
    • Dedicated capacity options
    • Compliance and audit requirements

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

  • You need outbound agent tunnels.
  • You want to start without paying.
  • You work on Linux, macOS, Windows, Self-hosted.
  • You also want static domains.

Questions people ask

Is Ona (formerly Gitpod) or ngrok better?
Neither clearly leads. Ona (formerly Gitpod) starts at Free and ngrok at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Ona (formerly Gitpod) or ngrok?
Ona (formerly Gitpod) starts at Free and ngrok at Free.
Does Ona (formerly Gitpod) or ngrok run on more platforms?
Ona (formerly Gitpod) runs on Web, Linux, macOS, Windows, AWS. ngrok runs on Linux, macOS, Windows, Self-hosted.
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 ngrok is typically brought in for.
What can Ona (formerly Gitpod) do that ngrok cannot?
Ona (formerly Gitpod) covers Ephemeral environments, Agent sessions, Bring your own cloud, Devcontainer standard. ngrok covers Outbound agent tunnels, Static domains, Traffic policy, Request inspection.

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.

ngrok: Can I use it in production?

It is sold for that now, with static domains, policy rules and a Kubernetes operator. The question is whether you accept a third party on the traffic path for every request.

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.

ngrok: Why does my free URL show a warning page?

Free HTTP endpoints carry an interstitial. Removing it requires a paid plan, and it is the most common reason people upgrade.

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.

ngrok: Does it work for SSH or a database?

Yes through TCP endpoints, which are a paid feature.

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.

ngrok: What is the self hosted alternative?

A reverse proxy on a server you own with a tunnel back to the service, or one of the self hosted tunnel projects. All of them cost more setup time than the thing they replace.

Share

Related pages

Other head to heads