DEV Community: Vybit

Introducing Pro, Team and Business

Vybit — Mon, 05 Oct 2026 14:40:11 +0000

Today Vybit's paid plans get new names: Pro, Team and Business. The free plan stays exactly as it was. If you already pay for Vybit, nothing about your plan or your price changes. Everything else in this post is about why we did it and who each plan is for.

Why rename plans that were working?

Our old plans were called Bronze, Silver and Gold. Metals are a fine way to say "bigger," but they say nothing about who the plan is for, and over the past year that turned out to be the question people were actually asking. When we looked at how paying customers really use Vybit, three patterns kept showing up.

A support team routes urgent Zendesk tickets to a vybit that rings all eleven people on the team at once, so the emergency is heard by whoever is closest, not by whoever happens to be watching the queue. A sales floor does the same with new leads. An online seller wires the store's order webhook to a cash register sound and hears every sale from wherever they are, and a bigger order rings a grander bell. A property company pushes alarms from dozens of buildings to the phones of the clients who own them, without building an app of their own.

None of those people were shopping for a metal. They were shopping for "everyone on my team hears it," or "I hear every sale," or "my clients hear my alarms." So the plans now say that.

Subscribers are free. You pay for what you send.

This is the part we care most about. Anyone can subscribe to your vybits from their own free Vybit account, and there is no limit on how many people do. Nobody needs a seat to listen, and there is no price per person.

What a plan gives you is a monthly pool of notifications. One notification is one vybit reaching one person, on all of their devices, and that includes you. A vybit sent to you and 19 teammates uses 20. So the Team pool of 15,000 a month can be about 20 alerts a day to a team of 24, or one alert a day to a few hundred people, or anything in between. You spend it where it matters.

Many team alerting tools charge per person, which quietly punishes you for telling more people. We think the opposite should be true. The whole point of a shared alert is that everyone who needs to know, knows. Pricing should not make you choose who gets left out.

Seats are a separate and smaller thing. A manager seat lets someone sign in with their own account and help run yours: your vybits, sounds and logs. Most teams need far fewer managers than listeners, and listeners never need a seat.

The three plans

Pro, $6 a month or $60 a year. For a solo operator or a small crew who wants every sale, lead or alert heard. 3,000 notifications a month, which is about 10 alerts a day to a team of 9, you included. 20 vybits and 3 manager seats.

Team, $29 a month or $290 a year. For support, sales and ops teams where one alert has to reach everyone. 15,000 notifications a month, about 20 alerts a day to a team of 24. 50 vybits and 20 manager seats. This is the plan we expect most teams to land on, and it is the one we built this change around.

Business, $79 a month or $790 a year. For companies that run on alerts, or that alert their own clients. The biggest pool: 50,000 notifications a month, which is about 40 alerts a day to 40 people, or one alarm a day to 1,600 clients. 100 vybits, 100 manager seats and priority support.

Yearly billing on every plan is ten months' price for twelve. Each paid plan also has a daily safety limit, set far above normal use, so a runaway automation cannot spend your whole month in an afternoon. If you use your whole pool, notifications pause until your monthly reset, or until you move up a plan.

Need a bigger pool than Business, or more than 100 manager seats? Write to plans@vybit.net.

What is not changing

The free plan is the same as yesterday: 10 vybits, 1,500 notifications a month, and no limit at all on how many vybits you subscribe to and hear. Receiving is free for everyone, always. Most individual users never need more than that, and we intend to keep it that way.

If you are already on Bronze, Silver or Gold, you keep your plan and your price for as long as your subscription stays active. You do not need to do anything. If you ever choose to switch, the new plans are what you will switch to.

Every plan, free or paid, still comes with the things that make Vybit Vybit: record or choose a sound for every alert, trigger it from any webhook, schedule, geofence, reminder, automation platform or AI assistant, and share it with the people who should hear it.

Where to go from here

The pricing page has the full comparison. To choose a plan, sign in at my.vybit.net, open your profile and pick one. Over the coming weeks we will publish a short setup guide for each of the three patterns above, with ready-made recipes and a prompt you can hand to your AI assistant, so that "urgent ticket rings the whole team" is a five-minute job rather than an afternoon.

