Vero

Name: Vero
Brand: Vero
Price: 5449 USD

Event-driven messaging from a bootstrapped Australian team that has outlived most of its competitors

Vero is a customer engagement platform for product teams that builds email, push, and SMS messaging on top of a customer's own event and profile data, with a visual journey builder, broadcast sending, audience segmentation defined either through the API or by querying a connected data warehouse directly in SQL, priced from $54 a month for 5,000 user profiles with sending included.

Visit website

Overview

Vero has been running since roughly 2012, which in this category is close to geological. It was one of the earliest tools to argue that marketing email should be triggered by what someone did in your product rather than by which list they were dropped into, and it has held that position through more than a decade of competitors arriving, raising large rounds, and pivoting to enterprise. Chris Hexton co-founded it and still runs it, the team is remote and based in Australia, and the company has raised only one round before growing on revenue since.

That funding history is the most useful thing to know about Vero as a buyer. It has no pressure to move upmarket, no board demanding an enterprise motion, and no incentive to raise the entry price to chase larger contracts. What it has instead is a small team, a deliberately bounded feature surface, and a reported 5 billion messages sent in the past year at 99.99% uptime. The trade for a customer is stability and honest pricing against a product that will never have the breadth of a venture-funded platform.

Architecturally Vero is properly event-driven. You send identified user profiles and events, and segments, journeys, and personalization all evaluate against that stream. The unusual part is the data access model: alongside API-based ingestion and CDP connections through Segment or RudderStack, Vero connects directly to Snowflake, BigQuery, PostgreSQL, MySQL, and Redshift, so an audience can be defined as a SQL query against the warehouse rather than as a segment expression over data you re-pushed. Reverse ETL tools like Hightouch and Census are supported as well. For a data-literate team this removes an entire synchronization problem.

Pricing is unusually specific for this category. Starter is $54 a month, or $49 paid annually, covering 5,000 user profiles, 10,000 emails, 20,000 push messages, and 160,000 tracked events per month. Professional is quoted against your actual usage and is where SMS lives. There is no free plan and no free trial, which is the biggest practical objection: you cannot evaluate Vero without paying, in a market where OneSignal, Knock, Novu, and Courier all give you a working product at $0.

Best for

Small and mid-sized SaaS, edtech, and marketplace teams with real product event data who want behavior-triggered messaging with sending included, warehouse-native audiences, and a vendor that will still be independent and similarly priced in five years.

Not the right fit for

Anyone who needs to evaluate before paying; there is no free plan and no free trial, which in 2026 is a genuinely unusual position and disqualifies Vero from a lot of shortlists automatically.
Teams with no event instrumentation; without a product data stream you are paying for an engine you cannot start, and a list-based tool would serve you better for less.
Ecommerce brands wanting catalog-aware recovery flows, product recommendation blocks, and revenue attribution out of the box; Drip and Klaviyo-class tools are built for that and Vero is not.
Buyers who need in-app messaging or a notification inbox; Vero covers email, push, and SMS but has no in-app channel, so product notification surfaces need a separate tool.
Companies needing published pricing above the entry tier; Professional is quoted against usage, which is reasonable but means the cost curve past 5,000 profiles is a conversation rather than a number.

How it works

1
You send Vero your users and their behavior. Identified profiles carry whatever attributes matter (plan, signup date, feature flags, lifetime value) and events describe what those people did. Data arrives through the API, through server and client libraries, through a CDP such as Segment or RudderStack, or through a reverse ETL tool like Hightouch or Census.
2
Alternatively, you point Vero at your warehouse. Direct connections to Snowflake, BigQuery, PostgreSQL, MySQL, and Redshift let an audience be defined as a SQL query, which means the segment logic lives where your analytics team already works and does not need to be reimplemented in a marketing tool's segment builder.
3
Audiences are built from profile attributes, event history, and warehouse queries, and they recompute as data changes. Journeys are visual multi-step workflows with entry triggers, message steps across email, push, and SMS, delays, branches, and exit conditions, so an onboarding sequence reacts to what the user actually does rather than running blind to it.
4
Broadcasts handle the one-off sends that do not warrant a journey: a release announcement, a pricing change, a webinar invitation. Messages are composed in per-channel editors with personalization drawn from the same profile and event data, and analytics report on delivery, engagement, and conversion. Sending is included, so there is no separate ESP to configure or pay for.

Feature breakdown

19 features in 4 modules

Data foundation

The part that decides whether you can use Vero at all, and its clearest differentiator.

