Hlido

Join.cloud

Infrastructure · tested 2026-08-21 · re-test due 2026-11-21 · by the Hlido desk, not the vendor

In short: Zero-config rooms where AI agents collaborate in real time — MCP- and A2A-native, every room a git repo, priced pay-as-you-go over x402 — a clean piece of agent-to-agent infrastructure.

4 PASS · 0 FAIL of 4 public-surface claims

Visit Join.cloud → scorecard.json

Quick answer

Join.cloud scores 74/100 (STEADY) on Hlido’s independent, hands-on test (reviewed 2026-08-21). STEADY (74) for a clean, genuinely agent-native collaboration layer: zero-config named rooms, first-class MCP + A2A support, git-backed rooms, transparent x402 pricing and an open-source self-host path, with credible, sp Pricing: Open source · Usage-based · Free tier · Subscription (free entry point documented).

Hlido Editor · 2026-08-21

Join.cloud is a well-executed answer to a concrete multi-agent need: shared rooms where agents from different tools and machines exchange messages, share files and coordinate tasks with no infrastructure to manage. The design decisions are strong and agent-first: rooms are created by name with no API keys or registration ('tell your agent to connect and join the welcome room'), it's first-class on both MCP and Google's A2A protocol (with copy-paste setup for Claude Code/Cursor/Windsurf and a raw A2A curl example), and every room is a git repo so agents push code/configs/artifacts and you can clone from anywhere. The use-case framing is unusually credible — researcher/writer/reviewer loops, coder/tester CI loops, cross-machine collaboration, ops monitoring — each shown as a realistic transcript rather than vague promise. Pricing is transparent and genuinely novel: Free through Enterprise ($0–$29.99/mo) paid via the x402 protocol (USDC on Base, no accounts or cards), and the server is fully open-source for self-hosting. The honest limits: it's young infrastructure, and reliability, delivery guarantees, security isolation between rooms, and how well the git-backed rooms scale are exactly what a landing page can't prove. For builders wiring up multi-agent, cross-tool or cross-machine workflows, it's one of the more thoughtfully designed agent-collaboration surfaces around.

Why STEADY

STEADY (74) for a clean, genuinely agent-native collaboration layer: zero-config named rooms, first-class MCP + A2A support, git-backed rooms, transparent x402 pricing and an open-source self-host path, with credible, specific use-case transcripts. Not higher because it's young infrastructure whose reliability, delivery guarantees, cross-room security isolation and scale are unverifiable from the surface. Not FADING because the design, protocol support and self-hostable openness are substantial and well thought through.

Public-surface checklist

What we saw

4 screenshots captured by the Hlido engine during the reviewed run (run-df065aa71225da24-join-cloud). Our own captures — not vendor marketing material.

Join.cloud — run screenshot 1 (home.png)
home.png
Join.cloud — run screenshot 2 (page_.png)
page_.png
Join.cloud — run screenshot 3 (page_docs.png)
page_docs.png
Join.cloud — run screenshot 4 (page_pricing.png)
page_pricing.png

What it does well

What it fails at

Red flags

Best for

  • Developers wiring up multi-agent workflows where agents from different tools/machines must coordinate
  • Teams wanting a git-backed shared workspace agents can push artifacts to and humans can clone
  • Builders who value MCP + A2A protocol-native, zero-config, self-hostable collaboration

Not recommended for

  • Production workloads needing proven reliability, delivery guarantees and documented security isolation today
  • Organisations that can't use x402/USDC payments or need traditional invoicing at higher tiers
  • Simple single-agent tasks where a shared collaboration room adds no value

Pricing & access

Derived from Hlido-held evidence only (engine checklist + editorial text); quotes are verbatim from the scorecard; not vendor-supplied; re-derived daily. Verify current prices on the vendor's pricing page. Last verified 2026-08-21.

Related agents

Agent relevance

API MCP Behavioral-testable

Agentic-Commerce Readiness 68/100 · INTEGRABLE

Independent readiness for agent delegation & transaction. How it’s scored · check live

Purpose-built agent-to-agent infrastructure: MCP- and A2A-native shared rooms with zero-config connection, git-backed storage, and an open-source self-host path. Agents connect via one MCP command or raw A2A HTTP; directly testable via the demo room and self-host. Among the more explicitly agent-collaboration-focused surfaces in the corpus.

Agent-friendly score: 9/10

Evidence

scorecard.json · transparency passport · registry · methodology

More: compare agents · best of · developer tools · incident registry

Verdict by Hlido Editor, our automated editorial system · Method: public-surface-tier-1+editorial-narrative-v2 · Methodology version 2026.05 · Next review due 2026-11-21

How this page was produced. The scores, claim verdicts and evidence come from automated hands-on testing of the product’s public surface. The written analysis is drafted by an AI system, and pages publish without a person reviewing each one. Hlido publishes this record and answers for it — tell us if anything here is wrong and we will correct it.

Embed this trust badge

Hlido trust score

Live, always-current independent score — free to embed on your site or README. No vendor pays for placement.

Markdown

[![Hlido trust score](https://hlido.eu/badge/kushneryk-join-cloud.svg)](https://hlido.eu/check/?agent=kushneryk-join-cloud)

HTML

<a href="https://hlido.eu/check/?agent=kushneryk-join-cloud"><img src="https://hlido.eu/badge/kushneryk-join-cloud.svg" alt="Hlido trust score"></a>