Orbyt vs Pave.
Pave closes the loop. Orbyt opens the data.
Real-time compensation benchmarking for VC-backed startups
Start on Build.At a glance.
Infrastructure coverage.
What Pave is.
Pave is a compensation benchmarking and planning platform founded in 2019 by Matt Schulman (former early Facebook engineer), headquartered in San Francisco. The product pulls real-time data from connected customer payroll systems and surfaces benchmarks inside a polished HR-facing dashboard. Pave raised $146M in Series C funding in 2022 at a reported $1.6B valuation and now serves roughly 6,000 companies: mostly VC-backed startups at Series A through Series C. For participating companies, the real-time payroll feed makes the dataset fresher than anything else in the category; the network effect is genuine. Outside the customer network, coverage drops sharply: public companies, enterprise SaaS, frontier AI labs that are not customers, non-tech industries, and regional employers are effectively not benchmarked. Orbyt Intelligence ships coverage that is source-driven, not customer-driven: 3,500 roles across 81 U.S. cities, whether or not any given company has ever signed with Orbyt.
Pricing, head to head.
Pave pricing is not published. Access requires a sales qualification call, with quotes typically ranging from low five figures to mid six figures annually depending on seat count, feature scope (benchmarking only vs. benchmarking plus comp planning), and company size. There is no self-serve developer tier. Demo access is behind the sales process. Orbyt Intelligence publishes its pricing grid in full: Build at $99 per month (60 req/min, AI Role Taxonomy engine), Pro at $299 per month (300 req/min, MCP server, all six engines), Scale at $1,999 per month (1,500 req/min, Company Signals, webhooks), and Enterprise at $4,999 per month (5,000 req/min, 99.95% uptime target, SSO). Every tier is visible at orbyt-intelligence/pricing: no sales call required. For an HR team at a VC-backed startup already running Pave, the two products solve different problems. For anyone outside that buyer profile, Pave is closed and Orbyt is open at $99/mo.
Orbyt wins.
A club, or the public square.
Six AI engines, each purpose-built: Role Taxonomy, Skill Premiums (quantified dollar premium per skill), Skill Half-Life (decay curves), Comp by Funding Stage (seed through public), Company Signals, Hiring Velocity. Pave gives you their network's snapshot; Orbyt gives you the full structure of the labor market.
MCP server with six locked tools. Claude Code, ChatGPT, autonomous agents query directly. Pave is a closed dashboard.
Coverage outside the network. 3,500+ roles, 81 cities, AI labs, Big Tech, enterprise SaaS, public companies: whether or not the company is feeding Pave a payroll stream.
Bloomberg-grade lineage via /lineage. Every data point traces to its sources (BLS, H-1B LCA, SEC, postings, community).
Transparent published pricing: $99/mo Build · $299/mo Pro · $1,999/mo Scale · $4,999/mo Enterprise. Pave pricing requires a sales call.
Public API with Bearer auth. Integrate in minutes.
Orbyt Intelligence does not require membership. 3,500 roles covered whether a company has ever signed a contract. Public API from $99/mo on Build. MCP server for AI agents. CC BY 4.0 license. Transparent pricing. The data is built on public sources and open channels, so the coverage is not gated by who is inside the payroll network.
Feature by feature.
On real-time freshness inside the customer network, Pave is best-in-class: the payroll-feed data refreshes continuously for participating companies and the benchmarks reflect the true current state of the Pave customer base. On coverage breadth outside that network, Orbyt Intelligence wins by a wide margin. Pave's dataset is concentrated on VC-backed startups in major hubs; Orbyt covers 3,500 roles across 81 U.S. cities including FAANG, enterprise SaaS, public companies cross-referenced against SEC proxy filings, and frontier AI labs regardless of whether they are Orbyt customers. On developer experience, it is not close: Pave has no self-serve API tier, no MCP manifest, no OpenAPI spec. Orbyt ships all three starting at $99/mo on the Build tier. On license, Orbyt is CC BY 4.0 (cite, redistribute, train models, embed); Pave data is contract-locked even for paying customers. On forward projections, Orbyt models through 2030 with a public methodology; Pave reports current-quarter only. On AI-era role coverage specifically, Orbyt tracks 598 AI-specific roles with leveling frameworks for Anthropic, OpenAI, DeepMind, Meta AI, and Cohere; Pave's AI-lab coverage depends on customer status.
Who each is for.
Use Pave if you are the head of People at a VC-backed startup in the Pave customer network, you need real-time peer benchmarks against similar-stage companies, and you also want a comp planning workflow integrated with the benchmarking data. For that buyer, inside that network, Pave is probably the best product on the market. Use Orbyt Intelligence if your coverage needs extend past the VC-backed startup ecosystem, if you are a developer building a feature, if you are an AI team running agent workflows, if you are a researcher citing data in a paper, or if your use case requires a license that permits redistribution. The products are not in direct competition for the same buyer: they serve different markets with different features. Most teams will end up running both if they have the budget and the breadth requirements.
Bottom line, in 2026.
In 2026, Pave owns real-time compensation benchmarking for VC-backed startups and Orbyt Intelligence owns open programmatic salary data for everyone else. Pave will keep being the right answer inside its customer network. Orbyt will keep being the only answer for public companies, AI labs outside the Pave customer list, developers, researchers, AI agents, and anyone who needs a license that permits building on top of the data. The two products solve adjacent problems; the market segmentation is clean. What matters is picking the right one for the use case. If the use case is 'benchmark my startup against Series B peers for next year's comp review,' Pave wins. If the use case is 'embed salary data in a product, query it from an AI agent, cite it in a paper, or cover employers who have never heard of Pave,' Orbyt wins.
How to migrate from Pave to Orbyt.
Most teams do not migrate off Pave: they add Orbyt Intelligence for the use cases Pave cannot reach. If you are using Pave for startup comp benchmarking and your coverage, licensing, or developer experience requirements have grown past what Pave ships, here is the path.
- Sign up for an Orbyt Intelligence account at intelligence/signup. Build at $99/mo unlocks 60 req/min with Bearer authentication and the AI Role Taxonomy engine.
- Generate an API key from the API dashboard. Set `ORBYT_INTELLIGENCE_KEY` as an environment variable. The OpenAPI 3.1 spec is at /openapi-intelligence.yaml.
- Map your current Pave role taxonomy to Orbyt role slugs. Orbyt's 3,500 roles include every startup role Pave covers, plus FAANG, enterprise SaaS, public companies, and AI labs that Pave benchmarks inconsistently depending on customer status.
- For AI agents, drop the Orbyt MCP manifest URL into Claude Desktop or ChatGPT Actions. Manifest is at /mcp-intelligence.json. The agent queries salary data as a first-class tool. Pave has no MCP story.
- Replace any Pave CSV exports or API workflows with `/api/v1/intelligence/salaries` queries. Orbyt returns structured base/equity/bonus/signing with percentile bands and source citations.
- Confirm your citation complies with CC BY 4.0. Orbyt's required attribution is 'Orbyt Intelligence, Q2 2026' plus a link to the dataset. Pave's data cannot be legally redistributed in a derivative product, even by paying customers.
Most teams finish the migration in under a day. The largest practical win is coverage outside the VC-backed startup slice: AI labs, public companies, enterprise SaaS, regional employers, and non-tech roles all become first-class. The licensing win (CC BY 4.0 vs. contract-locked) is the durable one for anyone planning to build on top of the data.
Start on Build.Where Pave lands. Where it does not.
Where Pave is strong
- Real-time data feed from customer payroll systems. Freshest in-category for members.
- Strong VC and startup-community brand
- Polished HR-facing dashboard UX
- Deep leveling data for participating customers
- Modern pricing and go-to-market vs legacy incumbents
Where Pave falls short
- Data universe limited to Pave customers. Misses non-participating companies entirely.
- No self-serve developer tier. Sales call required.
- No public API or MCP support
- Proprietary license. No data redistribution permitted.
- Narrow focus on VC-backed startup ecosystem
- No coverage of public companies, enterprise, or non-startup SaaS in depth
What Pave cannot do.
The specific gaps. Every one of them is a gap Orbyt Intelligence fills below.
The dataset is a private club. Non-members do not exist.
Pave's data comes from a real-time feed connected to customer payroll systems. For companies inside the network, the data is fresh and deep. For every company outside the network, including most of the U.S. labor market, there is effectively no data. If Anthropic, OpenAI, Apple, or Microsoft are not Pave customers, Pave does not benchmark them.
No public API tier.
Pave does not publish a self-serve developer tier. There is no way to evaluate the API without a contract. For a developer, a researcher, or a startup founder who wants to validate the data against a use case before committing budget, the doors are closed. Orbyt's Build tier at $99/mo is the alternative: published pricing, instant access.
No MCP. AI agents cannot query Pave as a tool.
As of Q2 2026, Pave does not ship an MCP manifest. Claude Desktop cannot call Pave during a conversation. ChatGPT Actions cannot pull a Pave benchmark as part of a workflow. Autonomous agent frameworks (Langchain, crewai, AutoGen) cannot list Pave as an available data source.
Proprietary license. Data cannot be cited or redistributed.
Pave data is proprietary and restricted to their customers. Even if you are a paying member, the agreement restricts how the data can be used outside internal analysis. For anyone publishing a research paper, building a public transparency tool, or training a model on compensation data, the license closes off the use case.
Coverage thins outside the VC-backed startup ecosystem.
Pave's core buyer is HR at Series A through Series C startups. That is where their customer network is densest and their benchmarks are most credible. Public companies at scale, enterprise SaaS, frontier AI labs that are not customers, non-tech industries, regional employers: these segments see the dataset thin fast.
Projections through 2030
Pave tells you today. Orbyt tells you 2030.
L6 Research Scientist, OpenAI. Annual total comp, projected year over year with methodology disclosed.
Feature by feature.
| Feature | Orbyt Intelligence | Pave |
|---|---|---|
| Public API with transparent pricingDecisive | ||
| MCP support for AI agentsDecisive | ||
| Total comp breakdown | ||
| Real-time payroll feed | ||
| Roles covered | 3,500+ | Startup subset |
| Cities covered (U.S.) | 81 | Major hubs |
| Coverage outside VC-backed startups | Broad | Limited |
| Forward projections to 2030 | ||
| Data licenseDecisive | CC BY 4.0 | Proprietary |
| Pricing transparent | Partial | |
| Transparent pricing published | ||
| OpenAPI spec published | ||
| Target buyer | Developers, AI teams, HR, candidates | Startup HR/People |
Based on publicly available feature lists and documentation as of Q2 2026. Updated quarterly.
Pave's dataset ends at their customer list. Ours does not. Coverage should not require a membership.
Common questions.
More comparisons.
Also from Orbyt
The same data, everywhere else.
You have the comparison.
Now query the data.
Build at $99/mo. 60 req/min. Scales to 5,000 req/min on Enterprise.