Audryo Review (2026): Pricing, Features & Honest Verdict

TLDR

Audryo is a lifecycle email platform built for your AI assistant to operate over MCP, an HTTP API or a CLI, with a human approval step before anything sends. It is careful, thoroughly documented and very young. Best for: SaaS teams already working with an assistant. Price: free beta now, planned from EUR 19/mo, free plan yes. Rating: 7/10.

What is Audryo?

We found Audryo on Product Hunt, where it launched on 29 September 2026 as customer email that an assistant can run for you. It covers the full lifecycle stack: contacts and events, audiences, automated journeys, one-off campaigns, transactional sends and results measured against a holdout group. The difference from older tools is who does the setup. Your assistant does, through named tools, and you approve the result.

Audryo is operated by Dear Friend Digital GmbH, a product studio in Nuremberg, Germany. The terms say the service is for businesses only, not consumers, and the core platform is hosted in Germany. It is in public beta, free until 1 January 2027 for up to 25,000 reached people a month, and the paid bands on its pricing page are listed as planned and not for sale yet.

What Are Audryo’s Key Features?

An agent toolkit with real scopes

The audryo package (MIT licence, version 0.1.1, first published on 28 September 2026) bundles an MCP server, a CLI and three skill files for assistants. The docs list 33 MCP tools, from get_product_context and list_journeys to run_dry_run, draft_campaign and send_transactional. Each token carries read, write or deliver scope. Without deliver, an assistant can build audiences, journeys and emails but cannot send a single message, even by mistake.

Review before anything reaches a customer

Journeys are versioned. An assistant drafts a flow, you check who receives it, what they receive, when it stops and who changed it, then approve and activate. Any edit after that comes back for review instead of replacing the live version. The public operating rules served by the API say no autonomy level permits autonomous approval or delivery, which is the right default for anything that emails customers.

Consent and suppression checks that hold

Audryo checks every recipient before every send. Marketing and newsletter emails need a recorded consent entry, and the docs are blunt that a contact property like subscribed: true does not count. Suppressions stop all email to an address, a blocklist accepts wildcard domains, and double opt-in is a setting. People without consent show as blocked rather than quietly mailed.

Sandbox mode and holdout results

Every new project starts in sandbox mode. Journeys, campaigns and API sends run for real, with waits, consent checks and personalisation, but each email lands in a sandbox inbox inside Audryo instead of a real one. You can fast forward waits to test a three day journey in minutes. Once live, results compare the people who got the journey against a held out group, so you see lift, not only opens.

What Is It Like to Use Audryo?

The setup is short if you already use Claude Code or Codex. There is a plugin for Claude Code that installs the MCP server and skills in two commands, and other clients take a one line MCP config with an Audryo token. The quickstart then hands you a starter prompt that tells the assistant to read the project context, propose one useful lifecycle step and stop for review.

From there the work is conversational. You ask for an onboarding journey for new signups, and the assistant reads your data schema, drafts the audience and emails, runs a dry run and hands back a list of what changed. You open the same draft in the Audryo editor to change a headline or add a German version. The docs suggest pairing the email skill with an image generation skill for custom hero images.

Documentation is the strongest part of the product right now. The API is described by an OpenAPI document with about 150 paths, there is an llms.txt index, and the pages explain edge cases like what happens when someone gains consent mid journey. That level of care is unusual for a product four days past launch.

Everything around the docs is thinner. The public toolkit repository had one star and eight commits when we checked, the package saw about 300 registry downloads in its first week, and there are no public customer stories yet. You are an early tester, and the terms say so: no service level agreement, and beta features can be throttled, paused or discontinued.

Where Does Audryo Fall Short?

Audryo does not send email itself. Every message goes out through your own Resend, Mailgun or SMTP account, and the terms state that you pay that provider separately. That protects your sending reputation, but it means a second invoice and a DNS setup that Audryo cannot do for you. Competitors like Bento include marketing sends in the price.

The site disagrees with itself on AI. The plans documentation says every plan includes Audryo AI, while the pricing page code says the planned 500 person Free tier does not include hosted Audryo AI. The pricing FAQ also says paid plans add hosted AI. If built in AI drafting matters to you, assume it is a paid feature after the beta.

