A HumanLayer alternative, now that it has joined Factory
Last updated 14 November 2026
Published 14 November 2026. Everything stated about other products below is from their own published pages, read on that date. Corrections to hello@jabee.ai.
HumanLayer is the company that put a name on a real problem: an AI agent that is about to do something irreversible should be able to contact a human, ask, and wait for the answer. Its SDK made "approval from a person" a function call, and a lot of the human-in-the-loop vocabulary this market uses traces back to it.
On 4 November 2026 HumanLayer announced it is joining Factory. Its own announcement says the platform remains available through a transition period of at least 30 days, and that recent payments to paying customers are being refunded. Before that, on 23 October 2026, it open sourced its core code under Apache 2.0. The company had already moved its product focus from the approvals SDK to a development environment over the past year, so for anyone still running agent approvals through it, the writing is not on the wall; it is in the announcement.
If that is you, the question is where the approval goes now.
What the job actually is
Strip the vocabulary and the job is small and strict: an agent reaches a step it must not take alone, a named person gets asked on a channel they actually see, the agent blocks until an answer exists, and the answer is recorded. Everything else — dashboards, policies, audit exports — is packaging around those four steps.
The options differ mainly on one axis: where the question lands. A question that lands where nobody is looking is a refusal with extra steps, so pick by the channel your approvers really watch.
The options, with their published prices
Prices are each vendor's own published figures, read on 14 November 2026:
| Option | Channel the question arrives on | Published price |
|---|---|---|
| HumanLayer's open sourced code | your own deployment of it | Free, Apache 2.0, self-hosted and self-maintained |
| gotoHuman | a web inbox | Free to 300 reviews/month, then from $99/month |
| Build it on a workflow tool (n8n and similar) | depends on the node you wire | The tool's own subscription, plus your WhatsApp or Slack credentials |
| Jabee approvals | WhatsApp, with email fallback | $29/month for 500 requests, then 3¢ each |
Three notes a table cannot hold:
Self-hosting the open sourced code is a real option and an honest one: it is the same approval model, free, and entirely yours to operate. What you take on is what you always take on with an archived-or-donated codebase — you are the maintainer now, and the question-delivery channels are whatever you wire up yourself.
The web-inbox products are built for teams whose approvers live in a browser all day. If your approvers are reviewing marketing copy from a desk, an inbox with thumbs up and thumbs down is a good shape. The failure mode is the 9pm deploy approval that sits in a tab nobody has open.
The workflow-tool route works and is the most flexible, with one catch this market consistently underestimates: the WhatsApp nodes in those tools use your Cloud API credentials, so you need a WhatsApp Business Account, a registered number and an approved template before the first question can be asked.
Where we fit, and where we do not
What we built asks on WhatsApp — the app your approver already has open and has never muted — over Meta's official Cloud API, with no number, business verification or template of your own, because the number and template are ours. The agent side is one HTTP call, or one MCP server for agents that speak it:
{
"mcpServers": {
"jabee": {
"command": "npx",
"args": ["-y", "@jabee/mcp"],
"env": { "JABEE_API_KEY": "jak_..." }
}
}
}
That gives the agent ask_person — a question with approve, skip and edit buttons that blocks until somebody taps one — plus tell_person for one-way notices and check_approval for answers that came later. The edit button matters more than it sounds: "no, the staging one" is a denial plus an instruction, and it comes back to the agent as both.
The honest limits: questions reach your own verified people only, never your customers, because every request rides a shared number; there is one verified handset per business (to reach several people, each verifies, or you connect your own number); and there are no review queues or multi-step approval policies. If you need four approvers and a policy engine, we are the wrong shape and the web-inbox products above are the right one. If you need one competent human to say yes before the agent acts, on the phone in their pocket, that is exactly what this is.
Moving an integration in an afternoon
The shape of a migration from any SDK-based approval flow is the same three steps: find the call sites where the agent asks, swap the client, and re-test the timeout path. The equivalent of a blocking approval call here is ask_person with a wait_seconds, and the equivalent of polling a pending approval is check_approval with the request id it returned. The approvals API reference has the webhook signatures and the Node and Python verification snippets; the MCP page has every tool argument.
The first three requests are free, which is enough to wire it to a dev agent and watch a question with three buttons arrive before deciding anything.
Questions
What happened to HumanLayer? Its own announcement of 4 November 2026 says it is joining Factory, that the platform remains available through a transition period of at least 30 days, and that recent payments are being refunded to paying customers. It open sourced its core code under Apache 2.0 on 23 October 2026.
Can I keep running HumanLayer myself? The code published under Apache 2.0 can be self-hosted and used freely. What changes is operational: you maintain it, you run the infrastructure behind it, and you wire up the channels questions arrive on.
What is the cheapest human-in-the-loop approval setup for an AI agent? For approvals that land on WhatsApp with nothing of your own to register, $29 a month for 500 requests is the published price here, and the first three are free. A web-inbox product has a free tier up to 300 reviews a month at one vendor. Self-hosting open sourced code is free in licence fees and costs whatever your time and servers do.
Can an AI agent ask for approval on WhatsApp without a WhatsApp Business account? Yes, if the request goes through a service whose number and Meta-approved template already exist. Jabee works that way: the agent calls ask_person over MCP or one HTTP endpoint, the question arrives on a verified phone with approve, skip and edit buttons, and the call blocks until an answer exists.
Does the person's answer get back to the agent as text? With an edit option, yes. Whatever the person types comes back as the amendment on the decision, so "approve, but make it 20% not 30%" is one reply rather than a refusal followed by a new prompt.
Sources
- HumanLayer, HumanLayer joins Factory: the acquisition announcement, the transition window, and the refunds. Read 14 November 2026.
- Factory, news announcement. Read 14 November 2026.
- gotoHuman, pricing page: the free tier at 300 reviews a month and the paid tiers from $99. Read 14 November 2026.
Written by Mumen Tayyem, founder of Jabee, in Dubai. Jabee's approvals API asks a person on WhatsApp over Meta's official Cloud API and waits for the answer: $29 a month for 500 requests, no number or Meta account of your own.