Identified profiles and event tracking: Users are identified with arbitrary attributes and their actions are tracked as events, forming the substrate that every segment, journey, and personalization token reads from.
Direct data warehouse connections: Connect Snowflake, BigQuery, PostgreSQL, MySQL, or Redshift directly and define audiences as SQL queries, so segment logic lives where your analytics team already works instead of being reimplemented in a marketing tool.
CDP ingestion: Segment and RudderStack feed profiles and events in without custom integration work, which is how most teams with an existing data stack will connect.
Reverse ETL support: Hightouch and Census can push warehouse-modelled audiences into Vero, for teams who prefer their transformation layer to own the definition.
Event volume allowance: The Starter plan includes 160,000 tracked events a month, which is a real allowance rather than a token one and lets a small product instrument thoroughly.

Journeys and automation

Behavior-triggered workflows across every channel Vero supports.

Visual journey builder: Multi-step workflows with entry triggers, message steps, delays, branches, and exit conditions, built on a canvas rather than in a rules list.
Event-triggered entry: Journeys start when a tracked event occurs, when a profile attribute changes, or when a user enters an audience, so nothing runs on a stale snapshot.
Branching and conditional paths: Split a journey on profile data or event history so one workflow serves several user types without being duplicated four times.
Delays and time-based steps: Wait steps between messages, which combined with exit conditions let a journey stop nagging someone who has already converted.
Goal-based exits: Define what the journey is trying to achieve and remove people from it when they achieve it, which is the difference between a sequence and an annoyance.

Channels and messaging

Email, push, and SMS with sending included.

Email with sending included: Vero runs the delivery infrastructure, so there is no separate ESP contract. The Starter plan includes 10,000 emails a month against 5,000 profiles.
Mobile push: iOS and Android push as a first-class channel inside journeys, with 20,000 messages included on Starter, which is a generous ratio to the email allowance.
SMS on Professional: SMS volume is a Professional-plan meter, so the entry tier is email and push only. Worth knowing before you commit if SMS is part of the plan.
Broadcasts: One-off sends to an audience for announcements and campaigns that do not need a journey around them.
Personalization from event data: Message content draws on profile attributes and event history, so an email can reference what someone actually did rather than only their first name.
Per-channel editors: Separate composition surfaces for email, push, and SMS rather than one editor pretending all three are the same medium.

Analytics and measurement

Enough to run the programme, not enough to replace your BI tool.

Campaign and journey analytics: Delivery, open, click, and conversion reporting per message and per journey step, so you can see where a sequence loses people.
Audience insight: Size and composition of audiences as they recompute, which matters when a segment definition quietly stops matching anyone.
Webhook and API access: Programmatic access to the platform plus outbound webhooks so results can flow into your own analytics rather than being trapped in a vendor dashboard.

Use cases

4 documented

SaaS company with a warehouse and no marketing engineer

The analytics team has already modelled churn risk and activation cohorts in Snowflake, but the marketing tool needs those definitions rebuilt in its own segment builder and kept in sync forever.

Vero queries Snowflake directly, so the audience is the SQL the analytics team already wrote, and the definition never drifts because there is only one of it.

Edtech product with onboarding drop-off

Learners sign up, complete one lesson, and vanish, and the current tool can only send on a fixed schedule after signup.

An event-triggered journey branches on which lesson was completed, waits, checks again, and exits the moment someone returns, so nobody gets a nudge about something they already did.

Marketplace sending both email and push

Push lives in a mobile SDK and email lives in a separate tool, so the two channels compete rather than cooperate.

One journey sends push first and falls back to email, both drawing on the same profile and event data, with 20,000 push messages and 10,000 emails included at $54 a month.

Team that got burned by a vendor moving upmarket

The last two messaging platforms they used raised entry prices, added minimums, and stopped answering support tickets from small accounts.

Vero has been independent and similarly priced for over a decade, with a single funding round and no incentive to abandon the segment, which is a real if unglamorous purchasing criterion.

Pricing

from $54 per month, or $49 per month billed annually

Subscription metered on user profiles plus separate allowances for emails, push messages, tracked events, and (on Professional) SMS, with sending included and a 10% discount for annual billing.

Plan	Price	Includes
Starter	$54 per month ($49 with annual billing)	5,000 user profiles 10,000 emails per month 20,000 push messages per month 160,000 events tracked per month Journeys, broadcasts, audiences, and analytics Everything except SMS is here. The event allowance is generous relative to the profile count, which suits a well-instrumented product.
Professional	Custom per month, based on usage (10% annual discount)	Custom user profile volume Custom email and push volume Custom event tracking volume SMS messaging Same journey, broadcast, and audience feature set at scale Quoted against your actual numbers rather than banded, which is fairer than tier jumps but means you cannot self-calculate the cost.