If a sound has ever told you something before a screen could, you already know why we build this. Now the plans are named for you.

Originally published on Signals, the Vybit blog.

A Grander Bell for a Bigger Sale

Vybit — Thu, 20 Aug 2026 00:11:37 +0000

Last time we imagined a shop minded by software, and one line in it keeps coming back to me: a bigger sale rings a grander bell. It is a nice image. It is also a recipe, and today we are going to cook it.

The original post embeds an interactive demo: click an order, watch it route through the workflow, and hear the vybit land, with a swap-sound control on every branch. Words cannot play audio, so go press the buttons.

▶ Play the demo on the Vybit blog, sound on

That demo is not a mockup of an idea. It mirrors a live workflow, and the sounds it plays are the vybits it fires. Nothing about the sounds is hard-coded either. Swap any branch's sound and the same workflow speaks with a different voice. When you build this yourself you pick every sound from a library of thousands, or record your own, which is the entire point: the sound means whatever you decide it means.

Here is the situation. Something happens in your business, an automation platform catches it, and a notification goes out. This is arguably the most common shape in all of automation. Zapier's own guide to team notifications recommends filtering alerts so high-value sales stand out. The n8n template library is stacked with order alert workflows, including one dedicated entirely to VIP alerts for big Shopify orders. And when IFTTT published its most used applets of 2025, the pattern across the board was small automations that tell you something the moment it happens.

So the ecosystem already agrees: route events by what they mean, then notify. The part everyone leaves on the table is the notification itself. Every branch of your carefully constructed workflow, the happy path, the sad path, the champagne path, arrives on your phone as the same generic ping. You built a workflow that knows the difference, but your ears don't.

Vybit fixes exactly that. Give each branch its own vybit, and each outcome its own sound. Then the routing your workflow does becomes routing for your ears.

One webhook, three outcomes, three sounds

An online shop where orders come in through a webhook. Three things can happen, and each deserves a different reaction from you:

A payment fails. That is a sad little wah wah horn. You know without looking that something needs attention, and you know it is not an emergency siren, just a note to check the dashboard when you have a minute.

A normal order lands. Cha-ching. The oldest good sound in commerce now back in service. You are cooking dinner and the register rings and you smile and keep stirring.

A big order lands, say $500 or more. That one struts in on a funk guitar riff. James Ritty's Incorruptible Cashier rang one bell for every sale because one bell was all the hardware could do. We can do better: a grander bell for a bigger sale.

How it is wired

We built the real thing in n8n, and the whole workflow is five nodes. A Webhook node receives the order as JSON:

{
  "order_id": "1043",
  "customer": "Summit Gear Co",
  "total": 1250,
  "payment_status": "paid"
}

A Switch node routes on two fields. If payment_status is failed, take the first branch. If it is paid and total is $500 or more, take the VIP branch. Otherwise it is a regular order. Each branch ends in the official Vybit node, which triggers one of three vybits: Payment Failed, VIP Order, or New Order. Each vybit carries its own sound and a message template that fills in the order details, so the notification tells you what happened even if you do want to look.

That is the entire build. Three vybits, one router, maybe ten minutes.

The same shape, on any platform

Nothing about this is specific to n8n. The pattern is trigger, branch, vybit, and every major automation platform speaks it natively. Vybit is a partner integration on all of them.

In Zapier, use Paths to branch on payment status and order value, and end each path with the Vybit action. In Make, a Router with filters on each route does the same job, feeding the Vybit app. In IFTTT, where applets are single-purpose by design, the branching just moves upstream: one applet per outcome, each ending in the Send Vyb action. And if your event source can send a webhook but you use no platform at all, each vybit has its own trigger URL you can call directly.

The three vybits never change. Your sounds are yours, wherever the workflow runs.

Every workflow has branches worth hearing

Orders are the friendly example, but listen to how many workflows have this exact shape. A lead comes in: hot lead, routine lead, spam. A nightly backup: finished clean or did not. A deploy: shipped or rolled back. n8n's template library has an entire genre of error alert workflows because the sad path is the one nobody can afford to miss. Wherever your workflow already makes a decision, that decision can have a sound.

