Skip to content
Moat or Bloat

better-call

Utility library for better error handling and function calls

Library Rated 7 Oct 2026

Link
github.com/Bekacru/better-call.git
Built by
Beka

Bloat

257/500

Where it landed on the scale

Bloat
0
Float
300
Moat
400

Summary

better-call is a real, working open-source TypeScript library. It has shipped steadily for over two years, reached v1.0, and has 30 releases. It has no revenue model and no local-market angle, and it competes with established tools like Hono and tRPC, so its viability and moat are modest.

Bloat · Not much here works or looks likely to last, yet.

Breakdown

Five measures, 100 points each. Open the receipts under any of them to see the posts and pages behind the points.

Viability

Is there a real problem, someone who would pay, and a market this builder can actually reach?

It solves a real developer problem (one function usable as a server action, an API route and a typed client call), and it sits inside the better-auth ecosystem. But it is free MIT software with no payment or pricing path and no tie to the local market, so there is no demonstrated way to earn money.

42/100

Rubric 41–60Plausible users and a believable way to charge them. Not yet shown to work.

Receipts (3)

  1. Explains the concrete use case: one function used as a server action, an API route and a typed fetch client in Next.js and SvelteKit.

    “why I made better-call it is a lightweight web framework that let you create endpoints that can be called like normal functions. You can mount these endpoints on a router and serve them with a web framework (like bun. nextjs, sveltekit...), and you can use the client RPC for type-safe calls. usecase: - for nextjs you can make one function and call it as a server action, call it inside RSC, mou”

    Post · @bekacru_c · 17 Aug 2024 · open on Telegram (opens in a new tab)

  2. MIT-licensed repo now under the better-auth organization, so no commercial model is visible.

    Checked 7 Oct 2026 · github.com/Bekacru/better-call.git (opens in a new tab)

  3. The creator describes better-call as related to better-auth, which suggests it serves a larger project rather than being a standalone business.

    “> Besides better-auth, are there any other projects you’re currently working on or thinking about? there are other projects like better-call and better-fetch but they are still related to better auth so not really”

    Post · @bekacru_c · 19 Feb 2025 · open on Telegram (opens in a new tab)

Moat

What stops someone copying it?

The edge is mostly execution and a small footprint in a space with strong alternatives (Hono, tRPC). Its link to better-auth could give it distribution, but the dossier shows no proprietary data, network effects or hard technology.

28/100

Rubric 21–40The only edge is execution, or being first.

Receipts (3)

  1. The creator positions it as an alternative to Hono or tRPC, which are well-established competitors.

    “There have been many changes to better-call. I'll release version 0.0.5 once I'm satisfied with it, and it will be kinda viable alternative to Hono or tRPC”

    Post · @bekacru_c · 13 Aug 2024 · open on Telegram (opens in a new tab)

  2. The stated selling point is minimal footprint and low complexity, which is a design advantage that others can copy.

    “why I made better-call it is a lightweight web framework that let you create endpoints that can be called like normal functions. You can mount these endpoints on a router and serve them with a web framework (like bun. nextjs, sveltekit...), and you can use the client RPC for type-safe calls. usecase: - for nextjs you can make one function and call it as a server action, call it inside RSC, mou”

    Post · @bekacru_c · 17 Aug 2024 · open on Telegram (opens in a new tab)

  3. The repo is under the better-auth org, a possible but unproven source of distribution.

    Checked 7 Oct 2026 · github.com/Bekacru/better-call.git (opens in a new tab)

Momentum

Did the updates keep coming?

Worked on for 27 months, with updates in 16 of them, and still shipping releases as of October 2026. The path from v0.0.5 to v1.0 and onward is steady.

84/100

  • Sustained shipping60/60

    Worked on across 27 months.

  • Consistency24/40

    Updates in 16 of 27 months.

Receipts (2)

  1. Earliest post about it.

    “I made it to a library and wrote some docs 🚀 a lot of things to improve but happy with the results :)) https://github.com/Bekacru/better-call.git”

    Post · @bekacru_c · 27 Jul 2024 · open on Telegram (opens in a new tab)

  2. Most recent post about it.

    “> Besides better-auth, are there any other projects you’re currently working on or thinking about? there are other projects like better-call and better-fetch but they are still related to better auth so not really”

    Post · @bekacru_c · 19 Feb 2025 · open on Telegram (opens in a new tab)

Infrastructure

Does a real, working product exist?