The 1 January 2027 switch is vague. Nothing we read explains what happens to a beta workspace on that date: whether it drops to the 500 person Free tier, needs a card, or gets notice first. The terms only promise reasonable notice for list price changes. The 25,000 tier text also refers to a Free mark that paid plans remove, while the beta copy never says whether beta emails carry it.

Data handling is mostly good with one asterisk. AI drafting runs through OpenRouter, which the privacy policy says is configured for no data retention and no training on prompts. Raw contact records are not sent to models. But AI routing can process data outside the EU, which buyers drawn by the German hosting may overlook.

How Much Does Audryo Cost?

Audryo is free during the public beta, up to 25,000 reached people a month, with no card required. After 1 January 2027 the planned tiers start at EUR 19 a month for 1,000 reached people. Those prices are not for sale yet, and you cannot activate a paid tier during the beta.

The pricing page slider holds every tier in its code: 500 people free forever, 1,000 for EUR 19, 5,000 for EUR 59, 10,000 for EUR 99, 25,000 for EUR 179, 50,000 for EUR 299, 100,000 for EUR 499, 250,000 for EUR 899 and 500,000 for EUR 1,499 a month. Above that is custom Enterprise pricing with SSO, private infrastructure and an uptime SLA.

Its counting unit is the clever part. A reached person counts once per calendar month when they receive at least one email, whether campaign, journey or transactional. Stored contacts, people waiting in a journey, holdouts, failed sends and sandbox tests are free. If you go over your tier, nothing stops. Only two months in a row above it moves you up a tier, from the next billing period, with seven days of notice.

Compare that with the alternatives. Customer.io Essentials starts at $100 a month for 5,000 profiles. Bento charges $29 a month for up to 5,000 active users with unlimited marketing sends included. Audryo’s planned EUR 59 for 5,000 reached people looks fair, but add your provider: Resend Pro is $20 a month for 50,000 emails. For a SaaS with a large dormant list, paying only for people you email is a real saving.

Who is Audryo Best For?

Use Audryo if you run a SaaS or subscription app, already do much of your work with an AI assistant, and want onboarding, activation and win back emails without learning a visual journey builder. It also suits European teams who want German hosting, a consent ledger and a processor agreement on request.

Use it too if your contact list is far larger than the group you email in a given month. The reached people model rewards keeping old contacts and event history instead of deleting them to cut costs.

Skip Audryo if you need a vendor with a track record, an SLA or SMS and push alongside email. Skip it too if you want one invoice with delivery included, or if nobody on your team is comfortable setting DNS records for a sending domain.

Best Audryo Alternatives

Bento

Bento is the closest rival for SaaS lifecycle email, with event based automations, campaigns, forms and a separate transactional email product. Like Audryo it bills on people rather than stored contacts: the Marketing Platform is $29 a month for up to 5,000 active users, then from $0.01 per active user. There is no free plan, only a 30 day trial. Transactional email starts free for 100 emails, then $5 a month up to 12,500.

Customer.io

Customer.io is the established choice for data driven messaging across email and other channels, with a visual workflow builder and its own built in assistant. Essentials starts at $100 a month for 5,000 profiles and one million emails, and Premium starts at $1,000 a month billed yearly.

Resend

Resend is a developer email API and one of the providers Audryo sends through. On its own it suits teams that want to code transactional email and simple broadcasts themselves. The free tier covers 3,000 emails a month, Pro is $20 a month for 50,000 emails and Scale is $90 a month for 100,000.

Final Verdict: Is Audryo Worth It?

Audryo gets the hard parts of agent operated email right. Scoped tokens, versioned journeys, a sandbox that runs the real pipeline and consent checks an assistant cannot talk its way past are what you would want before letting software email your customers. The reached people pricing is also friendlier than contact based billing for most SaaS lists.

It is still a four day old beta with a separate provider invoice, unclear AI terms after launch and no word yet on what happens to beta workspaces on 1 January 2027. We recommend trying it now while it is free, ideally on onboarding emails in sandbox mode, and waiting for the post beta details before you move your whole lifecycle program over.