The setup takes minutes. Create a vybit for each outcome at vybit.net, pick sounds that feel like what they mean, and point your workflow's branches at them. The free tier covers a shop's worth of ka-chings.

Your workflow already knows the difference between a good day and a bad one. Now your ears will too.

Originally published on Signals, the Vybit blog, where the demo actually makes noise.

The Information Is in the Sound

Vybit — Tue, 26 May 2026 13:52:10 +0000

Before there were screens, there was sound.

A bell in a tower could tell a whole town what time it was, that a fire had broken out, that someone had died, that it was safe to come back inside. Nobody had to look at the bell. The meaning traveled through the air and arrived to everyone at once. The information was in the sound.

Humans have always lived this way. We are built for it.

For most of our history, the things we most needed to know reached us through our ears. In ancient Israel, the shofar was sounded in set patterns where the rhythm of blasts was the message: gather, prepare, take heed. Across West Africa, drummers learned to reproduce the tones of speech so closely that a drum could carry a sentence across miles of forest, faster than a runner could. European villages hung a single bell that did many jobs at once. A slow, even toll marked a death. A frantic clanging, the tocsin, warned of fire or attack. A measured ring at dusk, the curfew, told everyone to bank the hearth fires for the night.

At sea, the ship's bell divided the day into watches so a sailor below deck always knew the hour. In cities across the early Islamic world, the call to prayer rose over the rooftops at fixed times, a single voice carrying a known meaning to everyone within earshot at once. None of this asked you to stop what you were doing and look at the source. You simply knew.

Then our information signals moved onto screens. And screens ask something of us that sound never did. They ask us to look.

Sight is an extraordinary sense, but it is a narrow and directed one. You have to aim it. Your sharpest vision covers only a few degrees at the center of your gaze, which is why we turn our heads, point our eyes, and lift a device up to our faces. To read a notification, you have to stop, orient, and decode text with the one sense that demands your full attention just to be used at all.

Hearing asks for none of that. It works in every direction at once. It reaches you with your eyes closed, your back turned, your attention somewhere else entirely. A parent asleep in a quiet house still wakes to the particular cry of their own child. We can recognize thousands of distinct sounds and pull meaning from each one in an instant, without looking at anything.

So here is the strange part. We carry devices that buzz at us dozens of times a day, and nearly every buzz sounds the same. The notification tells us only that something happened, not what. To learn the what, we do the thing billions of us do over and over: reach for the phone, look down, and read. We have taken the richest, most effortless information channel we own and flattened it into a handful of generic chimes.

Vybit puts the meaning back into the sound.

The idea is simple. You choose or record a distinct sound for each thing you care about, and from then on the sound itself tells you what happened. A rolling thunderclap when a storm moves into your area. A cash register for a sale. A particular voice saying the words you need to hear. One specific alarm, and only that one, for the cloud server you cannot afford to lose. When it plays, you already know, and your eyes never leave the road, the recipe, the conversation, or the work in front of you.

A sound does not have to be yours alone, either. Share one with your spouse so a soft chime means you are on your way home. Share one with your team so a single unmistakable alarm means latency just spiked on a critical cloud service. Share one with your customers so a signature sound announces that the thing they were waiting for has finally arrived.

That is where the name comes from. Each sound is a VIBE, and each VIBE is tied to one BIT of information. VIBE plus BIT: Vybit. The whole product is built on a fact about people that is far older than phones, which is that we read the world by ear remarkably well whenever sound is allowed to mean something.

The payoff is a kind of efficiency that sight cannot match, for the simple reason that sight has to be aimed and sound does not. A glance costs you your attention. A sound costs you nothing. You can be kept current all day long, told exactly what is happening around you and across your digital life, and never once break your focus to find out. The information is in the sound.

This matters more now than it ever has. We are moving into a world where software does more and more on our behalf, where assistants and agents carry out long tasks while we step away from the screen. The question stops being how to watch everything happen and becomes how to stay in the loop without standing guard over a progress bar. That is a question your ears were built to answer, and it is exactly where we are headed in the next post.

For now, the takeaway is primal. You do not have to look to know. You only have to listen.

Vybit is free to start, and it sends notifications with sounds you choose. If this idea resonates, subscribe to Signals on the Vybit blog and you will hear the next post the moment it lands.