A real, full-featured library exists, with a typed client, middleware, cookies and 30 versioned releases. Operational extras such as a status page and accounts don't apply to this kind of project.

83/100

  • It's live20/20

    https://github.com/Bekacru/better-call.git responded when checked.

  • HTTPS5/5

    Hosted on a platform (store, GitHub or Telegram) — HTTPS is the platform's.

  • Real product35/35

    A full, versioned library with a typed RPC client, middleware, signed cookies and a v1.0 release, published on npm and GitHub across 30 releases.

  • Own home0/10

    No home found.

  • Maintained15/15

    Last sign of shipping 2026-10-01.

  • Operations8/15

    It has a package registry presence and GitHub releases, and the creator says docs were written. There is no status page, API or accounts, which is normal for a library. The npm check was blocked, so docs could not be verified.

Receipts (5)

  1. https://github.com/Bekacru/better-call.git responded when checked.

    Checked 7 Oct 2026 · github.com/Bekacru/better-call.git (opens in a new tab)

  2. v0.1.0 lists a typed RPC client, cookies (regular and signed) and middlewares.

    “New Release 🎉 Better Call v0.1.0 This release is a signficant step for the library, Now it aligns with my initial picture. Includes: - typed RPC client (wraps over better-fetch) - Cookies (regular & signed cookies) - Middlewares - A lot of small improvements and fixes npm: https://www.npmjs.com/package/better-call?activeTab=readme github: https://github.com/Bekacru/better-call https://gith”

    Post · @bekacru_c · 17 Aug 2024 · open on Telegram (opens in a new tab)

  3. v1.0 was announced in February 2025.

    “better-call v1.0 https://github.com/bekacru/better-call”

    Post · @bekacru_c · 16 Feb 2025 · open on Telegram (opens in a new tab)

  4. 30 GitHub releases and frequent commits through October 2026.

    Checked 7 Oct 2026 · github.com/Bekacru/better-call.git (opens in a new tab)

  5. The creator says they wrote docs when turning the code into a library.

    “I made it to a library and wrote some docs 🚀 a lot of things to improve but happy with the results :)) https://github.com/Bekacru/better-call.git”

    Post · @bekacru_c · 27 Jul 2024 · open on Telegram (opens in a new tab)

Sustainability

Is it being set up to last?

It is distributed through npm and GitHub and is actively maintained, with a link to the better-auth ecosystem. There is no revenue, pricing or support channel, and its moat is thin against Hono and tRPC.

20/100

  • Distribution10/30

    Versioned downloadable releases (30 on GitHub).

  • Payments0/15

    No payment provider found.

  • Pricing0/10

    No pricing found on the site.

  • Revenue0/5

    No post mentions customers, sponsors or revenue, and no payment provider was found.

  • Privacy policy0/7

    No privacy policy found.

  • Terms0/5

    No terms of service found.

  • Support0/8

    No support contact found.

  • Commitment10/20

    The creator kept a visible path from v0.0.5 to v0.1.0 to v1.0 and keeps shipping. The repo now sits in the better-auth organization, which suggests a broader project. There is no dedicated community channel or funding evidence.

Receipts (5)

  1. Versioned downloadable releases (30 on GitHub).

    Checked 7 Oct 2026 · github.com/Bekacru/better-call.git (opens in a new tab)

  2. The crawler found no payments, pricing or accounts.

    Checked 7 Oct 2026 · npmjs.com/package/better-call (opens in a new tab)

  3. v0.1.0 is described as matching the creator's initial vision.

    “New Release 🎉 Better Call v0.1.0 This release is a signficant step for the library, Now it aligns with my initial picture. Includes: - typed RPC client (wraps over better-fetch) - Cookies (regular & signed cookies) - Middlewares - A lot of small improvements and fixes npm: https://www.npmjs.com/package/better-call?activeTab=readme github: https://github.com/Bekacru/better-call https://gith”

    Post · @bekacru_c · 17 Aug 2024 · open on Telegram (opens in a new tab)

  4. v1.0 followed through on the earlier roadmap.

    “better-call v1.0 https://github.com/bekacru/better-call”

    Post · @bekacru_c · 16 Feb 2025 · open on Telegram (opens in a new tab)

  5. Commits on 49 listed days from October 2025 to October 2026 under the better-auth org.

    Checked 7 Oct 2026 · github.com/Bekacru/better-call.git (opens in a new tab)