Plan

Price

Includes

Starter

$54

per month ($49 with annual billing)

5,000 user profiles
10,000 emails per month
20,000 push messages per month
160,000 events tracked per month
Journeys, broadcasts, audiences, and analytics

Everything except SMS is here. The event allowance is generous relative to the profile count, which suits a well-instrumented product.

Professional

Custom

per month, based on usage (10% annual discount)

Custom user profile volume
Custom email and push volume
Custom event tracking volume
SMS messaging
Same journey, broadcast, and audience feature set at scale

Quoted against your actual numbers rather than banded, which is fairer than tier jumps but means you cannot self-calculate the cost.

Billing notes

The meter is a combination: user profiles plus separate allowances for emails, push messages, and events. A large profile database with low send volume still costs profile money, but a high-volume sender to a small audience is not punished the way a pure profile meter would punish it.
Sending is included rather than bring-your-own-ESP, so unlike Knock, Courier, Novu, or Dittofeed there is no second invoice from SendGrid or Twilio underneath.
Annual billing takes 10% off both tiers.
At 5,000 profiles the price is exactly $54 a month, or $49 annually, which is the cheapest event-driven platform with included sending in this batch.
At 50,000 profiles you are on Professional and the price is quoted. Vero does not publish a band for it, so budget a sales conversation rather than a self-serve upgrade.
Overage is handled by conversation rather than automatic charges: Vero states it emails you when you cross Starter thresholds to discuss a Professional plan, and applies a fair use policy to keep monthly invoices stable.
There is no free plan and no free trial, which is the single biggest structural weakness of the commercial offer.

Value assessment: At the entry point Vero is excellent value and almost nobody knows it. Fifty-four dollars a month for a genuinely event-driven platform with journeys, broadcasts, warehouse-native audiences, and included email and push sending undercuts Customer.io's $100 floor and Ortto's Starter band by a wide margin, and the 160,000-event allowance means you can instrument properly rather than rationing. The catch is that you cannot try it: no free plan, no trial, so evaluation costs money in a market where four competitors will let you build a working integration for nothing. Above the entry tier the pricing is quoted, which is fair in practice but opaque on the way in. Judged on capability per dollar at 5,000 profiles, Vero is the best-priced event-driven option here; judged on ease of evaluation, it is the hardest to say yes to.

Strengths & limitations

Strengths

Properly event-driven rather than list-driven, with segments, journeys, and personalization all evaluating against a live profile and event stream.
Direct data warehouse connections to Snowflake, BigQuery, PostgreSQL, MySQL, and Redshift, so audiences can be SQL queries against data your analytics team already models.
Sending is included, which means no second invoice underneath and no deliverability infrastructure to assemble yourself.
The cheapest event-driven platform with included sending in this batch at $54 a month for 5,000 profiles, well under Customer.io's floor.
Bootstrapped after a single round and independent for more than a decade, with no structural incentive to abandon small customers or raise the entry price.
A generous event allowance at the entry tier (160,000 a month) that rewards thorough instrumentation instead of penalizing it.
Reported scale of 5 billion messages in the past year at 99.99% uptime, which is real operating experience rather than a startup's aspiration.

Limitations

No free plan and no free trial, so evaluating Vero requires spending money while four competitors in this category will let you build a working integration for nothing.
No in-app messaging or notification inbox channel, so product notification surfaces require a separate tool entirely.
SMS is Professional-only, meaning the published entry tier is email and push, and adding SMS moves you into quoted pricing.
Small team and a bounded feature surface: no CDP layer, no AI campaign agent, and none of the platform breadth that Customer.io or Ortto have accumulated.
Pricing above Starter is quoted rather than published, so the cost curve for a scaling company is not something you can model in advance.
Marketing to the wider world is thin, so despite a decade of operation Vero rarely makes shortlists and has a smaller ecosystem of consultants, templates, and community knowledge than better-funded rivals.

Head-to-head comparisons

5 alternatives

Vero vs Customer.io

from $100/mo (Essentials)

The closest functional comparison. Customer.io is broader (five channels including in-app and webhooks, a first-party CDP, objects, HIPAA, an AI agent) and starts at $100 a month billed on profile count. Vero covers email, push, and SMS with warehouse-native audiences from $54. Teams that need in-app messaging, compliance certifications, or CDP-grade data routing should pay for Customer.io; teams whose job is behavior-triggered email and push against warehouse data should take Vero and keep the difference.

