← Back to home
Comparison · HR

Ashby vs HiBob

A side-by-side editorial comparison of Ashby and HiBob — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:mcp

Ashby vs HiBob: at a glance

FeatureAshbyHiBob
SectorHRHR
Velocity score5.06.3
Sparks · 30d01
Top themesats, recruiting, scheduling, e-signaturepublic-api, crud-coverage, mcp, hr-data
Last editorial update1d ago12d ago
WebsiteVisit →Visit →

What is Ashby?

Ashby ships near-daily recruiting-ops depth while its AI layer arrives from off-changelog.

Ashby publishes small, individually-scoped releases at close to one a day — 25 in the five weeks to 27 August. The weight sits in three places: interview scheduling (candidate availability notes, meeting-room filters, organizer-email controls, unavailable-time display), document and e-signature workflow (offer letters inside approvals, automated NDA sends on stage entry, date-format and file-naming controls), and reporting hygiene (editable hired dates with an audit trail, reportable archive notes). An AI layer shows up throughout — AI Notetaker sharing with recording-level access controls, conversational authoring for custom agents, Slack reaching the Ashby MCP server — but every one of those releases extends something introduced elsewhere.

Read the full Ashby trajectory →

What is HiBob?

HiBob is closing the gaps in its Public API, one module at a time.

Bob's developer changelog is almost entirely API surface work, shipped in a steady two-to-three-week rhythm. The pattern is coverage: modules that were UI-only or partially exposed — Employer, Skills, Hiring, Time Off, and now several employee tables — get first-class Public API endpoints. Alongside that, the Bob MCP Server moved to OAuth, and Hiring gained an explainable AI match score.

Read the full HiBob trajectory →

Ashby vs HiBob: editorial side-by-side

A5.0

Ashby ships near-daily recruiting-ops depth while its AI layer arrives from off-changelog.

◆ Current state

Ashby publishes small, individually-scoped releases at close to one a day — 25 in the five weeks to 27 August. The weight sits in three places: interview scheduling (candidate availability notes, meeting-room filters, organizer-email controls, unavailable-time display), document and e-signature workflow (offer letters inside approvals, automated NDA sends on stage entry, date-format and file-naming controls), and reporting hygiene (editable hired dates with an audit trail, reportable archive notes). An AI layer shows up throughout — AI Notetaker sharing with recording-level access controls, conversational authoring for custom agents, Slack reaching the Ashby MCP server — but every one of those releases extends something introduced elsewhere.

◆ Where it's heading

The pattern worth naming is that Ashby's AI surfaces do not originate in this changelog; they appear already built and then get wired into the existing product. Custom Agents is referenced as an opt-in feature the conversational-authoring release builds on, and the MCP server is a precondition of the Slack release rather than its subject. What this feed does show is Ashby steadily closing the manual gaps around those surfaces: the automated e-signature release is the clearest case, cutting out the coordinator who previously had to open a reminder activity and dispatch each NDA by hand. Alongside that, the intake surface keeps widening — conditional form fields, more accepted file types, attachments pulled from synced mail into the candidate profile.

◆ Prediction

Given that agents, the notetaker and MCP all landed from outside this feed and are now being connected to scheduling, documents and the candidate profile in turn, the next releases here are most likely further wiring of those surfaces into the ATS rather than a new AI capability announced on the changelog itself.

HiBob logo6.3

HiBob is closing the gaps in its Public API, one module at a time.

◆ Current state

Bob's developer changelog is almost entirely API surface work, shipped in a steady two-to-three-week rhythm. The pattern is coverage: modules that were UI-only or partially exposed — Employer, Skills, Hiring, Time Off, and now several employee tables — get first-class Public API endpoints. Alongside that, the Bob MCP Server moved to OAuth, and Hiring gained an explainable AI match score.

◆ Where it's heading

Two threads are converging. The endpoint work is making Bob writable from the outside rather than merely readable, with create, update, delete and bulk operations arriving where only partial coverage existed. The MCP and AI work assumes something on the other end will consume that surface programmatically. Read together, HiBob is preparing Bob to be operated by external systems and agents, not just integrated with.

◆ Prediction

Expect the remaining UI-only modules to get the same CRUD treatment, and expect the MCP server's tool list to grow to match whatever the Public API newly exposes. The entries do not indicate which module is next.

Alternatives to Ashby and HiBob

Other HR products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Ashby or HiBob.

See all Ashby alternatives → · See all HiBob alternatives →

Recent activity from Ashby and HiBob

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 6d agoAshbyUI update for unavailable time
  2. 7d agoAshbyShare AI Notetaker recordings with your team
  3. 8d agoAshbyManage follow ups in bulk
  4. 8d agoAshbyCurrency custom fields for jobs and openings
  5. 9d agoAshbyReport on archive notes
  6. 11d agoAshbyOptional candidate availability notes
  7. 16d agoHiBobEmployee data API: New Employee Tables endpoints
  8. 27d agoHiBobHiring API: New AI CV Matching score in Applications
  9. 28d agoHiBobNew Bob Skills API: Push and sync skills into Bob
  10. 1mo agoHiBobTime off API: Find employee calendars
  11. 1mo agoHiBobEmployer API: now available in the Public API
  12. 1mo agoHiBobTime Off API: policyTypeCustomName on get request details

Frequently asked questions

What is the difference between Ashby and HiBob?

Both compete on the same themes — mcp — within HR. HiBob is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is Ashby better than HiBob?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. HiBob is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other HR products to evaluate alongside.

What are the best alternatives to Ashby?

Top Ashby alternatives in HR are ranked by recent ship velocity. Browse the "Ashby alternatives" section above for the current picks, or visit /alternatives/ashby for the full list with editorial commentary on each.

What are the best alternatives to HiBob?

Top HiBob alternatives in HR are ranked by recent ship velocity. Browse the "HiBob alternatives" section above for the current picks, or visit /alternatives/hibob for the full list with editorial commentary on each.