Echobell vs Bark

A URL that pushes, or a channel that calls you

Bark turns a URL into an iOS notification, for free, on a server you can host yourself. Echobell adds Android and Apple Watch, alerts that arrive as an actual incoming call, and triggers that don't need a sender at all.

Echobell
VS
B Bark

Quick take

Bark is hard to beat for a personal iOS push you fire from a script. Echobell is for alerts that have to reach a team, on more than iPhone, at more than notification volume.

Choose Echobell when the alert has to reach Android or a watch, arrive as a call, or come from an inbox instead of a script.

At a glance

Echobell

B Bark

Platforms

iOS, Android and Apple Watch

Official client is iOS only

Highest urgency

Arrives as an incoming call with a ringtone and a call screen

Critical alerts and a repeating ringtone, still a notification

Where alerts come from

Webhooks, plus a dedicated email address per channel

HTTP request from whatever you are scripting

Key differences

Both turn an HTTP request into a notification. They differ in reach, in how loud the ceiling is, and in what can trigger them.

Platform reach

Echobell

Built in

iOS, Android and Apple Watch from one channel

Echobell covers a mixed-device team without a second tool.

B Bark

Partial

Official app is iOS only; Android users need something else

Urgency ceiling

Echobell

Built in

A real incoming call, with CallKit ringing and a call screen

A call screen is harder to sleep through than a loud banner.

B Bark

Partial

Critical alerts and call=1 repeat the ringtone, but it stays a notification

Hosting

Echobell

Not available

Hosted service only

Bark wins if you want the push server on your own machine.

B Bark

Built in

Runs on the public server or one you host yourself

Trigger sources

Echobell

Built in

Webhook and a per-channel email address, with templates and conditions

Echobell can alert on things that only ever send email.

B Bark

Not available

No email trigger or templating — the sender formats the whole message

Where Echobell wins

Echobell is built for alerts other people also depend on, not just your own phone.

Not iPhone-only

Android and Apple Watch are covered by the same channel, so a mixed team gets one setup.

An actual phone call

Calling mode rings with a full call screen, which is what it takes to wake someone at 4am.

Alerts from email, not just scripts

Every channel gets an address. Anything that can only send email — a bank, a vendor, a legacy system — becomes an alert.

Best-fit scenarios

People usually add Echobell alongside Bark for one of these reasons.

Someone on the team uses Android— When Bark's iOS-only client stops covering everyone who needs the alert.
Someone on the team uses Android

When Bark's iOS-only client stops covering everyone who needs the alert.

A push is no longer enough— When the alert has to survive a deep sleep, not just a silent switch.
A push is no longer enough

When the alert has to survive a deep sleep, not just a silent switch.

The source can only send email— When there is no script to add a Bark call to in the first place.
The source can only send email

When there is no script to add a Bark call to in the first place.

Moving from Bark

Nothing has to be switched off — Bark's key is a URL, and so is an Echobell channel.

  1. 1

    Create a channel per Bark key

    Keep the same grouping you already use for your Bark device keys.

  2. 2

    Swap the URL in your scripts

    Replace the api.day.app URL with the channel webhook. Title and body move into the request body as JSON.

  3. 3

    Turn on calling where it matters

    For anything you were sending with level=critical or call=1, set the channel to Calling instead.

FAQ

Find answers to common questions about Echobell

The official Bark client is iOS only. If part of your team is on Android, that is usually the reason to look elsewhere.

Not quite. Critical alerts and call=1 make the notification loud and repeat the ringtone, but it stays a notification. Echobell's calling mode rings with a real call screen.

No. Bark's server is open source and yours to run; Echobell is a hosted service. If self-hosting is the requirement, stay with Bark.

Keep the one-line URL. Add the phone call.

Point one Bark script at an Echobell channel and set it to Calling.