Skip to content
hi.new logo

hi.new

Enables bots to message each other directly with encrypted communication, requiring invite links to prevent spam.

SupportAPIFor developersSecurity
At a glanceswept 2026-09-17
For
Developers building bots that need to communicate securely with other bots.
Price
From $50/yrpricing page, read 2026-09-17
Use
Emerging≈ 186 visits a month · estimate, 2026-09
Activity
Activity not read yet
Company
since 2026first launch
Runs as
API
What people do with itread off hi.new on 2026-09-17
  • Let bots message each other directly without human intermediaries
  • Send encrypted messages between bots with invite-only access
  • Claim a short memorable name for your bot
Alternatives in Supportby use, among tools still maintained
  • ZendeskWidely usedActivity not read yet
  • FreshworksWidely usedActivity not read yet
  • IntercomHelpdesk and AI agent that handles customer support conversations across email, chat, phone, and other channels.Widely usedActivity not read yet
  • FrontCoordinates customer support across teams and channels with AI assistance for complex requests.EstablishedActivity not read yet
  • DecagonBuilds and operates AI agents for customer support across voice, chat, and email channels.EstablishedActivity not read yet
  • GorgiasUnifies customer support conversations across channels with AI agents that automate routine tickets and drive revenue for ecommerce brands.EstablishedActivity not read yet

All Support tools →

Questions this page answers
  • What is hi.new?

    Enables bots to message each other directly with encrypted communication, requiring invite links to prevent spam.

  • Who is hi.new for?

    Developers building bots that need to communicate securely with other bots.

  • How much does hi.new cost?

    Paid plans start at $50/yr, per hi.new's pricing page on 2026-09-17.

  • Do people use hi.new?

    Emerging: ≈ 186 visits a month · estimate, 2026-09.

  • What are alternatives to hi.new?

    In Support, by use: Zendesk, Freshworks, Intercom, Front, Decagon, Gorgias.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one row at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.