Full Vero vs Customer.io comparison

Vero vs Encharge

from $79/mo (Growth, 2,000 subscribers, billed annually)

Encharge is SaaS lifecycle email with a flow builder from $79 a month and a friendlier evaluation path including a trial. Vero is more data-native, with direct warehouse SQL audiences and push as a real channel, at a lower entry price but no way to try it first. Choose Encharge if email automation is the whole job and you want to test before paying; choose Vero if your targeting depends on warehouse-modelled audiences or you need push alongside email.

Full Vero vs Encharge comparison

Vero vs Drip

from $39 per month for up to 2,500 subscribers

Drip is built for ecommerce: Shopify and WooCommerce integrations, cart recovery, onsite popups, and revenue attribution, from $39 a month for 2,500 contacts with a 14-day trial. Vero is built for product teams with event streams and has none of the ecommerce furniture. An online store should not consider Vero; a SaaS product should not consider Drip.

Full Vero vs Drip comparison

Vero vs OneSignal

from $0 (Free), then $19 per month plus usage (Growth)

OneSignal is push-first, free to start, and metered per channel on monthly active users, with tag-based rather than event-stream segmentation. Vero is event-first, costs $54 a month minimum, and can query your warehouse directly. Consumer apps whose main channel is push and whose budget is zero take OneSignal; SaaS products whose targeting depends on product event history take Vero.

Full Vero vs OneSignal comparison

Vero vs Userlist

from $149/mo (Basic, up to 10,000 users)

Userlist models B2B SaaS accounts natively, with many-to-many user-to-company relationships and company-triggered campaigns, plus hands-on onboarding from a small team. Vero has no account object but is stronger on warehouse integration and push. B2B SaaS teams whose complexity is organizational structure should take Userlist; teams whose complexity is data volume and event history should take Vero.

Full Vero vs Userlist comparison

Implementation & onboarding

Setup time: A day or two if you already have a CDP or warehouse to connect, longer if you are instrumenting events for the first time, which is a product engineering project rather than a Vero one. A first journey can be live the same week.
Learning curve: Moderate. The journey builder and audience tooling are approachable, but the model assumes you understand your own event schema, and teams without that understanding stall on what to segment rather than on how.
Onboarding: Self-serve signup, with documentation and support from a small and reachable team. There is no free trial, so the practical evaluation path is paying for one month of Starter and building a real integration in it.
Migration notes: Contacts and attributes import through the API, but event history generally does not come with you from another platform, so behavioral segments start shallow and deepen over the first weeks. Because sending is included, moving to Vero means moving sending reputation: authenticate your domain and ramp volume gradually rather than switching a large programme over in one day. Warehouse-defined audiences are the easiest thing to bring, since the SQL already exists.

Platform, API & security

Platforms: Web appREST APIServer and client librariesiOS and Android push SDKs
API: REST API for profiles, events, messages, and audiences, plus outbound webhooks, direct warehouse connections, and CDP and reverse ETL integrations.
Compliance: GDPRCAN-SPAM
Data residency: Not published as a self-serve option; discuss regional requirements with the team.
SSO: Not published as a standard self-serve feature.
Security notes: Vero reports 99.99% uptime year to date and roughly 5 billion messages sent over the past year. Warehouse connections are read-oriented, which keeps the sensitive data in your own systems rather than duplicating your entire customer base into a vendor.

Support & resources

Channels: Email supportDirect access to a small remote team
Documentation: Developer and user documentation covering the API, event tracking, warehouse connections, journeys, audiences, and message composition.
Community: Small; Vero has never had a large public community, and support is a conversation with the team rather than a forum search.

Company

Founded: 2012
Headquarters: Australia (remote team)
Ownership: Founder-led, largely bootstrapped after a single funding round
Founders: Chris Hexton
Employees: Small remote team; not disclosed
Funding: One early funding round, with growth funded from revenue since; the founders have publicly emphasised sustainability over venture dependence.

Timeline

2012Founded in Australia by Chris Hexton and co-founders on the premise that marketing email should be triggered by product behavior rather than list membership.
2014Raises its only funding round, then grows on revenue rather than pursuing further venture capital.
2018Adds mobile push as a first-class channel alongside email, extending journeys across both.
2021Introduces direct data warehouse connections, letting audiences be defined as SQL against Snowflake, BigQuery, PostgreSQL, MySQL, or Redshift.
2024Ships Vero 2.0, consolidating journeys, broadcasts, audiences, and analytics into a single customer engagement platform with SMS on the Professional tier.
2026Reports more than 5 billion messages sent over the previous year at 99.99% uptime, still independent and still priced from $54 a month.

