By David,
If you run an MSP, October 2026 gave you two new AI pitches in one week.
Rewst made its new platform available in every market on October 13. The centerpiece is the Rewst Agent, which builds workflows, forms, dashboards and client-facing apps from a plain-English description. Neo Agent joined the Pax8 Marketplace on October 15, putting an AI service desk technician on the same invoice as your Microsoft licenses.
Both say they'll take work off your technicians. They mean different things by it, and choosing between them starts with understanding the difference.
The short version: Neo Agent does the work. It picks up tickets in your PSA, decides what each needs, carries out the fix through your tools and closes the ticket, with technician approval wherever you require it. The new Rewst builds the work. Its agent drafts a workflow, form or client app from your description, a person reviews and publishes it, and from then on it runs the same way every time. Many MSPs will end up with both, because one is a technician and the other is an automation platform.
Details below come from each vendor's public website and announcements as of October 2026, linked in the Sources section. Vendors change products and pricing, so confirm current details directly.
Two ways to put AI to work
The clearest way to see the difference is to follow one request, a new starter at a customer, through each product.
With Neo Agent, the onboarding request arrives as a ticket. Neo reads it, checks the customer's playbook and documentation, creates the account in Microsoft Entra ID or Active Directory, assigns licenses, updates the ticket and closes it. Neo's own example puts a manual onboarding at about 30 minutes and Neo's at under a minute. Next week's new starter is a new ticket, and Neo works it again.
With the new Rewst, you describe the onboarding process once: "when HR submits a new starter, create the account, assign the license for their role, add them to the right groups and email their manager." The Rewst Agent builds the workflow on Rewst's canvas, along with a branded form HR can fill in. An engineer reviews it, tests it and publishes it. From then on, every new starter at every customer runs through the same published workflow.
Neo is judgment applied to each ticket. Rewst is a process, captured once and repeated.
Side by side
| Neo Agent | The new Rewst | |
|---|---|---|
| What it is | An AI first-line technician for your service desk | An automation platform with an AI agent that builds for you |
| You give it | A brief, playbooks and documentation | A description of the outcome you want |
| It produces | Resolved, documented tickets | Workflows, forms, dashboards, reports and client apps |
| Where work starts | A ticket in your PSA, a phone call or a Teams message | A trigger, a schedule, a form or a client portal |
| PSA support | ConnectWise PSA, Autotask, HaloPSA, Syncro, ServiceNow | Through its integrations (340 used in Early Access) |
| Client-facing | Branded Teams chat bot and AI phone agent (add-ons) | Branded forms, client portals and self-service apps |
| Pricing | Monthly plans in credits, from $1,300 a month | Per client organization, in bands, all features included |
| Trial | 14 days, against your own tickets | Demo and quote |
Approvals and guardrails
Both vendors have clearly thought about the question your customers will ask: what is the AI allowed to do without a person?
Neo Agent gives every tool an access level: none, read or write, with its generic API tool scoped per endpoint. Test mode runs every action as a note in the ticket first, so you can watch Neo work your real queue before it changes anything. Technician-in-the-Loop holds the actions you choose until a technician approves them, and low-risk work can run unattended once you're comfortable. Every step goes into an audit log, described in plain English.
The new Rewst keeps a person between the AI and production. The Rewst Agent can't create, update or publish a workflow or form without explicit approval, and it asks again before publishing. Publishing is its own permission, given to named people. Credentials are scoped to the client they belong to, and AI access is granted separately from each integration, so you can revoke the AI's access without breaking the automations already running.
The difference follows from the job. Neo's AI acts at run time, so its controls are about which actions it can take and which need a human. Rewst's AI acts at build time, so its controls are about what reaches production. Once a Rewst workflow is published, it runs as written.
Pricing models
Neo Agent sells monthly plans sized in credits, six of them from 2,500 to 100,000 credits a month. Its Starter plan is listed at $1,300 a month, month to month with no setup fee, and sized for around 3,300 tickets. On Pax8 it bills on your existing Pax8 invoice. Because the unit is work done, the bill tracks your ticket volume.
The new Rewst prices per client organization, with lower per-client rates as your client count grows. Every feature, unlimited users and unlimited automations are included at every size. AI comes with an allowance worth 5% of your monthly invoice, or you can connect your own AI key and pay your provider directly. Rewst doesn't publish its per-client rates. Because the unit is a client, the bill tracks your customer count, not how much you automate.
Which one fits
- Choose Neo Agent first if your pain is ticket volume: a first-line queue that never empties, after-hours calls, or onboarding and password resets that eat your juniors' week. It works inside the PSA you already have, and its test mode makes it easy to try.
- Choose the new Rewst first if your pain is inconsistency: the same process done ten different ways across forty customers, license reconciliation at every billing cycle, or customers who want a self-service portal. You keep the logic, and it runs the same way every time.
- Plan for both if you're growing. Rewst's own launch named turning security alarms into PSA tickets as a top Early Access use case, and Neo is built to work exactly those tickets.
What both need underneath: the platform the ticket is about
Neither product runs your customers' infrastructure. They work through the tools you connect. That matters most for the services with the most moving parts, and for many MSPs that is Azure Virtual Desktop.
"Users can't get onto their desktops" might be a full host pool, a bad image, FSLogix storage running out or an Azure quota limit. An AI technician can only work that ticket as well as the platform behind it lets it see and act. An automation builder can only automate what has an interface to call.
That's the job Atlas AVD does. It runs in your own Azure tenant and deploys, scales, images and monitors AVD for every customer from one console. It alerts to SMS, Teams, Slack or any webhook, opens and resolves tickets in Atlas Flow or syncs them with ConnectWise Manage, and offers a scoped API for the tools you trust. Our three-way comparison walks through how Neo Agent, the new Rewst and Atlas AVD fit together, step by step.
See Atlas AVD for MSPs, or start a 30-day trial.
Sources
- Rewst: Rewst launches new automation platform globally (October 13, 2026)
- Rewst: Welcome to the new Rewst
- Rewst: Pricing
- Neo Agent: Neo Agent brings its AI service desk workforce to the Pax8 Marketplace (October 15, 2026)
- Neo Agent: neoagent.io