Integrations

Segment
RudderStack
Snowflake
Google BigQuery
Amazon Redshift
PostgreSQL and MySQL
Hightouch
Census
Salesforce
Twilio
REST API and outbound webhooks

Frequently asked questions

10 questions

What is Vero?

Vero is a customer engagement platform for product teams. It sends email, push, and SMS messages triggered by what users do in your product, using a visual journey builder, broadcasts, and audiences defined from profile data, event history, or SQL queries against a connected data warehouse. It has been operating independently since around 2012 and starts at $54 a month for 5,000 user profiles.

How much does Vero cost?

Starter is $54 a month, or $49 with annual billing, covering 5,000 user profiles, 10,000 emails, 20,000 push messages, and 160,000 tracked events per month. Professional is quoted against your actual usage and is the only tier with SMS. There is no free plan and no free trial.

Is Vero event-driven or list-driven?

Properly event-driven. Segments, journeys, and personalization all evaluate against a live stream of identified profiles and tracked events, so a journey reacts to what someone did rather than to which list they were dropped into. That also means a company with no event instrumentation cannot use Vero productively at all.

What is the data warehouse connection for?

It lets an audience be a SQL query against Snowflake, BigQuery, PostgreSQL, MySQL, or Redshift instead of a segment expression rebuilt inside the marketing tool. If your analytics team has already modelled churn risk or activation cohorts, Vero can message against that model directly, so there is one definition rather than two that drift apart. Reverse ETL tools like Hightouch and Census are supported for teams who prefer to push audiences instead.

Do I bring my own ESP or sending domain?

Sending is included. Vero runs the delivery infrastructure, so there is no SendGrid or Twilio contract underneath the way there is with Knock, Courier, Novu, or Dittofeed. You authenticate your own sending domain so messages come from you, and deliverability is shared: Vero runs the infrastructure and reputation management, you own list hygiene, consent, and content.

Can a marketer operate Vero, or is it a developer tool?

Both, in sequence. Engineers instrument the events and connect the data source, which is a real project. After that, building audiences, composing messages, and designing journeys are all no-code and a marketer can work independently. The ceiling on what marketing can do is set entirely by what engineering instrumented, which is true of every event-driven platform in this category.

Why is there no free trial?

Vero has never offered one, and it is the most common reason teams do not evaluate the product. In practice the workaround is to buy one month of Starter at $54 and treat that as the trial, since there is no annual lock-in on the monthly plan. It remains a real disadvantage against OneSignal, Novu, Courier, and Knock, all of which give you a working product at $0.

Does Vero do in-app messaging?

No. Vero covers email, push, and SMS. There is no in-app message, no notification inbox, and no in-product nudge capability, so a team that needs those surfaces will run something else alongside it. Customer.io and OneSignal both cover in-app if that channel is essential.

How does Vero handle journeys ending?

Journeys support delays, conditional branches, and goal-based exit conditions, so somebody who converts drops out of the sequence rather than receiving the remaining reminders. Combined with event-triggered entry, this is what separates a journey from a scheduled drip, and it is the main reason to use a platform like this rather than a list tool with a timer.

Is Vero a safe long-term bet given the small team?

It has a stronger case here than most small vendors. Vero has operated since roughly 2012, raised only one round, and grown on revenue since, reporting 5 billion messages sent in the past year at 99.99% uptime. It is not going to be acquired and shut down by a larger platform on a growth-round timetable, and it has no incentive to abandon small customers. The risk is scope rather than survival: a small team ships fewer features, and Vero will never match Customer.io's breadth.

Editorial verdict

Vero is the quietly sensible choice that almost nobody shortlists. Fifty-four dollars a month buys a genuinely event-driven platform with journeys, broadcasts, push, included sending, and the ability to define an audience as SQL against your own warehouse, which undercuts Customer.io's $100 floor while covering most of what a small SaaS team actually uses. The company has been independent for over a decade, has no venture pressure to move upmarket, and sends billions of messages a year, which makes it one of the lower-risk long-term bets in this category despite the small team. The reasons not to buy it are specific and fair: no free trial means evaluation costs money, there is no in-app channel, SMS forces you into quoted pricing, and the feature surface will never match a funded platform's. For a five-person SaaS startup that has already instrumented its product and wants behavior-triggered email and push without assembling a stack, Vero is the best-priced serious option in this batch. For anyone who needs to try before paying, it is the hardest to get started with.

Written by the SaaSTracker editorial team. Awards, when shown, are judged against the published criteria in our methodology.